From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xen.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: [PATCHv9 00/16] Linux: FIFO-based event channel ABI
Date: Mon, 11 Nov 2013 16:12:50 +0000 [thread overview]
Message-ID: <1384186386-13937-1-git-send-email-david.vrabel@citrix.com> (raw)
This is the complete Linux guest-side implementation of the FIFO-based
event channel ABI described in this design document:
http://xenbits.xen.org/people/dvrabel/event-channels-H.pdf
The Xen implementation is now available in xen-unstable, except for
the updates for draft H.
This series is also available from:
git://xenbits.xen.org/people/dvrabel/linux.git orochi-v9
Changes in v9:
- Updates for draft H: spin on BUSY when unmasking.
Changes in v8:
- Updates for draft G: use unmask hypercall for tail events.
Changes in v7:
- Add xen.fifo_events command line option (defaults to true).
- Use xen_evtchn_nr_channels() in xen_evtchn driver.
- Drop unnecessary test in evtchn_fifo_unmask()
- Refactor irq_info setup/cleanup a bit.
Changes in v6:
- nlevel -> 2l to match naming in Xen.
Changes in v5 (v4 not posted):
- Set priority of VIRQ_TIMER.
- Remove NR_EVENT_CHANNELS limit from xen-evtchn driver.
- Licence drivers/xen/events/fifo.c under a dual MIT/GPLv2.
Changes in v3:
- Support suspend/resume by reinitializing the control blocks on resume.
- Only init control block if one does not exist (should fix CPU
hotplug).
next reply other threads:[~2013-11-11 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 16:12 David Vrabel [this message]
2013-11-11 16:12 ` [PATCH 01/16] xen/events: refactor retrigger_dynirq() and resend_irq_on_evtchn() David Vrabel
2013-11-11 16:12 ` [PATCH 02/16] xen/events: remove unnecessary init_evtchn_cpu_bindings() David Vrabel
2013-11-11 16:12 ` [PATCH 03/16] xen/events: introduce test_and_set_mask() David Vrabel
2013-11-11 16:12 ` [PATCH 04/16] xen/events: replace raw bit ops with functions David Vrabel
2013-11-11 16:12 ` [PATCH 05/16] xen/events: move drivers/xen/events.c into drivers/xen/events/ David Vrabel
2013-11-11 16:12 ` [PATCH 06/16] xen/events: move 2-level specific code into its own file David Vrabel
2013-11-11 16:12 ` [PATCH 07/16] xen/events: add struct evtchn_ops for the low-level port operations David Vrabel
2013-11-11 16:12 ` [PATCH 08/16] xen/events: allow setup of irq_info to fail David Vrabel
2013-11-11 16:12 ` [PATCH 09/16] xen/events: add a evtchn_op for port setup David Vrabel
2013-11-11 16:13 ` [PATCH 10/16] xen/events: Refactor evtchn_to_irq array to be dynamically allocated David Vrabel
2013-11-11 16:13 ` [PATCH 11/16] xen/events: add xen_evtchn_mask_all() David Vrabel
2013-11-11 16:13 ` [PATCH 12/16] xen/evtchn: support more than 4096 ports David Vrabel
2013-11-11 16:13 ` [PATCH 13/16] xen/events: Add the hypervisor interface for the FIFO-based event channels David Vrabel
2013-11-11 16:13 ` [PATCH 14/16] xen/events: allow event channel priority to be set David Vrabel
2013-11-11 16:13 ` [PATCH 15/16] xen/x86: set VIRQ_TIMER priority to maximum David Vrabel
2013-11-11 16:13 ` [PATCH 16/16] xen/events: use the FIFO-based ABI if available David Vrabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1384186386-13937-1-git-send-email-david.vrabel@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).