qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Christoph Hellwig <hch@lst.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Re: bs->enable_write_cache and the guest ABI
Date: Tue, 09 Mar 2010 11:56:03 +0200	[thread overview]
Message-ID: <4B961B33.1000909@redhat.com> (raw)
In-Reply-To: <20100308230022.GC16057@shareable.org>

On 03/09/2010 01:00 AM, Jamie Lokier wrote:
> Avi Kivity wrote:
>    
>> I think we have to go with a qdev property as Christoph suggests.  Then
>> it becomes the management's responsibility to set it right.
>>      
> How can the management be expected to know or follow dynamically
> changing guest state?  There guests which disable a drive's write
> cache in some application scripts, and others which enable it in boot
> scripts.  That's not something management should be knowing about.
>    

The flag indicates whether the drive has a write cache or not.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-03-09  9:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-07 14:42 [Qemu-devel] bs->enable_write_cache and the guest ABI Avi Kivity
2010-03-08  9:39 ` Christoph Hellwig
2010-03-08  9:45   ` Avi Kivity
2010-03-08  9:47   ` Jamie Lokier
2010-03-08 17:00     ` Christoph Hellwig
2010-03-08 22:55       ` Jamie Lokier
2010-03-08 10:29 ` [Qemu-devel] " Juan Quintela
2010-03-08 10:48   ` Avi Kivity
2010-03-08 12:46     ` Juan Quintela
2010-03-08 23:00     ` Jamie Lokier
2010-03-09  9:56       ` Avi Kivity [this message]
2010-03-09 19:26         ` Jamie Lokier

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=4B961B33.1000909@redhat.com \
    --to=avi@redhat.com \
    --cc=hch@lst.de \
    --cc=jamie@shareable.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).