WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

Re: [Xen-devel] disable qemu PCI devices in HVM domains

To: Steven Smith <steven.smith@xxxxxxxxxxxxx>, James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] disable qemu PCI devices in HVM domains
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: 2008年12月31日 16:22:27 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: 2008年12月31日 08:22:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20081221195630.GA29139@xxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D0154FF9F@trantor > <C569370F.20329%keir.fraser@xxxxxxxxxxxxx> <20081215171059.GA2574@xxxxxxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0155005B@trantor > <20081221195630.GA29139@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Steven Smith writes ("Re: [Xen-devel] disable qemu PCI devices in HVM domains"):
> [stuff]
Thanks for that. I have applied your patches to the code, and checked
in your commentary as a new document file after some editing.
I've also:
* Documented this assurance you game James:
 > > 5) The drivers check the magic number by reading two bytes from 0x10
 > > > again. If it's changed from 0x49d2, the drivers are blacklisted
 > > > and should not load.
 > > It appears that you set it to '0xd249' when the driver is blacklisted.
 > > Can I rely on that?
 > I can't see any reason for us to ever change it, so if it makes things
 > easier for you then go ahead.
* Documented the registry location and allocation protocol
 (qemu-xen-unstable's xenstore.c, and ask on xen-devel, respectively)
* Assigned 0xffff for `experimental' drivers in the hope that people
 won't steal one of the existing assignments.
* Assigned 2 ("gplpv-windows") for James's drivers. James, you are
 in the best position to decide what the `build id' should look like
 and there is no need to document it other than in your release
 notes, so I'll leave that to you.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: RE: [Xen-devel] Multiple IRQ's in HVM for Windows , Ross Philipson
Next by Date: Re: [Xen-devel] pv_ops dom0 kernel failure with ata_piix , Jeremy Fitzhardinge
Previous by Thread: Re: [Xen-devel] disable qemu PCI devices in HVM domains , Steven Smith
Next by Thread: Re: [Xen-devel] disable qemu PCI devices in HVM domains , Ian Jackson
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /