All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] Spread the use of QEMU threading & locking API
Date: Wed, 04 Apr 2012 17:18:22 +0200	[thread overview]
Message-ID: <4F7C663E.20200@redhat.com> (raw)
In-Reply-To: <cover.1333552093.git.jan.kiszka@siemens.com>

Il 04/04/2012 17:08, Jan Kiszka ha scritto:
> Refreshed versions of some cleanups I already sent last year. See
> patches for details.

Patches 1, 2 and 5 are fine.  I had an alternative implementation using
a counting semaphore instead of the condition variable (which would work
on Windows too), but I can rebase later if ever.

For patches 3 and 4, I'd rather use an EventNotifier...

Paolo

> The series also helps using different scheduling policies for QEMU
> threads which includes hardening internal locks.
> 
> Jan Kiszka (5):
>   Introduce qemu_cond_timedwait for POSIX
>   Switch POSIX compat AIO to QEMU abstractions
>   Use qemu_eventfd for POSIX AIO
>   Reorder POSIX compat AIO code
>   Switch compatfd to QEMU thread
> 
>  compatfd.c          |   16 +----
>  posix-aio-compat.c  |  162 +++++++++++++++++----------------------------------
>  qemu-thread-posix.c |   23 +++++++
>  qemu-thread-posix.h |    5 ++
>  4 files changed, 84 insertions(+), 122 deletions(-)
> 

  parent reply	other threads:[~2012-04-04 15:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 15:08 [Qemu-devel] [PATCH 0/5] Spread the use of QEMU threading & locking API Jan Kiszka
2012-04-04 15:08 ` [Qemu-devel] [PATCH 1/5] Introduce qemu_cond_timedwait for POSIX Jan Kiszka
2012-04-04 15:08 ` [Qemu-devel] [PATCH 2/5] Switch POSIX compat AIO to QEMU abstractions Jan Kiszka
2012-04-04 15:08 ` [Qemu-devel] [PATCH 3/5] Use qemu_eventfd for POSIX AIO Jan Kiszka
2012-04-04 15:08 ` [Qemu-devel] [PATCH 4/5] Reorder POSIX compat AIO code Jan Kiszka
2012-04-04 15:08 ` [Qemu-devel] [PATCH 5/5] Switch compatfd to QEMU thread Jan Kiszka
2012-04-04 15:18 ` Paolo Bonzini [this message]
2012-04-04 15:24   ` [Qemu-devel] [PATCH 0/5] Spread the use of QEMU threading & locking API Jan Kiszka
2012-04-04 15:29     ` Paolo Bonzini
2012-04-04 15:38       ` Jan Kiszka
2012-04-04 15:43         ` Jan Kiszka
2012-04-04 16:05       ` Jan Kiszka
2012-04-04 16:39         ` Paolo Bonzini
2012-04-04 16:55           ` Jan Kiszka
2012-04-04 17:19             ` Jan Kiszka
2012-04-05  7:51               ` Paolo Bonzini
2012-04-05 10:55                 ` Jan Kiszka
2012-04-05 11:07                   ` Paolo Bonzini
2012-04-05 11:18                     ` Jan Kiszka
2012-04-05 11:29                       ` Paolo Bonzini
2012-04-05 12:04                         ` Jan Kiszka
2012-04-05 12:48                           ` Paolo Bonzini
     [not found]                             ` <4F7D977A.1020905@siemens.com>
2012-04-05 13:40                               ` Paolo Bonzini
2012-04-05 14:01                                 ` Jan Kiszka
2012-04-05 14:11                                   ` Paolo Bonzini

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=4F7C663E.20200@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kwolf@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 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.