qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	ronnie sahlberg <ronniesahlberg@gmail.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Weird iscsi/fd-event issue since recent merge of event system changes
Date: Mon, 21 May 2012 12:59:38 +0200	[thread overview]
Message-ID: <4FBA201A.5040505@redhat.com> (raw)
In-Reply-To: <4FBA1CC4.7020009@redhat.com>

Il 21/05/2012 12:45, Kevin Wolf ha scritto:
>> I have not yet found the exact part of this big patch that cause this
>> slowdown, but will continue investigating.
>>
>> I am posting this here in case someone has any idea  or if 55ms rings any bells.

55ms is the frequency of the PIT while the BIOS is running.  I'd guess
something is not waking up the iothread properly.

> The only thing in this merge that looks as if it could be related is
> Paolo's AIO changes between commit adfe92f6 and 9eb0bfca.
> 
> Or if you use IDE, Stefan's patches to make PIO operations asynchronous
> could be related.

Yeah, both seem just as likely to be the culprit.  Please bisect.

Paolo

  reply	other threads:[~2012-05-21 10:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  6:07 [Qemu-devel] Weird iscsi/fd-event issue since recent merge of event system changes ronnie sahlberg
2012-05-21 10:45 ` Kevin Wolf
2012-05-21 10:59   ` Paolo Bonzini [this message]
2012-05-21 11:00   ` ronnie sahlberg
2012-05-21 13:20     ` Stefan Hajnoczi
2012-05-22  9:07       ` ronnie sahlberg
2012-05-22  9:15         ` Paolo Bonzini
2012-05-22  9:15         ` ronnie sahlberg
2012-05-22  9:29           ` Paolo Bonzini
2012-05-22  9:48             ` ronnie sahlberg
2012-05-22 10:03               ` ronnie sahlberg
2012-05-22 16:31                 ` Michael Tokarev
2012-05-25  6:53                   ` ronnie sahlberg

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=4FBA201A.5040505@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=stefanha@linux.vnet.ibm.com \
    /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).