All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [patch 1/3] QEMU/KVM: separate thread for IO handling
Date: Thu, 27 Mar 2008 17:49:47 +0200	[thread overview]
Message-ID: <47EBC21B.9030907@qumranet.com> (raw)
In-Reply-To: <20080327154859.GA8184@dmt>

Marcelo Tosatti wrote:
>>>  
>>>       
>> I still don't understand this.  Timer expiration ought to be processed 
>> in the iothread, when SIGALRM is dequeued, and be completely unrelated 
>> to whatever vcpu 0 is doing.
>>     
>
> Yes, now it is unrelated. But before the patch it wasnt. So "currently
> the SIGALRM handler..." means the current code in kvm-userspace.git.
>
>   

I see now.  Okay, will merge.

>>> - Processing of IO events will not be unnecessarily interrupted.
>>>  
>>>       
>> What do you mean by this?
>>     
>
> That SIGIO, SIGALRM and SIGUSR2 signals will not interrupt
> main_loop_wait(), since they are now blocked. Better latency, less time
> holding the mutex lock

Signals are blocked in current git, they can only interrupt the guest, 
not the host.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

  reply	other threads:[~2008-03-27 15:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 15:09 [patch 0/3] QEMU dedicated IO thread Marcelo Tosatti
2008-03-27 15:09 ` [patch 1/3] QEMU/KVM: separate thread for IO handling Marcelo Tosatti
2008-03-27 15:23   ` Avi Kivity
2008-03-27 15:48     ` Marcelo Tosatti
2008-03-27 15:49       ` Avi Kivity [this message]
2008-03-27 15:09 ` [patch 2/3] QEMU/KVM: add function to handle signals Marcelo Tosatti
2008-03-27 15:25   ` Avi Kivity
2008-03-27 15:57     ` Marcelo Tosatti
2008-03-27 15:57       ` Avi Kivity
2008-03-27 16:55   ` Avi Kivity
2008-03-27 15:09 ` [patch 3/3] QEMU/libkvm: dont create vcpu0 thread Marcelo Tosatti
2008-03-27 15:55   ` Avi Kivity
2008-03-27 15:54 ` [patch 0/3] QEMU dedicated IO thread Avi Kivity
2008-03-27 19:06   ` Avi Kivity
2008-03-27 20:21     ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2008-04-02 23:20 [patch 0/3] separate thread for IO handling V3 Marcelo Tosatti
2008-04-02 23:20 ` [patch 1/3] QEMU/KVM: separate thread for IO handling Marcelo Tosatti

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=47EBC21B.9030907@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=marcelo@kvack.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.