From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
Keir Fraser <keir.fraser@eu.citrix.com>,
Kouya Shimura <kouya@jp.fujitsu.com>,
Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: Windows Bug Check 0x101 issue
Date: Wed, 26 Mar 2008 10:27:44 +0000 [thread overview]
Message-ID: <20080326102744.3124cbb4@core> (raw)
In-Reply-To: <18410.9596.488204.878357@mariner.uk.xensource.com>
> > +static void ide_flush_cb(void *opaque, int ret)
> > +{
> > + IDEState *s = opaque;
> > +
> > + s->status = READY_STAT;
> > + ide_set_irq(s);
>
> You need to check the return value (ret) and set an appropriate IDE
> error status if the operation failed. ide_abort_command may be of
> some use.
Flush errors are a bit hard to emulate. On a flush failing you have to
provide back an error state indicating the LBA block number (LBA28 or
LBA48 according to which flush command) of the specific failing block.
Calling the cache flush again restarts the flushing process having
dropped that block.
Alan
next prev parent reply other threads:[~2008-03-26 10:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 9:53 Windows Bug Check 0x101 issue Kouya Shimura
2008-03-24 11:01 ` Samuel Thibault
2008-03-24 11:05 ` Keir Fraser
2008-03-25 10:54 ` Kouya Shimura
2008-03-25 10:59 ` Keir Fraser
2008-03-25 11:28 ` Ian Jackson
2008-03-25 17:57 ` Samuel Thibault
2008-03-26 7:07 ` Kouya Shimura
2008-03-26 10:13 ` Samuel Thibault
2008-03-26 10:29 ` Ian Jackson
2008-03-26 10:27 ` Alan Cox [this message]
2008-03-26 10:51 ` Ian Jackson
2008-03-26 12:34 ` Alan Cox
2008-03-26 14:18 ` Ian Jackson
2008-03-26 10:39 ` Ian Jackson
2008-03-27 5:20 ` Kouya Shimura
2008-03-27 9:08 ` Alan Cox
2008-03-27 16:34 ` Ian Jackson
2008-03-27 16:30 ` Alan Cox
2008-03-27 17:39 ` Ian Jackson
2008-03-28 3:09 ` Kouya Shimura
[not found] ` <87k5jnl7qt.fsf@basil.nowhere.org>
2008-03-28 9:32 ` Ian Jackson
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=20080326102744.3124cbb4@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kouya@jp.fujitsu.com \
--cc=samuel.thibault@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.