Skip to content

RFC Xen: FIFO-based event channel ABI

David Vrabel xen-devel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest8 patches 18 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/8debug: remove some event channel info from the 'i' and 'q' debug keysxen/arch/x86/irq.c xen/common/keyhandler.c+3 -130 replies
2/8evtchn: refactor low-level event channel port opsxen/arch/x86/irq.c xen/common/Makefile xen/common/event_channel.c +4 more+172 -603 replies
3/8evtchn: add a hook to bind an event port to a VCPUxen/common/event_channel.c xen/include/xen/event.h+16 -00 replies
4/8evtchn: Dynamically allocate d->evtchnxen/common/event_channel.c xen/include/xen/sched.h+15 -11 reply
5/8evtchn: use a per-domain variable for the max number of event channelsxen/common/event_channel.c xen/common/schedule.c xen/include/xen/event.h +1 more+8 -41 reply
6/8HACK! evtchn: increase number of buckets to support the FIFO ABIxen/include/xen/sched.h+3 -20 replies
7/8evtchn: add FIFO-based event channel ABIxen/include/public/event_channel.h+70 -02 replies
8/8evtchn: add FIFO-based event channel hypercalls and port opsxen/common/Makefile xen/common/event_channel.c xen/common/event_fifo.c +4 more+604 -59 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH RFC 0/8] Xen: FIFO-based event channel ABI

This is an RFC of the FIFO-based event channel ABI described in this design document:

http://xenbits.xen.org/people/dvrabel/event-channels-C.pdf

Changes since draft B are:

- Queue tail is now private to Xen.

- Guest pages are specified by MFN in the hypercalls.

- Updated link/unlink algorithm to avoid races when adding an event to a queue that is becoming empty.

Patch 1-5 do some preparatory work for supporting alternate ABIs.

Patch 6 is a hack to allow it to build.

Patch 7-8 add the ABI and the implementation. Patch 8 list some of the known limitations with this RFC implementation.

David