From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKIDW-0000Iv-AT for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:12:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKIDR-0000GA-JT for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:12:29 -0500 Received: from [199.232.76.173] (port=54463 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKIDR-0000G5-Cj for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:12:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:25352) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKIDR-0003xe-3Z for qemu-devel@nongnu.org; Mon, 14 Dec 2009 16:12:25 -0500 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id nBELCNVH028261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 14 Dec 2009 16:12:23 -0500 Message-ID: <4B26AA2E.8000608@redhat.com> Date: Mon, 14 Dec 2009 22:12:14 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH RFC] virtio: add features qdev property References: <4B261269.7080801@redhat.com> <20091214111046.GB32355@redhat.com> <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> In-Reply-To: <20091214204319.GA6398@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Markus Armbruster , qemu-devel@nongnu.org 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