public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: Spawning threads in KVM/QEMU
Date: Wed, 14 Nov 2007 11:37:58 +0200	[thread overview]
Message-ID: <473AC1F6.7030007@qumranet.com> (raw)
In-Reply-To: <68676e00711131508l4cb1cafajd559ca804d61b3c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1194 bytes --]

Luca Tettamanti wrote:
> On Nov 13, 2007 11:42 PM, Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>   
>> Anthony Liguori wrote:
>>     
>>> 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.
>>>
>>>       
>> Maybe you set the mask too late? try setting it before creating the thread:
>>  sigfillset(&thread_sig_mask);
>>  sigdelset(&thread_sig_mask,SIGILL);
>>  sigdelset(&thread_sig_mask,SIGFPE);
>>  sigdelset(&thread_sig_mask,SIGSEGV);
>>     
>
> When using RTC or HPET for timing you also need to mask SIGIO; you may
> also need to change F_SETOWN (enable_sigio_timer) with the correct
> thread id, i.e.:
>
> fcntl(fd, F_SETOWN, gettid());
>
> Luca
>
>   
I do mask SIGIO - first the set is fiilled, then SGILL,SIGFPE,SIGSEGV 
are back enabled.
Regards, Dor

[-- Attachment #1.2: Type: text/html, Size: 1801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  parent reply	other threads:[~2007-11-14  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 20:15 Spawning threads in KVM/QEMU Anthony Liguori
     [not found] ` <473A05D6.2040003-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-11-13 22:42   ` 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 [this message]
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=473AC1F6.7030007@qumranet.com \
    --to=dor.laor-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kronos.it-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox