[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [v5][PATCH 0/5] xen: add Intel IGD passthrough support
- To: Paolo Bonzini <pbonzini@xxxxxxxxxx>, "Michael S. Tsirkin" <mst@xxxxxxxxxx>
- From: "Chen, Tiejun" <tiejun.chen@xxxxxxxxx>
- Date: Wed, 25 Jun 2014 17:50:16 +0800
- Cc: peter.maydell@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, stefano.stabellini@xxxxxxxxxxxxx, allen.m.kay@xxxxxxxxx, qemu-devel@xxxxxxxxxx, Kelly.Zytaruk@xxxxxxx, anthony.perard@xxxxxxxxxx, anthony@xxxxxxxxxxxxx, yang.z.zhang@xxxxxxxxx
- Delivery-date: Wed, 25 Jun 2014 09:50:37 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 2014/6/25 17:31, Paolo Bonzini wrote:
Il 25/06/2014 11:21, Chen, Tiejun ha scritto:
Adding a vendor-specific capability or BAR
in an existing device is painful - hard to find
free space for it.
Yes, this is a potential risk as well since we can't guarantee current
free space is always valid for ever.
For past devices, we know which BARs they use. For future devices, it
would be nice if the PCH/MCH backdoor was specified so that we know they
will leave a free BAR for virtualization.
Now I'm a bit confused about BAR here.
You're saying we will reserve a free BAR to address those information to
expose to guest, but which device does this free BAR belong to? The
video device? Or PCH/MCH?
Thanks
Tiejun
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
