From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: KVM call agenda for Sept 21 Date: Mon, 20 Sep 2010 14:30:15 -0500 Message-ID: <4C97B647.4070005@codemonkey.ws> References: <20100920164445.GN19949@x200.localdomain> <4C9790EF.9030505@redhat.com> <20100920191537.GH30611@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org, Nadav Har'El , "Dong, Eddie" , Sheng Yang To: "Michael S. Tsirkin" Return-path: Received: from mail-vw0-f66.google.com ([209.85.212.66]:62872 "EHLO mail-vw0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757299Ab0ITTad (ORCPT ); Mon, 20 Sep 2010 15:30:33 -0400 Received: by vws18 with SMTP id 18so1282890vws.1 for ; Mon, 20 Sep 2010 12:30:33 -0700 (PDT) In-Reply-To: <20100920191537.GH30611@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56388 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oxm4U-0002Rv-3U for qemu-devel@nongnu.org; Mon, 20 Sep 2010 15:30:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oxm4R-00086c-D8 for qemu-devel@nongnu.org; Mon, 20 Sep 2010 15:30:36 -0400 Received: from mail-vw0-f67.google.com ([209.85.212.67]:41341) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oxm4R-00086X-B4 for qemu-devel@nongnu.org; Mon, 20 Sep 2010 15:30:35 -0400 Received: by vws9 with SMTP id 9so738404vws.10 for ; Mon, 20 Sep 2010 12:30:34 -0700 (PDT) Message-ID: <4C97B647.4070005@codemonkey.ws> Date: Mon, 20 Sep 2010 14:30:15 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <20100920164445.GN19949@x200.localdomain> <4C9790EF.9030505@redhat.com> <20100920191537.GH30611@redhat.com> In-Reply-To: <20100920191537.GH30611@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: KVM call agenda for Sept 21 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Chris Wright , Nadav Har'El , kvm@vger.kernel.org, "Dong, Eddie" , qemu-devel@nongnu.org, Avi Kivity , Sheng Yang 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 >