From: Ross Philipson <ross.philipson@citrix.com>
To: xen-devel@lists.xen.org
Cc: dgdegra@tycho.nsa.gov
Subject: XSM dummy policy blocking event channel creation
Date: Wed, 1 May 2013 15:40:25 -0400 [thread overview]
Message-ID: <51816FA9.9020402@citrix.com> (raw)
I am working on the next set of V4V patches to post to the list. I have
pulled the very latest staging branch of Xen and I quickly ran into a
new problem. We are basically trying to create an event channel during
the creation of dom0. We have split up the evtchn_alloc_unbound()
function into two functions but the basic problem is the same. The call
to xsm_evtchn_unbound() is returning -EPERM from the new code in
xsm/dummy.h. This patch set added this functionality:
http://lists.xen.org/archives/html/xen-devel/2012-11/msg01920.html
Specifically we are failing this part of the test return -EPERM:
static always_inline int xsm_default_action(
xsm_default_t action, struct domain *src, struct domain *target)
{
...
case XSM_TARGET:
if ( src != target && !IS_PRIV_FOR(src, target) )
return -EPERM;
The src domain is the current->domain which is idle_domain and target is
dom0 which is in the process of being created. Neither of them is
privileged (dom0 is not set to privileged yet). And I have not gotten
past dom0 creation yet so I don't know what will happen when V4V tries
to initialize for domU's.
I need some advice on how to proceed here. I am not terribly conversant
in the working of XSM and do not have a clear idea how to proceed.
Thanks,
Ross Philipson
next reply other threads:[~2013-05-01 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:40 Ross Philipson [this message]
2013-05-01 20:50 ` XSM dummy policy blocking event channel creation Daniel De Graaf
2013-05-01 21:09 ` Ross Philipson
2013-05-01 22:02 ` Daniel De Graaf
2013-05-02 14:23 ` Ross Philipson
2013-05-02 15:10 ` Daniel De Graaf
2013-05-02 15:37 ` Ross Philipson
2013-05-02 16:03 ` Daniel De Graaf
2013-05-03 13:14 ` Ross Philipson
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=51816FA9.9020402@citrix.com \
--to=ross.philipson@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.