From: Gleb Natapov <gleb@qumranet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Flush pending AIO on reboot and shutdown.
Date: Wed, 13 Aug 2008 17:41:48 +0300 [thread overview]
Message-ID: <20080813144148.GE17567@minantech.com> (raw)
In-Reply-To: <20080813142904.GR6165@implementation.uk.xensource.com>
On Wed, Aug 13, 2008 at 03:29:04PM +0100, Samuel Thibault wrote:
> Gleb Natapov, le Wed 13 Aug 2008 17:25:58 +0300, a écrit :
> > On Wed, Aug 13, 2008 at 03:06:41PM +0100, Samuel Thibault wrote:
> > > Gleb Natapov, le Wed 13 Aug 2008 16:59:41 +0300, a écrit :
> > > > On Wed, Aug 13, 2008 at 02:46:08PM +0100, Samuel Thibault wrote:
> > > > > Gleb Natapov, le Wed 13 Aug 2008 16:23:58 +0300, a écrit :
> > > > > > If there is outstanding IDE IO when BIOS starts execution then IDE
> > > > > > commands sent by BIOS will interfere with it and will leave IDE
> > > > > > subsystem in unpredictable state. This can happen when system reboots
> > > > > > unexpectedly without waiting for IO completion. Flushing IO before exit
> > > > > > prevents data lose.
> > > > >
> > > > > I'm wondering: isn't that what happens with real machines?
> > > > >
> > > > With shutdown yes, but why not try harder. With reboot I don't think
> > > > that in real HW you can hang IDE interface after reboot ;)
> > >
> > > Mmm, I couldn't understand.
> > >
> > > With real hardware, if you reboot into the bios the board is not
> > > resetted either, and thus the interference is the same.
> > >
> > On real hardware if you press reset button
>
> That's when you press the reset button. When you have a triple fault
> the IDE board won't be resetted.
>
As far as I see qemu doesn't handle triple faults yet and when it will
handle it we will flush aio there too.
> > Currently BOCHS BIOS doesn't check that IDE is busy (it doesn't even
> > know that HW is present) and sends overlapping command.
>
> Then fix it.
>
Wow you found one more reason to do nothing in qemu. Congratulations.
The real HW are much more complex then what qemu is implementing. The
real HW can even save you buffers after you unplugged your computer. And
for real HW it takes much less time to do it too.
--
Gleb.
next prev parent reply other threads:[~2008-08-13 14:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 13:23 [Qemu-devel] [PATCH] Flush pending AIO on reboot and shutdown Gleb Natapov
2008-08-13 13:46 ` Samuel Thibault
2008-08-13 13:59 ` Gleb Natapov
2008-08-13 14:06 ` Samuel Thibault
2008-08-13 14:25 ` Gleb Natapov
2008-08-13 14:29 ` Samuel Thibault
2008-08-13 14:40 ` Avi Kivity
2008-08-13 14:41 ` Gleb Natapov [this message]
2008-08-13 16:14 ` Samuel Thibault
2008-08-13 13:52 ` Anthony Liguori
2008-08-13 14:13 ` Gleb Natapov
2008-08-13 15:07 ` Anthony Liguori
2008-08-13 15:18 ` Avi Kivity
2008-08-13 15:47 ` Anthony Liguori
2008-08-13 16:36 ` Avi Kivity
2008-08-13 15:23 ` Gleb Natapov
2008-08-13 15:53 ` Anthony Liguori
2008-08-13 18:35 ` Gleb Natapov
2008-08-13 18:40 ` Avi Kivity
2008-08-13 18:53 ` Gleb Natapov
2008-08-13 19:04 ` Anthony Liguori
2008-08-14 10:26 ` Jamie Lokier
2008-08-13 19:03 ` Anthony Liguori
2008-08-13 22:32 ` Samuel Thibault
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=20080813144148.GE17567@minantech.com \
--to=gleb@qumranet.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).