xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xen.org
Cc: david.vrabel@citrix.com, jbeulich@suse.com, ian.campbell@citrix.com
Subject: [RFC PATCH V5 00/15] Implement 3-level event channel ABI in Xen
Date: Tue, 19 Mar 2013 15:15:25 +0000	[thread overview]
Message-ID: <1363706140-26989-1-git-send-email-wei.liu2@citrix.com> (raw)

This is the 5th RFC series (in fact 6th because I dropped RFC in one of the
series I posted) for the 3-level event channel design.

Changes since V4:
* Rework internal event channel object store to optimize memory usage.
* Switch back to function pointers, because it has the same (or less)
  performance degradation compared to 'switch' statement, while at the same
  time it allows for clearer code structure.
* Separate internal event channel inteface and ABI implementation.
* Only enable 3-level event channel for Dom0, this should be a good starting
  point for testing. The toolstack integration is left open.
* A compat shim is missing, but should be trivial to add.

Changes since V3:
* Dedicated EVTCHNOP for extended ABI query
* Dedicated EVTCHNOP for 3-level ABI registration
* 3-level ABI is registered in two phases:
  * register the bitmaps
  * register per-cpu L2 selector
* libxl: evtchn_extended -> evtchn_extended_allowed

Changes since V2:
* new interface to register extended event channel ABI
* use vmap to simplify mapping
* replace MAX_EVTCHNS macro with inline function
* libxl: evtchn_l3 -> evtchn_extended

The most notable bit of this series is the interface change. In order to cope
with future ABIs, the interface is renamed to EVTCHNOP_register_extended. It
also provides supported ABI query, so that we can remove unused ABI in the
future.

The semantic meaning of EVTCHNOP_register_extended changes a bit. The `level'
in parameter now changes to `cmd', which means we should go down to specific
ABI routines. ABI-specific structures are still embedded in the union.

Changes since V1:
* move all evtchn related macros / struct definitions to event.h
* only allow 3-level evtchn for Dom0 and driver domains
* add evtchn_l3 flag in libxl


Diffstat:
 xen/arch/arm/domain.c              |    1 +
 xen/arch/x86/domain.c              |    1 +
 xen/arch/x86/irq.c                 |    7 +-
 xen/common/Makefile                |    1 +
 xen/common/event_channel.c         |  404 +++++++++++++++++++++++++-----------
 xen/common/evtchn_bitmap_abi.c     |  323 ++++++++++++++++++++++++++++
 xen/common/keyhandler.c            |    6 +-
 xen/common/schedule.c              |    4 +-
 xen/include/asm-arm/config.h       |    1 +
 xen/include/asm-x86/config.h       |    5 +-
 xen/include/public/event_channel.h |   48 +++++
 xen/include/public/xen.h           |   35 ++--
 xen/include/xen/event.h            |   70 ++++++-
 xen/include/xen/sched.h            |   31 ++-
 14 files changed, 779 insertions(+), 158 deletions(-)

             reply	other threads:[~2013-03-19 15:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 15:15 Wei Liu [this message]
2013-03-19 15:15 ` [RFC PATCH V5 01/15] Clean up trailing whitespaces Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 02/15] evtchn: reset bucket if xsm_alloc_security_evtchn fails Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 03/15] evtchn: alter internal object handling scheme Wei Liu
2013-03-20  9:22   ` Jan Beulich
2013-03-19 15:15 ` [RFC PATCH V5 04/15] evtchn: generalize event channel operations Wei Liu
2013-03-20  9:31   ` Jan Beulich
2013-03-19 15:15 ` [RFC PATCH V5 05/15] evtchn: add d->max_evtchns Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 06/15] evtchn: implement extended event channel ABIs query Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 07/15] evtchn: define 3-level event channel registration interface Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 08/15] evtchn: add evtchn_extended in struct domain Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 09/15] evtchn: calculate max event channels for EVTCHN_EXTENDED_L3 Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 10/15] evtchn: update Xen public header xen.h Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 11/15] evtchn: use pointers to reference evtchn_pending/mask Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 12/15] evtchn: introduce EVTCHN_WORD_BITORDER macro Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 13/15] evtchn: infrastructure to manipulate 3-level event channel pages Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 14/15] evtchn: implement 3-level event channel routines Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 15/15] evtchn: only allow 3-level event channel on Dom0 Wei Liu

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=1363706140-26989-1-git-send-email-wei.liu2@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.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).