From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKIHw-0002Dg-Kd for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:17:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKIHs-0002BY-TS for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:17:04 -0500 Received: from [199.232.76.173] (port=60352 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKIHs-0002BQ-Q2 for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:17:00 -0500 Received: from mx1.redhat.com ([209.132.183.28]:27254) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKIHs-0004MV-Ho for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:17:00 -0500 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id nBELGx1m026847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 14 Dec 2009 16:16:59 -0500 Date: Mon, 14 Dec 2009 23:14:16 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCH RFC] virtio: add features qdev property Message-ID: <20091214211416.GE6100@redhat.com> References: <4B262379.1060009@redhat.com> <20091214135915.GN973@redhat.com> <4B26534D.1060806@redhat.com> <20091214162342.GB5807@redhat.com> <4B267365.5090608@redhat.com> <20091214191742.GA6100@redhat.com> <4B26A2BC.6010501@redhat.com> <20091214204319.GA6398@redhat.com> <4B26AA2E.8000608@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B26AA2E.8000608@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Markus Armbruster , qemu-devel@nongnu.org On Mon, Dec 14, 2009 at 10:12:14PM +0100, Gerd Hoffmann wrote: > On 12/14/09 21:43, Michael S. Tsirkin wrote: >> What do we put in e.g. 0.11 compat? Any features we enable >> there might not be supported by host. > > compat properties as usual? > > Sorry, I still fail to see your problem. > > You'll have a 'disable' bitmap. Fill it via 'features='. > Or using separate properties for each feature. > qemu goes figure host_features. When done it masks out the features > disabled via properties. The result is used as final feature bitmap. > > -M pc-0.11 will disable hw_checksum > management software can do it too via -device virtio-net-pci,... if some > machines in the pool don't support it. And of course qemu will disable > it on its own in case the host kernel doesn't support it. > > cheers, > Gerd management is always behind :). Imagine a new and improved qemu. I run old management. I expect to see old properties, but old management can not disable new ones :) -- MST