From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
"jeremy@goop.org" <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH 1/3] xen/event: Add reference counting to event channels
Date: Wed, 26 Oct 2011 13:28:03 -0400 [thread overview]
Message-ID: <4EA84323.4000108@tycho.nsa.gov> (raw)
In-Reply-To: <1319647887.9436.55.camel@zakaz.uk.xensource.com>
On 10/26/2011 12:51 PM, Ian Campbell wrote:
> On Wed, 2011-10-26 at 16:47 +0100, Daniel De Graaf wrote:
>> @@ -939,6 +943,10 @@ static void unbind_from_irq(unsigned int irq)
>> {
>> struct evtchn_close close;
>> int evtchn = evtchn_from_irq(irq);
>> + struct irq_info *info = irq_get_handler_data(irq);
>> +
>> + if (atomic_read(&info->refcnt) > 0 && !atomic_dec_and_test(&info->refcnt))
>> + return;
>
> This isn't all that atomic any more...
>
> evtchn_make_refcounted() doesn't seem to have any locking which would
> save you...
>
> Perhaps you could always manipulate this flag under the mapping lock
> (which perhaps is normally taken around about the sort of place you'd
> want to do this anyway) and make it non-atomic?
>
> Or maybe you could build something with cmpxchg?
>
> Ian.
>
It's atomic for the cases where it needs to be. There are two cases in which
unbind_from_irq can be called:
1. Negative refcnt (to be exact, == -1). This is an internal reference, and
unbind_from_irq is only called once as guaranteed by the caller.
2. Positive refcnt. Once refcnt has been changed to positive, it cannot be
changed back, so "atomic_read(&info->refcnt) > 0" will always be true, for
any number of parallel callers, assuming all callers had a reference to begin
with. In this case, only the atomic_dec_and_test needs atomicity to resolve
the race when parallel callers are running evtchn_put.
The conversion from -1 to positive refcnt is done during the creation of the
event channel, before multiple references to the event channel are allowed.
There is also no way to convert an event channel from positive to negative
(without destroying it completely) so a race from that conversion is also
not possible.
I considered using atomic_dec_if_positive here, but as the existing condition
has no races this is unnecessary.
Should this explanation be copied into a comment to avoid future confusion?
--
Daniel De Graaf
National Security Agency
next prev parent reply other threads:[~2011-10-26 17:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 21:14 [PATCH 0/2] Add reference counting to grant notify ioctls Daniel De Graaf
2011-09-16 21:14 ` [PATCH 1/2] xen/event: Add reference counting to event channel Daniel De Graaf
2011-09-17 4:50 ` Jeremy Fitzhardinge
2011-09-17 6:11 ` Keir Fraser
2011-09-19 15:50 ` Daniel De Graaf
2011-09-19 16:22 ` Jeremy Fitzhardinge
2011-09-19 17:53 ` Daniel De Graaf
2011-09-16 21:14 ` [PATCH 2/2] xen/gnt{dev, alloc}: reserve event channels for notify Daniel De Graaf
2011-10-18 21:04 ` [PATCH v2 0/2] Add reference counting to grant notify ioctls Daniel De Graaf
2011-10-18 21:04 ` [PATCH 1/2] xen/event: Add reference counting to event channel Daniel De Graaf
2011-10-19 9:20 ` Ian Campbell
2011-10-24 20:22 ` Konrad Rzeszutek Wilk
2011-10-24 22:20 ` Daniel De Graaf
2011-10-25 19:05 ` Konrad Rzeszutek Wilk
2011-10-25 8:17 ` Ian Campbell
2011-10-25 19:09 ` Konrad Rzeszutek Wilk
2011-10-25 20:44 ` Ian Campbell
2011-10-18 21:04 ` [PATCH 2/2] xen/gnt{dev, alloc}: reserve event channels for notify Daniel De Graaf
2011-10-19 9:24 ` Ian Campbell
2011-10-19 14:23 ` Daniel De Graaf
2011-10-19 14:45 ` [PATCH 2/2] xen/gnt{dev,alloc}: " Ian Campbell
2011-10-24 20:57 ` [PATCH 2/2] xen/gnt{dev, alloc}: " Konrad Rzeszutek Wilk
2011-10-24 22:01 ` Daniel De Graaf
2011-10-25 19:02 ` Konrad Rzeszutek Wilk
2011-10-25 19:41 ` Daniel De Graaf
2011-10-25 19:51 ` Konrad Rzeszutek Wilk
2011-10-25 20:27 ` Ian Campbell
2011-10-25 20:42 ` Daniel De Graaf
2011-10-25 20:50 ` Ian Campbell
2011-10-25 21:07 ` Daniel De Graaf
2011-10-26 15:47 ` [PATCH v3 0/3] Add reference counting to grant notify ioctls Daniel De Graaf
2011-10-26 15:47 ` [PATCH 1/3] xen/event: Add reference counting to event channels Daniel De Graaf
2011-10-26 16:51 ` Ian Campbell
2011-10-26 16:57 ` Ian Campbell
2011-10-26 17:28 ` Daniel De Graaf [this message]
2011-10-27 9:03 ` Ian Campbell
2011-10-26 18:42 ` [PATCH 1/3 v3.2] " Daniel De Graaf
2011-10-26 15:47 ` [PATCH 2/3] xen/gntalloc: Change gref_lock to a mutex Daniel De Graaf
2011-10-26 15:47 ` [PATCH 3/3] xen/gnt{dev, alloc}: reserve event channels for notify Daniel De Graaf
2011-10-27 21:58 ` [PATCH v4 0/3] Add reference counting to grant notify ioctls Daniel De Graaf
2011-10-27 21:58 ` [PATCH 1/3] xen/event: Add reference counting to event channels Daniel De Graaf
2011-10-27 21:58 ` [PATCH 2/3] xen/gntalloc: Change gref_lock to a mutex Daniel De Graaf
2011-10-27 21:58 ` [PATCH 3/3] xen/gnt{dev, alloc}: reserve event channels for notify Daniel De Graaf
2011-11-11 20:33 ` [PATCH v4 0/3] Add reference counting to grant notify ioctls Konrad Rzeszutek Wilk
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=4EA84323.4000108@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.