From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 0/2] PV drivers product number registration Date: Wed, 26 Sep 2012 08:51:48 -0400 Message-ID: <20120926125148.GI7356@phenom.dumpdata.com> References: <1348662212-3559-1-git-send-email-paul.durrant@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1348662212-3559-1-git-send-email-paul.durrant@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Paul Durrant Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Wed, Sep 26, 2012 at 01:23:30PM +0100, Paul Durrant wrote: > PV drivers in HVM guests typically make use off an 'unplug' protocol in QEMU > to prevent co-existence of emulated devices. > See docs/misc/hvm-emulated-unplug.markdown for details. > > The register of product numbers used by the blacklisting feature of this > protocol is currently directly in the xenstore.c source module of > traditional QEMU. It should really be in a Xen header file to prevent Why do we want to blacklist them? Isn't it a whitelist (as in it is the right values?) > duplication/conflict between QEMU versions. > > Moreover the linux PV-on-HVM drivers make use of product number 3 seemingly > without ever registering that number. > > This patch series introduces a new header and registers product number 3 > for Linux's use. A subsequent patch to qemu-xen-unstable wll be created to > make use of the new header. > > Signed-off-by: Paul Durrant > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >