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

["G.R." <firemeteor@xxxxxxxxxxxxxxxxxxxxx>]

On Fri, Dec 21, 2012 at 2:27 AM, Ross Philipson
<Ross.Philipson@xxxxxxxxxx> wrote:


>> > Possibly with suitable macros used instead of magic numbers (e.g.,
>> > XC_PAGE_* and a macro for the opregion size).
>>
>> I guess there is no predefined macro for OpRegion size. And I guess I
>> need to define it twice for both code?
>
> In addition we should think about defining the IGD OpRegion in ACPI per the 
> spec (cited earlier). Guest drivers seem to find the region just by reading 
> the ASLS register in the gfx device's config space but it would be more 
> correct to define it in ACPI too. Just a thought.

Is it a requirement for the patch to be accepted? Or, are you saying
that this should not be IGD passthrough specific?
I'm not sure what you refer to by 'ACPI' here. Is it the spec itself
or header in your source code?
I'm sorry to ask but I'm just a unlucky user trying to fix my box.

The ASLS register is just the documented way to communicate the
OpRegion you can find in the spec.
There are a lot of details in the spec. But as long as we are not
going to emulate it, only the size is relevant here, I believe.

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