Re: Re: [PATCH] ioemu-remote: ACPI S3 state wake up

[Jean Guyader <jean.guyader@eu.citrix.com>]

I already tried to reduce the rw area, and just keep 0xe0 -> 0xef. But 
obviously it doesn't work the device model needs to write on this frame 
0xf1. I still don't figure out why.


Trolle Selander wrote:
> Don't leave the main rombios unprotected. I also added a comment to 
> explain the "magic numbers", since their meaning is perhaps not as 
> obvious as I thought, in particular now that we're no longer 
> blanket-protecting the entire firmware area anymore.
> 
> / Trolle
> 
> Signed-off-by: Trolle Selander <trolle.selander@eu.citrix.com 
> <mailto:trolle.selander@eu.citrix.com> 
> <mailto:trolle.selander@eu.citrix.com>
> 
> On Wed, Jul 23, 2008 at 7:02 PM, Ian Jackson <Ian.Jackson@eu.citrix.com 
> <mailto:Ian.Jackson@eu.citrix.com>> wrote:
> 
>     Jean Guyader writes ("[PATCH] ioemu-remote: ACPI S3 state wake up"):
>      > ioemu-remote: The device model needs to write in the ACPI tables
>     when it
>      > wakes up from S3 state.
> 
>     I've applied this but I have to say these magic numbers
>      > -        if (xc_hvm_set_mem_type(xc_handle, domid, mem_type,
>     0xc0, 0x40))
>      > +        if (xc_hvm_set_mem_type(xc_handle, domid, mem_type,
>     0xc0, 0x20))
>     are pretty unpleasant!  Are they directly derived from addresses
>     specified in ACPI ?  I haven't looked ...
> 
>     Ian.
> 
>     _______________________________________________
>     Xen-devel mailing list
>     Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
>     http://lists.xensource.com/xen-devel
> 
> 


-- 
Jean Guyader