From: Tim Deegan <tim@xen.org>
To: Jean Guyader <jean.guyader@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH 4/5] xen: events, exposes evtchn_alloc_unbound_domain
Date: Thu, 9 Aug 2012 11:06:05 +0100 [thread overview]
Message-ID: <20120809100605.GC16986@ocelot.phlegethon.org> (raw)
In-Reply-To: <1344023454-31425-5-git-send-email-jean.guyader@citrix.com>
At 20:50 +0100 on 03 Aug (1344027053), Jean Guyader wrote:
>
> Exposes evtchn_alloc_unbound_domain to the rest of
> Xen so we can create allocated unbound evtchn within Xen.
>
> Signed-off-by: Jean Guyader <jean.guyader@citrix.com>
> @@ -161,18 +163,18 @@ static long evtchn_alloc_unbound(evtchn_alloc_unbound_t *alloc)
> {
> struct evtchn *chn;
> struct domain *d;
> - int port;
> + evtchn_port_t port;
> domid_t dom = alloc->dom;
> - long rc;
> + int rc;
The function returns long; if you're tidying this up to be an int, might
as well change the return type too.
>
> rc = rcu_lock_target_domain_by_id(dom, &d);
> if ( rc )
> return rc;
>
> - spin_lock(&d->event_lock);
> + rc = evtchn_alloc_unbound_domain(d, &port);
This moves some of the setting of channel state before the xsm hook.
Also, the state changes lower down in this function are no longer under
the event_lock. :(
Cheers,
Tim.
next prev parent reply other threads:[~2012-08-09 10:06 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 19:50 [PATCH 0/5] RFC: V4V (v3) Jean Guyader
2012-08-03 19:50 ` [PATCH 1/5] xen: add ssize_t Jean Guyader
2012-08-06 8:08 ` Jan Beulich
2012-08-06 14:47 ` Jean Guyader
2012-08-09 9:51 ` Tim Deegan
2012-08-09 10:19 ` Jean Guyader
2012-08-09 10:39 ` Jan Beulich
2012-08-09 10:48 ` Jean Guyader
2012-08-09 13:02 ` Jan Beulich
2012-08-09 10:59 ` Tim Deegan
2012-08-09 11:08 ` Jean Guyader
2012-08-03 19:50 ` [PATCH 2/5] xen: Introduce guest_handle_for_field Jean Guyader
2012-08-03 19:50 ` [PATCH 3/5] xen: virq, remove VIRQ_XC_RESERVED Jean Guyader
2012-08-06 8:10 ` Jan Beulich
2012-08-06 14:46 ` Jean Guyader
2012-08-06 14:49 ` Andrew Cooper
2012-08-06 14:56 ` Ian Campbell
2012-08-06 15:01 ` Jean Guyader
2012-08-06 15:13 ` Ian Campbell
2012-08-06 15:46 ` Jan Beulich
2012-08-03 19:50 ` [PATCH 4/5] xen: events, exposes evtchn_alloc_unbound_domain Jean Guyader
2012-08-06 8:19 ` Jan Beulich
2012-08-09 10:06 ` Tim Deegan [this message]
2012-08-09 10:23 ` Ian Campbell
2012-08-09 10:35 ` Tim Deegan
2012-08-09 10:40 ` Jean Guyader
2012-08-09 23:25 ` Jean Guyader
2012-08-10 7:35 ` Jan Beulich
2012-08-10 7:51 ` Jean Guyader
2012-08-10 7:57 ` Jan Beulich
2012-08-23 12:03 ` Jean Guyader
2012-08-03 19:50 ` [PATCH 5/5] xen: Add V4V implementation Jean Guyader
2012-08-06 8:45 ` Jan Beulich
2012-08-23 11:57 ` Jean Guyader
2012-08-24 20:06 ` Jan Beulich
2012-09-01 20:58 ` Jean Guyader
2012-09-01 20:56 ` Jean Guyader
2013-06-11 17:10 ` [PATCH 5/5] xen: Add V4V implementation - padding question Ross Philipson
2013-06-11 17:25 ` Tim Deegan
2013-06-11 17:40 ` Ross Philipson
2013-06-11 17:54 ` Ross Philipson
2013-06-11 18:04 ` Tim Deegan
2013-06-12 7:45 ` Jan Beulich
2013-06-13 17:21 ` Stefano Stabellini
2012-08-09 10:38 ` [PATCH 5/5] xen: Add V4V implementation Tim Deegan
2012-08-10 16:51 ` Jean Guyader
2012-08-13 9:38 ` Tim Deegan
2012-08-13 12:43 ` Jean Guyader
2012-08-16 12:32 ` Tim Deegan
2012-08-04 13:24 ` [PATCH 0/5] RFC: V4V (v3) Jean Guyader
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=20120809100605.GC16986@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=jean.guyader@citrix.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).