qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] io-thread optimizations
Date: Mon, 22 Aug 2011 15:20:07 -0500	[thread overview]
Message-ID: <4E52B9F7.5030906@us.ibm.com> (raw)
In-Reply-To: <cover.1314027959.git.jan.kiszka@siemens.com>

On 08/22/2011 10:46 AM, Jan Kiszka wrote:
> Rebased as requested, also fixing a compiler warning about last_io being
> write-only on !CONFIG_IOTHREAD. That "__attribute__ ((unused))" in patch
> 2 can be removed again when CONFIG_IOTHREAD becomes mandatory.

Applied all.  Thanks.

Regards,

Anthony Liguori

>
> Jan Kiszka (3):
>    Do not drop global mutex for polled main loop runs
>    Poll main loop after I/O events were received
>    Do not kick vcpus in TCG mode
>
>   cpus.c   |    2 +-
>   sysemu.h |    2 +-
>   vl.c     |   22 ++++++++++++++++------
>   3 files changed, 18 insertions(+), 8 deletions(-)
>

      parent reply	other threads:[~2011-08-22 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 15:46 [Qemu-devel] [PATCH v3 0/3] io-thread optimizations Jan Kiszka
2011-08-22 15:46 ` [Qemu-devel] [PATCH v3 1/3] Do not drop global mutex for polled main loop runs Jan Kiszka
2011-08-22 15:46 ` [Qemu-devel] [PATCH v3 2/3] Poll main loop after I/O events were received Jan Kiszka
2011-08-22 15:46 ` [Qemu-devel] [PATCH v3 3/3] Do not kick vcpus in TCG mode Jan Kiszka
2011-08-22 19:47 ` [Qemu-devel] [PATCH v3 0/3] io-thread optimizations Edgar E. Iglesias
2011-08-22 20:20 ` 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=4E52B9F7.5030906@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=jan.kiszka@siemens.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.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).