From: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] ioemu : add flush in ide_unplug_harddisks()
Date: Tue, 24 Feb 2009 08:46:33 +0900 [thread overview]
Message-ID: <C1C99610F52C8At.horikoshi@jp.fujitsu.com> (raw)
In-Reply-To: <18850.53676.560908.266537@mariner.uk.xensource.com>
Hi.
Thank you for the comment.
I have understood that it is a best approach to use the IDE flush cache command.
I'm sorry I had overlooked the thread.
Best regards,
Tomonari Horikoshi
Ian Jackson san wrote:----------------------
Sent: Mon, 23 Feb 2009 16:41:16 +0000
Subject: Re: [Xen-devel] [PATCH] ioemu : add flush in ide_unplug_harddisks()
> Stefano Stabellini writes ("Re: [Xen-devel] [PATCH] ioemu : add flush in ide_unplug_harddisks()
> "):
> > Tomonari Horikoshi wrote:
> > > I think the "flush" is necessary.
> > > When "ioemu ide device" changes into "vbd" by "ide_unplug_harddisks()".
> >
> > I don't think that calling bdrv_aio_flush is a good idea since it is
> > asyncronous and right after the call we are going to close the device
> > without waiting for completion.
>
> Yes, bdrv_aio_flush is wrong I think.
>
> This seems related to the discussion we had in January. As I wrote
> in
> http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00165.html
> it seems to me that the guest should know about be able to flush
> for itself ? After all we implement the IDE flush cache command.
>
> Ian.
>
prev parent reply other threads:[~2009-02-23 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 3:29 [PATCH] ioemu : add flush in ide_unplug_harddisks() Tomonari Horikoshi
2009-02-20 11:40 ` Stefano Stabellini
2009-02-23 16:41 ` Ian Jackson
2009-02-23 23:46 ` Tomonari Horikoshi [this message]
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=C1C99610F52C8At.horikoshi@jp.fujitsu.com \
--to=t.horikoshi@jp.fujitsu.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=stefano.stabellini@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.