qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC v2 2/6] aio: add aio_context_acquire() and aio_context_release()
Date: Thu, 20 Feb 2014 13:45:30 +0100	[thread overview]
Message-ID: <20140220124530.GB15847@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20140120102950.GB5727@T430.nay.redhat.com>

On Mon, Jan 20, 2014 at 06:29:50PM +0800, Fam Zheng wrote:
> On Fri, 01/10 09:45, Stefan Hajnoczi wrote:
> > +/* Take ownership of the AioContext.  If the AioContext will be shared between
> > + * threads, a thread must have ownership when calling aio_poll().
> > + *
> > + * Note that multiple threads calling aio_poll() means timers, BHs, and
> > + * callbacks may be invoked from a different thread than they were registered
> > + * from.  Therefore, code must use AioContext acquire/release or use
> > + * fine-grained synchronization to protect shared state if other threads will
> > + * be accessing it simultaneously.
> > + */
> > +void aio_context_acquire(AioContext *ctx);
> > +
> > +/* Reliquinish ownership of the AioContext. */
> 
> s/Reliquinish/Relinquish/

Fixed in next version.

  reply	other threads:[~2014-02-20 12:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10  1:45 [Qemu-devel] [RFC v2 0/6] dataplane: switch to N:M devices-per-thread model Stefan Hajnoczi
2014-01-10  1:45 ` [Qemu-devel] [RFC v2 1/6] rfifolock: add recursive FIFO lock Stefan Hajnoczi
2014-01-20 10:22   ` Fam Zheng
2014-02-20 12:45     ` Stefan Hajnoczi
2014-01-10  1:45 ` [Qemu-devel] [RFC v2 2/6] aio: add aio_context_acquire() and aio_context_release() Stefan Hajnoczi
2014-01-20 10:29   ` Fam Zheng
2014-02-20 12:45     ` Stefan Hajnoczi [this message]
2014-01-10  1:45 ` [Qemu-devel] [RFC v2 3/6] iothread: add I/O thread object Stefan Hajnoczi
2014-01-10  1:45 ` [Qemu-devel] [RFC v2 4/6] qdev: add get_pointer_and_free() for temporary strings Stefan Hajnoczi
2014-01-10  1:45 ` [Qemu-devel] [RFC v2 5/6] iothread: add "iothread" qdev property type Stefan Hajnoczi
2014-01-10  1:45 ` [Qemu-devel] [RFC v2 6/6] dataplane: replace internal thread with IOThread Stefan Hajnoczi

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=20140220124530.GB15847@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=famz@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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).