qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Christoph Hellwig <hch@lst.de>,
	Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: [Qemu-devel] Re: Write cache enable from guest at runtime
Date: Mon, 14 Mar 2011 18:16:27 +0100	[thread overview]
Message-ID: <20110314171627.GB1062@lst.de> (raw)
In-Reply-To: <AANLkTin7QzqiP_VH=ARu2T8mEagJR7=k-S4pLbMQ1ObE@mail.gmail.com>

On Mon, Mar 14, 2011 at 05:07:57PM +0000, Stefan Hajnoczi wrote:
> Hi Christoph,
> I have written up thoughts on write cache enable, including a
> workaround to change O_SYNC on a file without kernel changes:
> 
> http://wiki.qemu.org/Features/WriteCacheEnable
> 
> Guest ability to control write cache enable is useful and I'd like to
> see it in QEMU soon.  Any thoughts about what I've posted?  Care to
> submit your patches?

I have patches using Prerna's close and reopen method almost ready for posting.
Still fighting a bit with the new virtio code to wire it up.

Unlike your variant I actually added a generic change config request type,
which allows to re-use it for other runtime controllable features later.

  reply	other threads:[~2011-03-14 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 17:07 [Qemu-devel] Write cache enable from guest at runtime Stefan Hajnoczi
2011-03-14 17:16 ` Christoph Hellwig [this message]
2011-03-14 19:15   ` [Qemu-devel] " Stefan Hajnoczi
2011-03-15 10:50     ` Christoph Hellwig
2011-03-15 11:21       ` Stefan Hajnoczi

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=20110314171627.GB1062@lst.de \
    --to=hch@lst.de \
    --cc=aliguori@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=prerna@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 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).