All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Yu Ke <ke.yu@intel.com>
Subject: Re: 2.6.39 dom0 xen power management test
Date: Fri, 20 May 2011 14:09:05 -0400	[thread overview]
Message-ID: <20110520180905.GD30367@dumpdata.com> (raw)
In-Reply-To: <838094002.20110520195747@eikelenboom.it>

On Fri, May 20, 2011 at 07:57:47PM +0200, Sander Eikelenboom wrote:
> Hi Konrad / Yu Ke,
> 
> I have tried konrad's master tree:

Might want to try devel/next-2.6.39. It has the CPU freq and S3 patches in it.
I am still working through them, but they do seem to work (I can suspend
and resume a machine).

The #master has the ones that have been cleaned up and are slowly going
to make their path through the maintainers. The ACPI/S#/CPU freq aren't there
yet.

> 
> commit 329408d788f62629131ea28c112e973878d52c9e
> Merge: e370fe2 773f8cf
> Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Date:   Thu May 19 14:37:32 2011 -0400
> 
> Merge branch 'linux-next'
> 
> 
> With a xen-4.1.0 hypervisor, on my AMD x6 phenom.
> Curious if Xen Power Management would work...
> 
> Output of all xenpm get* commands is attached, prefix 32 is with a stable working 2.6.32.35 kernel from jeremy's tree with working xenpm.
> prefix 39 is with the kernel from the tree mentoined above.
> 
> There are differences in  cpu-idle-states (C0 and C1 state are not reported on .39)
> and cpu-freq-states/para (which fails entirely on .39)
> 
> But it doesn't crash .. just fails .. so that's positive ! :-)

HA!
> Of course i'm willing to give any more information or test additional patches.
> 
> 
> Will let it run for the night on 2.6.39 to see how blkback works !

Excellent.

  reply	other threads:[~2011-05-20 18:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 17:57 2.6.39 dom0 xen power management test Sander Eikelenboom
2011-05-20 18:09 ` Konrad Rzeszutek Wilk [this message]
2011-05-20 22:19   ` Sander Eikelenboom
2011-05-21  7:42   ` Sander Eikelenboom
2011-05-23 11:17     ` Stefano Stabellini
2011-05-23 11:54       ` Sander Eikelenboom
2011-05-23 13:03       ` Sander Eikelenboom
2011-05-23 13:59         ` Stefano Stabellini
2011-05-23 14:55           ` Sander Eikelenboom

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=20110520180905.GD30367@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ke.yu@intel.com \
    --cc=linux@eikelenboom.it \
    --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.