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: Wei Liu <wei.liu2@citrix.com>,
	david.vrabel@citrix.com, jbeulich@suse.com,
	ian.campbell@citrix.com
Subject: [RFC PATCH V5 15/15] evtchn: only allow 3-level event channel on Dom0
Date: Tue, 19 Mar 2013 15:15:40 +0000	[thread overview]
Message-ID: <1363706140-26989-16-git-send-email-wei.liu2@citrix.com> (raw)
In-Reply-To: <1363706140-26989-1-git-send-email-wei.liu2@citrix.com>

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

diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
index 0f9e8e4..f48c3a2 100644
--- a/xen/common/event_channel.c
+++ b/xen/common/event_channel.c
@@ -1118,7 +1118,10 @@ long do_event_channel_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
 
     case EVTCHNOP_query_extended_abis: {
         struct evtchn_query_extended_abis query;
+        struct domain *d = current->domain;
         query.abis = extended_event_channel;
+        if ( d->domain_id != 0 )
+            query.abis &= ~EVTCHN_EXTENDED_L3;
         rc = 0;
         if ( __copy_to_guest(arg, &query, 1) )
             rc = -EFAULT;
@@ -1127,6 +1130,9 @@ long do_event_channel_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
 
     case EVTCHNOP_register_3level: {
         struct evtchn_register_3level reg;
+        struct domain *d = current->domain;
+        if ( d->domain_id != 0 )
+            return -EPERM;
         if ( copy_from_guest(&reg, arg, 1) != 0 )
             return -EFAULT;
         rc = evtchn_register_3level(&reg);
-- 
1.7.10.4

      parent 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 [RFC PATCH V5 00/15] Implement 3-level event channel ABI in Xen Wei Liu
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 ` Wei Liu [this message]

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-16-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).