qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM brokenness due to IO thread changes
Date: Tue, 28 Apr 2009 15:09:57 -0500	[thread overview]
Message-ID: <49F76295.2010403@codemonkey.ws> (raw)
In-Reply-To: <49F75F67.9040402@web.de>

Jan Kiszka wrote:
> Marcelo Tosatti wrote:
>   
>> Jan,
>>
>> On Tue, Apr 28, 2009 at 09:40:01AM +0200, Jan Kiszka wrote:
>>     
>>> Hi,
>>>
>>> this is a heads-up, maybe someone has some time to look into this over
>>> the day: I seems like the IO thread changes caused a few regressions to
>>> the KVM mode.
>>>
>>> When I keep this feature disabled, I see strange hick-ups of the event
>>> delivery mechanism, and the guest stops once in a while for a second or
>>> so. Attaching strace makes the whole process terminate early (looks like
>>> it triggers a race in the signal handling). And when I enable the IO
>>> thread, I immediately get a deadlock on qemu_global_mutex.
>>>       
>> Yes its borked. The iothread should signal the vcpu thread whenever it
>> wants to grab the mutex lock, because unlike kvm-userspace it does not
>> drop the global mutex when entering guest mode (VCPU_RUN ioctl).
>>
>> Anthony will commit patches to fix that soon.
>>     
>
> Looking forward. It's far more efficient to test my infrastructure
> changes against the KVM mode.
>   

N.B. he's seeing issues with the IO thread disabled.

I've not seen this myself and my patch doesn't fix that problem.

Regards,

Anthony Liguori

  reply	other threads:[~2009-04-28 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  7:40 [Qemu-devel] KVM brokenness due to IO thread changes Jan Kiszka
2009-04-28 12:51 ` Marcelo Tosatti
2009-04-28 19:56   ` Jan Kiszka
2009-04-28 20:09     ` Anthony Liguori [this message]
2009-04-28 22:21       ` 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=49F76295.2010403@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jan.kiszka@web.de \
    --cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).