qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, famz@redhat.com, lersek@redhat.com,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 0/6] AioContext: ctx->dispatching is dead, all hail ctx->notify_me
Date: Wed, 22 Jul 2015 10:41:34 +0100	[thread overview]
Message-ID: <20150722094134.GC29283@redhat.com> (raw)
In-Reply-To: <1437487673-23740-1-git-send-email-pbonzini@redhat.com>

On Tue, Jul 21, 2015 at 04:07:47PM +0200, Paolo Bonzini wrote:
> This puts together all pending fixes in a single series.
> 
> Paolo
> 
> v1->v2
>         Split some changes to the tests to a separate patch
>         Fix commit message [Laszlo]
>         Clarify do...while loop in aio-win32.c [Kevin]
> 
> v2->v3
>         Decrement notify_me a little earlier in aio-posix.c.
> 
> v3->v4
>         Include 'qemu-timer: initialize "timers_done_ev" to set' [Peter]
>         Include fix and optimization for broken event_notifier_test_and_clear

I ran this overnight through many iterations with no problems seen.

Therefore:

Tested-by: Richard W.M. Jones <rjones@redhat.com>

Rich.

----------------------------------------------------------------------

$ while true; do echo -n .; LIBGUESTFS_HV=/home/rjones/d/qemu/aarch64-softmmu/qemu-system-aarch64 ./run ./heisenscsi.pl ; done
...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................^C



-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

  parent reply	other threads:[~2015-07-22  9:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 14:07 [Qemu-devel] [PATCH v4 0/6] AioContext: ctx->dispatching is dead, all hail ctx->notify_me Paolo Bonzini
2015-07-21 14:07 ` [Qemu-devel] [PATCH v4 1/6] qemu-timer: initialize "timers_done_ev" to set Paolo Bonzini
2015-07-21 14:07 ` [Qemu-devel] [PATCH v4 2/6] tests: remove irrelevant assertions from test-aio Paolo Bonzini
2015-07-21 14:07 ` [Qemu-devel] [PATCH v4 3/6] aio-win32: reorganize polling loop Paolo Bonzini
2015-07-21 14:07 ` [Qemu-devel] [PATCH v4 4/6] AioContext: fix broken ctx->dispatching optimization Paolo Bonzini
2015-07-21 14:07 ` [Qemu-devel] [PATCH v4 5/6] AioContext: fix broken placement of event_notifier_test_and_clear Paolo Bonzini
2015-07-21 14:07 ` [Qemu-devel] [PATCH v4 6/6] AioContext: optimize clearing the EventNotifier Paolo Bonzini
2015-07-22  2:23 ` [Qemu-devel] [PATCH v4 0/6] AioContext: ctx->dispatching is dead, all hail ctx->notify_me Fam Zheng
2015-07-22  9:41 ` Richard W.M. Jones [this message]
2015-07-22 11:39 ` 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=20150722094134.GC29283@redhat.com \
    --to=rjones@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lersek@redhat.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).