[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH][RFC] Support more Capability StructuresandDevice Specific

The PCI config space passthrough is actually crucial for Xen 3.3.

We have already found many device assignment issues caused by the lack of the 
passthrough (and I think more issues will be found).
For example, the assigned BroadCom NIC can't work because the driver needs to 
access the register BNX2_PCICFG_INT_ACK_CMD (at 0x84); another example: the USB 
assignment doesn't work -- one of the reasons is: UHCI-hc needs to access 
config space reigster USB_LEGKEY(at 0xC0-C1) to enable USB IRQ.

So it will be great to push the patch into xen-unstable tree.

-- Dexuan

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ian Jackson
Sent: 2008年7月1日 0:50
To: Yuji Shimada
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Dong, Eddie; Keir Fraser
Subject: Re: [Xen-devel] [PATCH][RFC] Support more Capability 
StructuresandDevice Specific

Yuji Shimada writes ("Re: [Xen-devel] [PATCH][RFC] Support more Capability 
Structures andDevice Specific"):
> I am going to release these following patches.
> Should I release patch against the upstream qemu merge prior to Xen
> Unstable ?

We're currently working to integrate the upstream qemu merge into
patchman.  I hope that we can be successful with this, so that we can
switch to this tree as the default in 3.3.

With that in mind:

Have you looked at the upstream merge at all yet ?  I haven't yet done
any PCI passthrough testing and I think it's very important that we do
some of that testing.  If you have any time available to do some
checking of the qemu upstream merge tree, even before we consider your
recent patches, that would be very helpful.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.