On Wed, 2019-06-12 at 12:27 +0100, Andrew Cooper wrote: > It is a consequence of our extra magic scheduler locks which protect > the > pointer used to locate them, and the ensuing double-step in ??? > (seriously - I can't figure out the function names created by the > sched_lock() monstrosity) which take the lock, re-read the lock > pointer > and drop on a mismatch. > Just FTR, they're:
vcpu_schedule_lock() vcpu_schedule_lock_irq() vcpu_schedule_lock_irqsave() and: pcpu_schedule_lock() pcpu_schedule_lock_irq() pcpu_schedule_lock_irqsave() and the corresponding *_schedule_unlock_*() ones, of course. ;-P Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
