All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Jan Kiszka <jan.kiszka@siemens.com>, Peter Lieven <pl@dlh.net>,
	qemu-devel <qemu-devel@nongnu.org>,
	kvm@vger.kernel.org,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] vnc: don't mess up with iohandlers in the vnc thread
Date: Thu, 10 Mar 2011 14:58:21 +0100	[thread overview]
Message-ID: <4D78D8FD.9070006@redhat.com> (raw)
In-Reply-To: <AANLkTi=WOPJ3eLAbTgYvStfbspahMzT3jUbroH2P2fUd@mail.gmail.com>

On 03/10/2011 02:54 PM, Corentin Chary wrote:
> > >  You can use a bottom half for this instead of a special socket. Signaling
> > >  a bottom half is async-signal- and thread-safe.
> >
> >  Bottom halves are thread safe?
> >
> >  I don't think so.
>
> The bottom halves API is not thread safe, but calling
> qemu_bh_schedule_idle()

Not _idle please.

> in another thread *seems* to be safe (here, it
> would be protected from qemu_bh_delete() by vnc_lock_output()).

If it weren't protected against qemu_bh_delete, you would have already 
the same race between writing to the socket and closing it in another 
thread.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	Peter Lieven <pl@dlh.net>
Subject: [Qemu-devel] Re: [PATCH 2/2] vnc: don't mess up with iohandlers in the vnc thread
Date: Thu, 10 Mar 2011 14:58:21 +0100	[thread overview]
Message-ID: <4D78D8FD.9070006@redhat.com> (raw)
In-Reply-To: <AANLkTi=WOPJ3eLAbTgYvStfbspahMzT3jUbroH2P2fUd@mail.gmail.com>

On 03/10/2011 02:54 PM, Corentin Chary wrote:
> > >  You can use a bottom half for this instead of a special socket. Signaling
> > >  a bottom half is async-signal- and thread-safe.
> >
> >  Bottom halves are thread safe?
> >
> >  I don't think so.
>
> The bottom halves API is not thread safe, but calling
> qemu_bh_schedule_idle()

Not _idle please.

> in another thread *seems* to be safe (here, it
> would be protected from qemu_bh_delete() by vnc_lock_output()).

If it weren't protected against qemu_bh_delete, you would have already 
the same race between writing to the socket and closing it in another 
thread.

