All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] Asynchronous reliable and configurable cache flush
Date: Thu, 3 Apr 2008 01:40:33 +0100	[thread overview]
Message-ID: <200804030140.33589.paul@codesourcery.com> (raw)
In-Reply-To: <18419.46090.542427.977863@mariner.uk.xensource.com>

> > > +    if (ret) {
> > > +        BADF("scsi-disc: IO error on flush: %s\n", strerror(-ret));
> >
> > This is wrong for two reasons: BADF already adds a suitable prefix,
> > and is for reporting qemu bugs (i.e. missing features or things that
> > should never happen). This is just a normal IO error, which we
> > correctly report to the guest.
>
> I don't think flush failures are a normal IO error.  They can only
> occur when the corresponding host block device is having serious
> trouble.  Normally (if it's actually a host disk) this is very bad.

In practice any IO error indicates that the target device is pretty screwed.
I don't see why flushes should be special. When caches are enabled I'd be 
fairly surprised if normal write operations ever returned an error.

Paul

  reply	other threads:[~2008-04-03  0:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 17:18 [Qemu-devel] [PATCH] Asynchronous reliable and configurable cache flush Ian Jackson
2008-04-01 17:46 ` Paul Brook
2008-04-01 18:45   ` Jamie Lokier
2008-04-02 12:26     ` Paul Brook
2008-04-02 15:23       ` Jamie Lokier
2008-04-02 16:20         ` Ian Jackson
2008-04-03 11:38           ` Jamie Lokier
2008-04-03 12:06             ` Ian Jackson
2008-04-02 16:27   ` Ian Jackson
2008-04-03  0:40     ` Paul Brook [this message]
2008-04-03 10:00       ` Ian Jackson
2008-04-01 18:07 ` Samuel Thibault
2008-04-02 14:21   ` Ian Jackson
2008-04-04 14:29     ` Samuel Thibault
2008-04-02 16:31 ` [Qemu-devel] " 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=200804030140.33589.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=Ian.Jackson@eu.citrix.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 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.