From: Carsten Schiers <carsten@schiers.de>
To: "Tian, Kevin" <kevin.tian@intel.com>, mark.langsdorf@amd.com
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"Yu, Ke" <ke.yu@intel.com>
Subject: AW: RE: RE: RE: RE: RE: No C-States any longer...
Date: Thu, 16 Jun 2011 08:22:22 +0200 [thread overview]
Message-ID: <2528978.431308205342002.JavaMail.root@uhura> (raw)
>In your case there's no _CST found, and then no PBLK found.
The only thing that are giveing me hope are:
- it worked once (Xenified 2.6.18.8)
- FADT contains C2/C3 Latency information (_CST Support is 00 BTW)
>do you mean the latest PVOPS from Konzad? I don't think Cstate/Pstate patches
>have been carried there, which still stay in Jeremy's tree.
Currently I tried with stable 2.6.32.x from Jeremy and Debian Squeeze, as Konrad
said, his 2.6.39.x would expose C-States for him, what did not before, I will try
his 2.6.39.x next. I can check this and native boot results tonight.
>Since this is the AMD box which I'm not familiar with, also CC Mark here who is
>the owner for power management on AMD boxes.
Mark, I realy hope you have an idea. This is - by the way - the X3 400e I just bought
because I never succeeded in getting TSC hickup-free >2.6.18 systems with my 4050e,
you eventually remember...?
Carsten.
next reply other threads:[~2011-06-16 6:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 6:22 Carsten Schiers [this message]
2011-06-16 6:30 ` RE: RE: RE: RE: RE: No C-States any longer Tian, Kevin
-- strict thread matches above, loose matches on Subject: below --
2011-06-15 13:06 Konrad Rzeszutek Wilk
2011-06-15 13:17 ` AW: " Carsten Schiers
2011-06-15 9:12 Carsten Schiers
2011-06-15 9:03 Carsten Schiers
2011-06-15 8:15 Tian, Kevin
2011-06-15 9:14 ` AW: " Carsten Schiers
2011-06-12 9:01 Tian, Kevin
2011-06-13 13:21 ` AW: " Carsten Schiers
2011-06-13 20:27 ` Carsten Schiers
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=2528978.431308205342002.JavaMail.root@uhura \
--to=carsten@schiers.de \
--cc=Ian.Campbell@citrix.com \
--cc=ke.yu@intel.com \
--cc=kevin.tian@intel.com \
--cc=mark.langsdorf@amd.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.