All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Davies <richard@arachsys.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Chris Webb <chris@arachsys.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, Zhi Yong Wu <zwu.kernel@gmail.com>,
	Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: add the support to drain throttled requests
Date: Fri, 23 Mar 2012 11:02:30 +0000	[thread overview]
Message-ID: <20120323110230.GK17656@alpha.arachsys.com> (raw)
In-Reply-To: <CAJSP0QW7FzX425ExBn7Ug4TCHXBfhsB-onqP3PDMz_JvtSsX0g@mail.gmail.com>

Stefan Hajnoczi wrote:
> > Hi. We were producing the IDE assert()s and deadlocks with linux kernels.
> > Although I believe the same symptoms exist on windows, I haven't actually
> > tested it myself. Typically they would show up in the 16-bit bootloader
> > code, even before the 32-bit OS has started.
>
> Okay, that makes sense.  Bootloaders and the BIOS may use the simplest
> driver interface - which may be PIO in the case.  I asked because the
> IDE DMA code path should work with I/O throttling and Windows is known
> for sometimes falling back to the PIO code path when some heuristics
> trigger.

Whilst the bootloader was the easiest place for us to replicate this
deadlock, we have also seen it with running Linux VMs.

Older Linux kernels (e.g. CentOS 5) will fall back to PIO mode on IDE
devices if they experience storage timeouts (e.g. due to heavy contention of
underlying storage from other VMs).

Hence, the IO limits deadlock can lead to running Linux VMs locking up as
well as just Windows and Linux bootloaders.

Cheers,

Richard.

  reply	other threads:[~2012-03-23 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13  1:53 [Qemu-devel] [PATCH] block: add the support to drain throttled requests zwu.kernel
2012-03-20  9:40 ` Zhi Yong Wu
2012-03-20  9:47   ` Paolo Bonzini
2012-03-20  9:58     ` Kevin Wolf
2012-03-20 11:44       ` Stefan Hajnoczi
2012-03-22 19:07         ` Chris Webb
2012-03-23 10:38           ` Stefan Hajnoczi
2012-03-23 10:43             ` Chris Webb
2012-03-23 10:50               ` Stefan Hajnoczi
2012-03-23 11:02                 ` Richard Davies [this message]
2012-03-23 11:32                   ` Stefan Hajnoczi
2012-03-23 16:56                     ` Stefan Hajnoczi
2012-03-26 14:21         ` Stefan Hajnoczi
2012-03-26 14:31           ` Kevin Wolf
2012-03-27  4:29           ` Zhi Yong Wu
2012-03-27  6:52             ` Stefan Hajnoczi
2012-03-20  9:56   ` Kevin Wolf

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=20120323110230.GK17656@alpha.arachsys.com \
    --to=richard@arachsys.com \
    --cc=chris@arachsys.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=wuzhy@linux.vnet.ibm.com \
    --cc=zwu.kernel@gmail.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 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.