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

RE: [Xen-devel] disable qemu PCI devices in HVM domains



> 
> Steven Smith writes ("Re: [Xen-devel] disable qemu PCI devices in HVM
> domains"):
> > [stuff]
> 
> Thanks for that.  I have applied your patches to the code, and checked
> in your commentary as a new document file after some editing.
> 
> I've also:
> 
> * Documented this assurance you game James:
> 
>  > > 5) The drivers check the magic number by reading two bytes from
0x10
>  > > >    again.  If it's changed from 0x49d2, the drivers are
blacklisted
>  > > >    and should not load.
>  > > It appears that you set it to '0xd249' when the driver is
> blacklisted.
>  > > Can I rely on that?
>  > I can't see any reason for us to ever change it, so if it makes
things
>  > easier for you then go ahead.
> 
> * Documented the registry location and allocation protocol
>   (qemu-xen-unstable's xenstore.c, and ask on xen-devel, respectively)
> 
> * Assigned 0xffff for `experimental' drivers in the hope that people
>   won't steal one of the existing assignments.
> 
> * Assigned 2 ("gplpv-windows") for James's drivers.  James, you are
>   in the best position to decide what the `build id' should look like
>   and there is no need to document it other than in your release
>   notes, so I'll leave that to you.
> 

Thanks Ian. I assume that that patch is in qemu-xen-unstable as opposed
to qemu-xen-3.3-testing... is there an easy way I can pull that patch
into my copy of 3.3-testing?

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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