All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Schiers <carsten@schiers.de>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: AW: RE: RE: RE: No C-States any longer...
Date: Thu, 16 Jun 2011 08:47:53 +0200	[thread overview]
Message-ID: <27407493.491308206873767.JavaMail.root@uhura> (raw)

Maybe a dump question, but in the beginning of our discussion, we had:

>> In drivers/scpi/processor_idle.c:
...
>> On a working Intel machine, it will go through it like this:
>> 
>>   - acpi_processor_get_power_info_cst, which returns 0
>>   - acpi_processor_get_power_info_default
>>   - later acpi_processor_power_verify will find some c-states
>
>this is expected sequence
>
>> 
>> On my non-working AMD machine, it will go through like this:
>>   - acpi_processor_get_power_info_cst, which returns -ENODEV
>>   - acpi_processor_get_power_info_fadt, which also return -ENODEV
>>   - this result is returned

There is a comment in acpi_processor_get_power_info_default it is
said that all processors need to support C1 at least. So (hypothesis), 
if my BIOS is not implemented as specified (neither _CST nor PBLK), 
shouldn't acpi_processor_get_power_info_default also bee called on my 
machine? Is the code exiting too early?

Carsten.

             reply	other threads:[~2011-06-16  6:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  6:47 Carsten Schiers [this message]
2011-06-16  7:12 ` RE: RE: RE: No C-States any longer Tian, Kevin
  -- strict thread matches above, loose matches on Subject: below --
2011-06-22 11:36 AW: " Carsten Schiers
2011-06-10  8:48 Tian, Kevin
2011-06-10 14:56 ` AW: " 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=27407493.491308206873767.JavaMail.root@uhura \
    --to=carsten@schiers.de \
    --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.