From: Anthony Liguori <aliguori@us.ibm.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Two signalfd_compat threads created: remove one
Date: Mon, 22 Sep 2008 09:49:20 -0500 [thread overview]
Message-ID: <48D7B070.2020107@us.ibm.com> (raw)
In-Reply-To: <f43fc5580809200712lc47e2f7q3e6e1a7a431b73b1@mail.gmail.com>
Blue Swirl wrote:
> Hi,
>
> Function qemu_aio_init() is called from both vl.c and block.c. This
> means that two threads handling signalfd_compat are created. This
> patch removes the call from vl.c.
>
Thanks for catching this. I committed a slightly different patch. We
already go through the trouble of maintaining an aio_initialized
variable so I added a simple check to short-cut the aio_init function if
we've already been initialized. Your patch isn't necessary a bad one
though since it's already called from bdrv_init. Please commit.
Regards,
Anthony Liguori
prev parent reply other threads:[~2008-09-22 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 14:12 [Qemu-devel] Two signalfd_compat threads created: remove one Blue Swirl
2008-09-22 14:49 ` Anthony Liguori [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=48D7B070.2020107@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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).