All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: kevin.tian@intel.com, ke.yu@intel.com, xen-devel@lists.xensource.com
Subject: Question about Xen S3 and resume code - Linux dom0 never exits the xen_safe_halt hypercall after resume
Date: Thu, 16 Jun 2011 18:57:39 -0400	[thread overview]
Message-ID: <20110616225739.GA8714@dumpdata.com> (raw)

I've been eyeing the ACPI S3/S5 code to see what would be necessary to
retool, and while testing I found something strange..

I've stuck the code on

 git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/acpi-s3.v1

I found out that if I don't have this patch:

commit 9f301b0a0081676dfc71b7f0898295e6bcba391a
Author: Yu Ke <ke.yu@intel.com>
Date:   Thu Jun 16 17:15:26 2011 -0400

    xen/acpi: add xen acpi processor driver

(which is in the devel/acpi-s3.v0 branch).

the hypervisor, after an S3 resume sits forever in the default_idle. The
Linux dom0 is stuck looping (I think) around SCHEDOP_block hypercall.

http://darnok.org/xen/devel.acpi-s3.v1.serial.log

If that patch above is present and I've cpufreq=xen on the Xen
hypervisor then Linux kernel gets unstuck and returns to userspace:

http://darnok.org/xen/devel.acpi-s3.v0.serial.log

(however, if I set cpuidle=0 cpufreq=none on the hypervisor line and
have the 9f301b0a0081676dfc71b7f0898295e6bcba391a patch it still
gets stuck).

I figured that the primary reason the guest is allowed to
exit is SCHEDOP_block loop is b/c the pm_idle call is set to the
acp_processor_idle which does "something" extra after the machine comes
out of a S3 suspend.

Any ideas?

             reply	other threads:[~2011-06-16 22:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 22:57 Konrad Rzeszutek Wilk [this message]
2011-06-17  2:21 ` Question about Xen S3 and resume code - Linux dom0 never exits the xen_safe_halt hypercall after resume Tian, Kevin
2011-06-20 12:36   ` Konrad Rzeszutek Wilk
2011-06-20 23:22     ` Tian, Kevin
2011-06-30  5:34       ` Tian, Kevin
2011-06-30 16:31         ` Konrad Rzeszutek Wilk
2011-06-30 22:13           ` Konrad Rzeszutek Wilk
2011-07-01  2:11             ` Tian, Kevin
2011-07-01  2:10           ` Tian, Kevin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110616225739.GA8714@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ke.yu@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.