WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] What's the state of dom0 S3? It doesn't work on latest x

On Thu, 2009-09-17 at 16:00 +0800, Tom Rotenberg wrote:
> So, if i clone the latest xen unstable, and build it, it should work?
> 

Well, although I got MSI device working after a S3 resume on my box,
I just found it still lacking something. The hypervisor doesn't
automatically restore the vectors to the physical devices, but only
does that on a hypercall: physdev_restore_msi.

I guess that it works because the S3 during is short and the addr/data
are still in the device?

> How should i send the machine to sleep? running 's2ram' causes a
> segmentation fault...

I uses the following:
        echo 0 > /sys/class/rtc/rtc0/wakealarm
        echo +20 > /sys/class/rtc/rtc0/wakealarm
        echo mem > /sys/power/state

Thanks,
Qing

> 
> On Thu, Sep 17, 2009 at 5:39 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> > On 09/16/09 18:14, Wei, Gang wrote:
> >> Current dom0 S3 should work with pci=nomsi. For msi case, we already have 
> >> workaround which may be sent out soon. The formal solution for msi case 
> >> which may require config space emulation need more consideration & 
> >> discussion.
> >>
> >
> > Actually I applied the MSI workaround today.
> >
> > ? ?J
> >

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