Re: [Xen-devel] Xen 4.2 Release Plan / TODO

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

On Tue, Mar 27, 2012 at 10:33 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Thu, 2012-03-22 at 10:38 +0000, Ian Campbell wrote:
>> On Thu, 2012-03-22 at 10:34 +0000, George Dunlap wrote:
>> > The devices in fact don't work quite right, AFAICT.  So I'm gathering
>> > that the "quirks" lists areas of PCI configuration space which it is
>> > safe for pciback to allow the guest to modify.  (I'm going to hack
>> > libxl to set "permissive" to test this theory.)
>>
>> I think that based on what Keir says we should just expose the
>> permissive setting in xl/libxl for the time being, that's a far simpler
>> patch. No need for the full power of per-register whitelisting
>
> Looks like this is just a case of writing the BDF of a device to a sysfs
> node or booting with xen-pciback.permissive=1 to turn it on globally.
> Possibly this could be "fixed" purely by documentation? I've added it to
> the TODO as a nice to have with George's name next to it, hope that's
> OK.

It seems like having xl/libxl capable of doing the sysfs writing is a
better thing, and shouldn't be too hard really.  I'll try to hack that
up this week.

Going forward, it would be nice if xl could do hot unplug and pciback
binding, so people wouldn't have to muck about with rmmod and manual
sysfs twiddling; but that will have to be a 4.3 thing I guess.

 -George

>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel