What's the state of dom0 S3? It doesn't work on latest xen

What's the state of dom0 S3? It doesn't work on latest xen

[Tom Rotenberg]

Hi,

I'm using a Lenovo T400, and it fails to go to S3, with the latest
xen-unstable (which uses the 2.6.30-pvops kernel).
Does anyone know how to make it work?

Tom

Re: What's the state of dom0 S3? It doesn't work on latest xen

[Pasi Kärkkäinen]

On Wed, Sep 16, 2009 at 07:01:05PM +0300, Tom Rotenberg wrote:
> Hi,
> 
> I'm using a Lenovo T400, and it fails to go to S3, with the latest
> xen-unstable (which uses the 2.6.30-pvops kernel).
> Does anyone know how to make it work?
> 

Hmm.. is xen-unstable checking out xen-tip/master instead of
rebase/master? 

rebase-master is at 2.6.31 atm..

-- Pasi

Re: What's the state of dom0 S3? It doesn't work on latest xen

[Tom Rotenberg]

well, i don't know...
2.6.31 should support S3?

On Wed, Sep 16, 2009 at 7:49 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Wed, Sep 16, 2009 at 07:01:05PM +0300, Tom Rotenberg wrote:
>> Hi,
>>
>> I'm using a Lenovo T400, and it fails to go to S3, with the latest
>> xen-unstable (which uses the 2.6.30-pvops kernel).
>> Does anyone know how to make it work?
>>
>
> Hmm.. is xen-unstable checking out xen-tip/master instead of
> rebase/master?
>
> rebase-master is at 2.6.31 atm..
>
> -- Pasi
>
>

Re: What's the state of dom0 S3? It doesn't work on latest xen

[Jeremy Fitzhardinge]

On 09/16/09 14:06, Tom Rotenberg wrote:
> well, i don't know...
> 2.6.31 should support S3?
>   

I believe so.

    J

RE: What's the state of dom0 S3? It doesn't work on latest xen

[Wei, Gang]

Jeremy Fitzhardinge wrote:
> On 09/16/09 14:06, Tom Rotenberg wrote:
>> well, i don't know...
>> 2.6.31 should support S3?
>> 
> 
> I believe so.

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.

Jimmy

Re: What's the state of dom0 S3? It doesn't work on latest xen

[Jeremy Fitzhardinge]

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

Re: What's the state of dom0 S3? It doesn't work on latest xen

[Tom Rotenberg]

So, if i clone the latest xen unstable, and build it, it should work?

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

On Thu, Sep 17, 2009 at 5:39 AM, Jeremy Fitzhardinge <jeremy@goop.org> 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
>

Re: What's the state of dom0 S3? It doesn't work on latest xen

[Qing He]

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@goop.org> 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
> >

Re: What's the state of dom0 S3? It doesn't work on latest xen

[Tom Rotenberg]

On which machine did u try it on?
what version of Xen & what version of the kernel were u using?

On Thu, Sep 17, 2009 at 6:53 PM, Qing He <qing.he@intel.com> wrote:
> 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@goop.org> 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
>> >
>