From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NKDkv-0008Hl-0T
	for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:26:41 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NKDkq-0008B2-6e
	for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:26:40 -0500
Received: from [199.232.76.173] (port=40039 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NKDkq-0008An-1f
	for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:26:36 -0500
Received: from mx1.redhat.com ([209.132.183.28]:17037)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mst@redhat.com>) id 1NKDkp-0002EN-FH
	for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:26:35 -0500
Received: from int-mx03.intmail.prod.int.phx2.redhat.com
	(int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id nBEGQY4u018272
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <qemu-devel@nongnu.org>; Mon, 14 Dec 2009 11:26:34 -0500
Date: Mon, 14 Dec 2009 18:23:42 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH RFC] virtio: add features qdev property
Message-ID: <20091214162342.GB5807@redhat.com>
References: <20091213204341.GA25823@redhat.com> <4B260846.9020503@redhat.com>
	<20091214094255.GA32140@redhat.com> <4B261269.7080801@redhat.com>
	<20091214111046.GB32355@redhat.com> <4B262379.1060009@redhat.com>
	<m3y6l51y50.fsf@crossbow.pond.sub.org>
	<20091214135915.GN973@redhat.com> <4B26534D.1060806@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B26534D.1060806@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org

On Mon, Dec 14, 2009 at 04:01:33PM +0100, Gerd Hoffmann wrote:
> On 12/14/09 14:59, Michael S. Tsirkin wrote:
>> It's not an easy quesiton.
>> If we do it as disable bits, then we get incompatible
>> machines when running on different hosts.
>
> In case that one host supports feature which the other doesn't and the  
> feature isn't masked out?  Well, management failure I'd say.  The whole  
> point of the compat machine types (and properties used there) is to make  
> sure the vm's are compatible even in case the hosts run different  
> software versions.
>
> cheers,
>   Gerd


So how do you do this?
Assume we have -disable_hw_csum.
We want new machine type to have it off, right?
But now you run qemu on host which does
not support hw_csum. With your suggestion
it will not enable hw csum?

-- 
MST