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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] PCI subsystem ids

To: Frank van der Linden <Frank.Vanderlinden@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] PCI subsystem ids
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 20 Aug 2008 18:03:14 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 20 Aug 2008 10:20:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48AC4E82.2020404@xxxxxxx>
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>
Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903
References: <48AC4E82.2020404@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> same driver, of course, and live happily ever after. Also, we considered 
> using Sun PCI subsystem IDs (as we do on our actual hardware), but 
> figured that it would be better to use the XenSource ids, so that all 
> Xen-based products out there can use eachothers virtual machines with 
> minimal hassle.

On the Linux side I'd also prefer the Xen identifiers as it means we can
reliably identify emulated hardware which can now and then be useful
when debugging reports or if the emulation is quirky.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>