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>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] PCI subsystem ids
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 20 Aug 2008 18:15:26 +0100
Delivery-date: Wed, 20 Aug 2008 10:15:49 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckC6FZIlRrU9G7bEd24zAAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] PCI subsystem ids
User-agent: Microsoft-Entourage/
On 20/8/08 18:04, "Frank van der Linden" <Frank.Vanderlinden@xxxxxxx> wrote:

> But, this isn't done across the board (e.g. the PIIX bridge devices
> don't have these IDs). This makes the Microsoft HCT fail.
> Attached is a patch that makes pci_register_device initialize these
> values with the 0x5853/0x0001 defaults, and removes the explicit inits
> of these values in the various devices.
> A few issues that are worthy of discussion: since Windows use the
> subsystem IDs in its device tree, Windows systems will come up with
> 'found new hardware' after this patch. But, they will just reload the
> 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.

This should be a patch against the qemu-xen-unstable.git repository. This
would only possibly get applied on the 3.4 branch and we will be deleting
the old qemu tree from the Xen repository very soon when that branch opens.

 -- Keir

Xen-devel mailing list

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