Paolo

  reply	other threads:[~2011-03-10 13:58 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 22:53 segmentation fault in qemu-kvm-0.14.0 Peter Lieven
2011-03-08 22:53 ` [Qemu-devel] " Peter Lieven
2011-03-09  7:13 ` Corentin Chary
2011-03-09  7:26 ` Stefan Weil
2011-03-09  7:26   ` Stefan Weil
2011-03-09  7:39   ` Michael Tokarev
2011-03-09  7:39     ` Michael Tokarev
2011-03-09  9:22     ` Stefan Weil
2011-03-09  9:22       ` Stefan Weil
2011-03-09 10:00   ` Peter Lieven
2011-03-09 10:00     ` Peter Lieven
2011-03-15 12:53   ` Peter Lieven
2011-03-15 12:53     ` Peter Lieven
2011-03-15 18:52     ` Stefan Weil
2011-03-15 18:52       ` Stefan Weil
2011-03-09  7:37 ` Jan Kiszka
2011-03-09  7:37   ` [Qemu-devel] " Jan Kiszka
2011-03-09  8:50   ` Corentin Chary
2011-03-09  9:04     ` Jan Kiszka
2011-03-09  9:54       ` Corentin Chary
2011-03-09  9:58         ` Jan Kiszka
2011-03-09 10:02           ` Jan Kiszka
2011-03-09 10:06             ` Corentin Chary
2011-03-09 10:12               ` Jan Kiszka
2011-03-09 10:14                 ` Corentin Chary
2011-03-09 10:17                   ` Jan Kiszka
2011-03-09 10:41                     ` [PATCH] vnc: threaded server depends on io-thread Corentin Chary
2011-03-09 10:41                       ` [Qemu-devel] " Corentin Chary
2011-03-09 10:50                       ` Peter Lieven
2011-03-09 10:50                         ` [Qemu-devel] " Peter Lieven
2011-03-09 10:57                         ` Corentin Chary
2011-03-09 10:57                           ` [Qemu-devel] " Corentin Chary
2011-03-09 11:05                           ` Stefan Hajnoczi
2011-03-09 11:05                             ` [Qemu-devel] " Stefan Hajnoczi
2011-03-09 11:25                             ` Jan Kiszka
2011-03-09 11:25                               ` [Qemu-devel] " Jan Kiszka
2011-03-09 11:32                               ` Peter Lieven
2011-03-09 11:32                                 ` [Qemu-devel] " Peter Lieven
2011-03-09 11:33                                 ` Jan Kiszka
2011-03-09 11:33                                   ` [Qemu-devel] " Jan Kiszka
2011-03-09 11:42                       ` Jan Kiszka
2011-03-09 11:42                         ` [Qemu-devel] " Jan Kiszka
2011-03-09 12:50                         ` Peter Lieven
2011-03-09 12:50                           ` [Qemu-devel] " Peter Lieven
2011-03-09 13:21                         ` [PATCH v2] " Corentin Chary
2011-03-09 13:21                           ` [Qemu-devel] " Corentin Chary
2011-03-09 13:42                           ` Corentin Chary
2011-03-09 13:42                             ` [Qemu-devel] " Corentin Chary
2011-03-09 13:51                           ` Paolo Bonzini
2011-03-09 13:51                             ` [Qemu-devel] " Paolo Bonzini
2011-03-09 13:59                             ` Corentin Chary
2011-03-09 13:59                               ` [Qemu-devel] " Corentin Chary
2011-03-10 12:59                         ` [PATCH 1/2] sockets: add qemu_socketpair() Corentin Chary
2011-03-10 12:59                           ` [Qemu-devel] " Corentin Chary
2011-03-10 12:59                         ` [PATCH 2/2] vnc: don't mess up with iohandlers in the vnc thread Corentin Chary
2011-03-10 12:59                           ` [Qemu-devel] " Corentin Chary
2011-03-10 13:06                           ` Paolo Bonzini
2011-03-10 13:06                             ` [Qemu-devel] " Paolo Bonzini
2011-03-10 13:45                             ` Anthony Liguori
2011-03-10 13:45                               ` [Qemu-devel] " Anthony Liguori
2011-03-10 13:54                               ` Corentin Chary
2011-03-10 13:54                                 ` [Qemu-devel] " Corentin Chary
2011-03-10 13:58                                 ` Paolo Bonzini [this message]
2011-03-10 13:58                                   ` Paolo Bonzini
2011-03-10 13:56                               ` Paolo Bonzini
2011-03-10 13:56                                 ` [Qemu-devel] " Paolo Bonzini
2011-03-10 13:47                           ` Peter Lieven
2011-03-10 13:47                             ` [Qemu-devel] " Peter Lieven
2011-03-10 15:13                         ` [PATCH v5] " Corentin Chary
2011-03-10 15:13                           ` [Qemu-devel] " Corentin Chary
2011-03-14  9:19                           ` Corentin Chary
2011-03-14  9:19                             ` [Qemu-devel] " Corentin Chary
2011-03-14  9:55                             ` Peter Lieven
2011-03-14  9:55                               ` [Qemu-devel] " Peter Lieven
2011-03-15 16:55                             ` Peter Lieven
2011-03-15 16:55                               ` [Qemu-devel] " Peter Lieven
2011-03-15 18:07                               ` Peter Lieven
2011-03-15 18:07                                 ` [Qemu-devel] " Peter Lieven
2011-03-09 10:02   ` segmentation fault in qemu-kvm-0.14.0 Peter Lieven
2011-03-09 10:02     ` [Qemu-devel] " Peter Lieven
2011-03-09 10:16   ` Peter Lieven
2011-03-09 10:16     ` [Qemu-devel] " Peter Lieven
2011-03-09 10:20     ` Jan Kiszka
2011-03-09 10:20       ` [Qemu-devel] " Jan Kiszka
2011-03-09 10:31       ` Peter Lieven
2011-03-09 10:31         ` [Qemu-devel] " Peter Lieven
2011-03-09 11:20   ` Paolo Bonzini
2011-03-09 11:20     ` [Qemu-devel] " Paolo Bonzini
2011-03-09 11:44     ` Jan Kiszka
2011-03-09 11:44       ` [Qemu-devel] " Jan Kiszka

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=4D78D8FD.9070006@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=corentin.chary@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=pl@dlh.net \
    --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.