xen/vm-event: Expand vm_event_* spinlock macros and rename the lock
authorAndrew Cooper <andrew.cooper3@citrix.com>
Fri, 31 May 2019 20:57:03 +0000 (13:57 -0700)
committerAndrew Cooper <andrew.cooper3@citrix.com>
Tue, 4 Jun 2019 13:43:51 +0000 (14:43 +0100)
commita63f8f0672e6b9582f32b4ac61a595e5aea7ede7
tree92867af3a6629bc51191a190f507d90f11ebfcbe
parent48b84249459fac2e96bde6337b0080662c5fe0ea
xen/vm-event: Expand vm_event_* spinlock macros and rename the lock

These serve no purpose, but to add to the congnitive load of following
the code.  Remove the level of indirection.

Furthermore, the lock protects all data in vm_event_domain, making
ring_lock a poor choice of name.

For vm_event_get_response() and vm_event_grab_slot(), fold the exit
paths to have a single unlock, as the compiler can't make this
optimisation itself.

No functional change.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
xen/common/vm_event.c
xen/include/xen/sched.h