All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, lersek@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, rjones@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:23:01 +0800	[thread overview]
Message-ID: <20150722022301.GC18149@ad.nay.redhat.com> (raw)
In-Reply-To: <1437487673-23740-1-git-send-email-pbonzini@redhat.com>

On Tue, 07/21 16:07, 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

Reviewed-by: Fam Zheng <famz@redhat.com>

> 
> Paolo Bonzini (6):
>   qemu-timer: initialize "timers_done_ev" to set
>   tests: remove irrelevant assertions from test-aio
>   aio-win32: reorganize polling loop
>   AioContext: fix broken ctx->dispatching optimization
>   AioContext: fix broken placement of event_notifier_test_and_clear
>   AioContext: optimize clearing the EventNotifier
> 
>  aio-posix.c                    |  20 +++---
>  aio-win32.c                    |  48 +++++++------
>  async.c                        |  35 ++++++----
>  docs/aio_notify.promela        |  77 +++++++++------------
>  docs/aio_notify_accept.promela | 152 +++++++++++++++++++++++++++++++++++++++++
>  docs/aio_notify_bug.promela    | 140 +++++++++++++++++++++++++++++++++++++
>  include/block/aio.h            |  61 +++++++++++++++--
>  qemu-timer.c                   |   2 +-
>  tests/test-aio.c               |  26 ++-----
>  9 files changed, 441 insertions(+), 120 deletions(-)
>  create mode 100644 docs/aio_notify_accept.promela
>  create mode 100644 docs/aio_notify_bug.promela
> 
> -- 
> 2.4.3
> 
> 

  parent reply	other threads:[~2015-07-22  2:23 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 ` Fam Zheng [this message]
2015-07-22  9:41 ` [Qemu-devel] [PATCH v4 0/6] AioContext: ctx->dispatching is dead, all hail ctx->notify_me Richard W.M. Jones
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=20150722022301.GC18149@ad.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --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 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.