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

Re: [Xen-devel] [PATCH] hvmloader / qemu-xen: Getting rid of resource conflict for OpRegion.



On 20/12/2012 10:41, "Ian Campbell" <Ian.Campbell@xxxxxxxxxx> wrote:

> Adding our qemu maintainer.
> 
> On Thu, 2012-12-20 at 03:56 +0000, G.R. wrote:
>> Switch to a new address that can reach to Jean.
>> 
>> On Thu, Dec 20, 2012 at 11:52 AM, G.R. <firemeteor@xxxxxxxxxxxxxxxxxxxxx>
>> wrote:
>>> This is hvmloader part of the change that gets rid of the resource
>>> conflict warning in the guest kernel.
>>> The OpRegion may not always be page aligned.
> 
> Is it worth detecting this and allocating 2 or 3 pages as required?
> 
> The OpRegion is always 8096 bytes? (two pages, but not necessarily
> aligned)?
> 
> Do we need to worry about what is in the "slop" at either end of a 3
> page region containing this? If they are sensitive registers then we may
> have a problem.

In the hvmloader patch it is not worth it I think, one extra page of memory
hole is hardly a scarce resource.

I don't know whether the qemu side is accurate enough. If the region is 8096
bytes then it is not necessarily the case that an unaligned start address
means we need three pages mapped.

 -- Keir

> 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


 


Rackspace

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