All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Spawning threads in KVM/QEMU
Date: Tue, 13 Nov 2007 14:15:18 -0600	[thread overview]
Message-ID: <473A05D6.2040003@us.ibm.com> (raw)

Hi,

I've been experimenting with creating IO threads for the PV device 
drivers.  Unfortunately, my experiments haven't gotten very far as QEMU 
tends to hang up a bit into booting the guest whenever I spawn a thread 
that does any sort of read/write on a file descriptor.  My suspicion is 
that it has something to do with signals being delivered to the wrong 
thread but after masking out all the signals for this thread, I still 
had no luck.

Any clues to what may be going on?

Regards,

Anthony Liguori

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

             reply	other threads:[~2007-11-13 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 20:15 Anthony Liguori [this message]
     [not found] ` <473A05D6.2040003-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-11-13 22:42   ` Spawning threads in KVM/QEMU Dor Laor
     [not found]     ` <473A283B.5040905-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-13 23:08       ` Luca Tettamanti
     [not found]         ` <68676e00711131508l4cb1cafajd559ca804d61b3c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-14  9:37           ` Dor Laor
2007-11-14  9:43       ` Avi Kivity

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=473A05D6.2040003@us.ibm.com \
    --to=aliguori-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.