From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pawel Moll Subject: Re: [RFC] kvm tools: Add support for virtio-mmio Date: Wed, 16 Nov 2011 13:21:58 +0000 Message-ID: <1321449718.3137.258.camel@hornet.cambridge.arm.com> References: <1321375667-17284-1-git-send-email-levinsasha928@gmail.com> <1321379773.3200.9.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Peter Maydell , "penberg@kernel.org" , "kvm@vger.kernel.org" , "mingo@elte.hu" , "asias.hejun@gmail.com" , "gorcunov@gmail.com" , Rusty Russell , "virtualization@lists.linux-foundation.org" To: Sasha Levin Return-path: Received: from service87.mimecast.com ([91.220.42.44]:57447 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755622Ab1KPNWG convert rfc822-to-8bit (ORCPT ); Wed, 16 Nov 2011 08:22:06 -0500 In-Reply-To: <1321379773.3200.9.camel@lappy> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, 2011-11-15 at 17:56 +0000, Sasha Levin wrote: > Hmm... If thats the plan, it should probably be a virtio thing (not > virtio-mmio specific). >=20 > Either way, it could also use some clarification in the spec. Well, the spec (p. 2.1) says: "The Subsystem Vendor ID should reflect the PCI Vendor ID of the environment (it's currently only used for informational purposes by the guest).". The fact is that all the curren= t virtio drivers simply ignore this field. So unless this changes I simpl= y have no idea how to describe that register. "Put anything there, no one cares"? "Write zero now, may change in future"? Any ideas welcomed. Cheers! Pawe=C5=82 PS. Thanks for defending my honour in the delayed-explosive-device thread ;-)