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, konrad.wilk@oracle.com
Cc: Wei Liu <wei.liu2@citrix.com>,
	ian.campbell@citrix.com, jbeulich@suse.com,
	david.vrabel@citrix.com
Subject: [RFC PATCH V5 10/14] xen: document 2/3-level event channel ABI
Date: Tue, 19 Mar 2013 15:22:04 +0000	[thread overview]
Message-ID: <1363706528-27141-11-git-send-email-wei.liu2@citrix.com> (raw)
In-Reply-To: <1363706528-27141-1-git-send-email-wei.liu2@citrix.com>

Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
 drivers/xen/events.c |   41 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

diff --git a/drivers/xen/events.c b/drivers/xen/events.c
index fe1831b..ee33421 100644
--- a/drivers/xen/events.c
+++ b/drivers/xen/events.c
@@ -57,6 +57,47 @@
 #include <xen/interface/sched.h>
 #include <asm/hw_irq.h>
 
+/*
+ * The 2-level (default) event channel ABI:
+ *
+ * This is the default ABI, it is guaranteed to be supported. The name
+ * comes from its 2-level lookup path.
+ *
+ * The first level is a per-cpu selector in struct vcpu_info. The size
+ * of L1 selector is sizeof(xen_ulong_t), in which each bit represents
+ * a xen_ulong_t word in the event bitmap (second level).
+ *
+ * The second level is a shared bitmap of events, embedded in shared
+ * info page.
+ *
+ * The lookup path is as followed. We first look at each bit of the L1
+ * selector. A non-zero bit in L1 selector indicates one or more bits
+ * in the corresponding word in L2 bitmap is / are set. In this case
+ * we pick up the word in bitmap, process each non-zero bit in the
+ * word and process the event.
+ *
+ *
+ * The 3-level event channel ABI:
+ *
+ * This ABI is more or less the same as the 2-level ABI. In this ABI:
+ *
+ * The first level is a per-cpu selector in struct vcpu_info. In fact,
+ * we reuse the same selector in 2-level ABI.
+ *
+ * The second level is a per-cpu bitmap of xen_ulong_t words, whose
+ * size is the same as the second level bitmap in 2-level ABI. However
+ * we cannot reuse the same bitmap in shared info page because this
+ * bitmap is per-cpu.
+ *
+ * The third level is a shared bitmap of events, which is allocated at
+ * boot time by Linux kernel.
+ *
+ * The lookup path is as followed. The first two levels lookup is the
+ * same as the 2-level ABI, but after picking up the non-zero bit in
+ * L2 selector, we still need to go down one level furthur for the
+ * actual event bit.
+ */
+
 /* extended event channel ABI in use, default is EVTCHN_EXTENDED_NONE */
 uint64_t xen_evtchn_extended = EVTCHN_EXTENDED_NONE;
 EXPORT_SYMBOL_GPL(xen_evtchn_extended);
-- 
1.7.10.4

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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 15:21 [RFC PATCH V5] Implement 3-level event channel ABI in Linux Wei Liu
2013-03-19 15:21 ` [RFC PATCH V5 01/14] xen: remove typedef in event_channel.h Wei Liu
2013-03-19 15:21 ` [RFC PATCH V5 02/14] xen: add KERN_DEBUG in printk Wei Liu
2013-03-19 15:21 ` [RFC PATCH V5 03/14] xen: fix output of xen_debug_interrupt Wei Liu
2013-03-19 15:21 ` [RFC PATCH V5 04/14] xen: sync public headers Wei Liu
2013-03-19 15:21 ` [RFC PATCH V5 05/14] xen: introduce test_and_set_mask Wei Liu
2013-03-19 15:22 ` [RFC PATCH V5 06/14] xen: replace raw bit ops with functions Wei Liu
2013-03-19 15:22 ` [RFC PATCH V5 07/14] xen: generalized event channel operations Wei Liu
2013-03-19 15:22 ` [RFC PATCH V5 08/14] xen: dynamically allocate cpu_evtchn_mask Wei Liu
2013-03-19 15:22 ` [RFC PATCH V5 09/14] xen: implement 3-level event channel routines Wei Liu
2013-03-19 15:22 ` Wei Liu [this message]
2013-03-19 15:22 ` [RFC PATCH V5 11/14] xen: introduce xen_event_channel_query_extended_abis Wei Liu
2013-03-19 15:22 ` [RFC PATCH V5 12/14] xen: introduce xen_event_channel_register_3level Wei Liu
2013-03-19 15:22 ` [RFC PATCH V5 13/14] xen: introduce xen_event_channel_register_extended Wei Liu
2013-03-19 15:22 ` [RFC PATCH V5 14/14] xen: register 3-level event channel 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=1363706528-27141-11-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=konrad.wilk@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).