From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Nadav Har'El <nyh@math.technion.ac.il>,
"Dong, Eddie" <eddie.dong@intel.com>,
Sheng Yang <sheng@linux.intel.com>
Subject: Re: KVM call agenda for Sept 21
Date: Mon, 20 Sep 2010 14:30:15 -0500 [thread overview]
Message-ID: <4C97B647.4070005@codemonkey.ws> (raw)
In-Reply-To: <20100920191537.GH30611@redhat.com>
On 09/20/2010 02:15 PM, Michael S. Tsirkin wrote:
> On Mon, Sep 20, 2010 at 06:50:55PM +0200, Avi Kivity wrote:
>
>> On 09/20/2010 06:44 PM, Chris Wright wrote:
>>
>>> Please send in any agenda items you are interested in covering.
>>>
>>>
>> nested vmx: the resurrection. Nice to see it progressing again, but
>> there's still a lot of ground to cover. Perhaps we can involve
>> Intel to speed things up?
>>
> Hotplug
>
Drive caching. Discussion on the mailing list but regardless of my own
opinions of what it should be, we really need to have a clearly defined
set of guarantees for all of the caching modes. This is something I get
asked very frequently about from end users because there's lack of
clarity about what each of the caching options do with respect to data
integrity.
Regards,
Anthony Liguori
>
>> --
>> error compiling committee.c: too many arguments to function
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-09-20 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 16:44 KVM call agenda for Sept 21 Chris Wright
2010-09-20 16:50 ` Avi Kivity
2010-09-20 19:15 ` Michael S. Tsirkin
2010-09-20 19:30 ` Anthony Liguori [this message]
2010-09-21 3:37 ` Nakajima, Jun
2010-09-21 11:48 ` Avi Kivity
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=4C97B647.4070005@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=eddie.dong@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nyh@math.technion.ac.il \
--cc=qemu-devel@nongnu.org \
--cc=sheng@linux.intel.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