All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: balbir@linux.vnet.ibm.com
Cc: Arun R Bharadwaj <arun@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/3] Introduce threadlets
Date: Tue, 19 Oct 2010 21:29:59 +0200	[thread overview]
Message-ID: <4CBDF1B7.3070908@redhat.com> (raw)
In-Reply-To: <20101019191225.GJ15844@balbir.in.ibm.com>

On 10/19/2010 09:12 PM, Balbir Singh wrote:
> > >Ideally you need
> > >
> > >           s = pthread_setcancelstate(PTHREAD_CANCEL_DISABLE, NULL);
> > >
> > > But qemu will need to wrap this around as well.
> >
> >  Why?  QEMU is never using thread cancellation.
>
> Yes, I agree, in the longer run, cancellation is a good way to kill
> threads, specially in a thread pool. My comment was more along the
> lines of good practices and potential use of pthread_cancel(), not a
> strict comment on something urgent or broken.

But there is no such use; as long as we keep ourselves to the 
qemu-thread API, we know that nothing will use cancellation.

The day qemu-thread will introduce cancellation functions we'll care 
about enabling/disabling it in some threads.

Paolo

  reply	other threads:[~2010-10-19 19:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 17:42 [Qemu-devel] v6: [PATCH 0/3]: Threadlets: A generic task offloading framework Arun R Bharadwaj
2010-10-19 17:42 ` [Qemu-devel] [PATCH 1/3] Introduce threadlets Arun R Bharadwaj
2010-10-19 18:36   ` Balbir Singh
2010-10-19 19:01     ` [Qemu-devel] " Paolo Bonzini
2010-10-19 19:12       ` Balbir Singh
2010-10-19 19:29         ` Paolo Bonzini [this message]
2010-10-19 21:00     ` [Qemu-devel] " Venkateswararao Jujjuri (JV)
2010-10-20  2:26       ` Balbir Singh
2010-10-19 21:36     ` Anthony Liguori
2010-10-20  2:22       ` Balbir Singh
2010-10-20  3:46         ` Venkateswararao Jujjuri (JV)
2010-10-20 13:05           ` Balbir Singh
2010-10-20 13:13         ` Anthony Liguori
2010-10-20  3:19       ` Venkateswararao Jujjuri (JV)
2010-10-20  8:16   ` Stefan Hajnoczi
2010-10-19 17:43 ` [Qemu-devel] [PATCH 2/3] Make paio subsystem use threadlets Arun R Bharadwaj
2010-10-20  2:24   ` Balbir Singh
2010-10-20  8:42   ` Kevin Wolf
2010-10-20  9:30   ` Stefan Hajnoczi
2010-10-20 13:16     ` Anthony Liguori
2010-10-21  8:40     ` Arun R Bharadwaj
2010-10-21  9:17       ` Stefan Hajnoczi
2010-10-19 17:43 ` [Qemu-devel] [PATCH 3/3] Add helper functions for virtio-9p to " Arun R Bharadwaj
2010-10-20 11:19   ` Stefan Hajnoczi
2010-10-20 13:17     ` Anthony Liguori
2010-10-20 11:57 ` [Qemu-devel] v6: [PATCH 0/3]: Threadlets: A generic task offloading framework Amit Shah
2010-10-20 12:05   ` Stefan Hajnoczi
2010-10-20 13:18     ` Anthony Liguori
2010-10-22  9:59       ` Amit Shah
2010-10-23 12:05         ` Stefan Hajnoczi
2010-10-27  7:57           ` Amit Shah
2010-10-27  8:37             ` Stefan Hajnoczi
  -- strict thread matches above, loose matches on Subject: below --
2010-10-13 15:30 [Qemu-devel] v5 [PATCH 0/3] qemu: " Arun R Bharadwaj
2010-10-13 15:31 ` [Qemu-devel] [PATCH 1/3] Introduce threadlets Arun R Bharadwaj
2010-10-14  9:02   ` Stefan Hajnoczi
2010-10-15 14:42     ` [Qemu-devel] " 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=4CBDF1B7.3070908@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arun@linux.vnet.ibm.com \
    --cc=balbir@linux.vnet.ibm.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.