WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

AW: RE: RE: RE: [Xen-devel] No C-States any longer...

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: AW: RE: RE: RE: [Xen-devel] No C-States any longer...
From: Carsten Schiers <carsten@xxxxxxxxxx>
Date: Thu, 16 Jun 2011 08:47:53 +0200
Cc:
Delivery-date: Wed, 15 Jun 2011 23:48:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple; d=mail.zeus06.de; h=date: from:to:message-id:subject:mime-version:content-type; q=dns/txt; s= beta; bh=/76Cb1gtWypKtWwl3Wy7T+j1i1MoRrLv+m6WHjTVIfs=; b=RHQI2bB rnhK+g7YpfGTLbdKYKH3qPRejhmDwYCqL+XKxuo9i1HcKxnDCmfFibOOnGM48kI9 NcvUW3tLvxGKIj0YCxsRjYDcN4BpmDe90fXNoR+l9m0EjBnwDNjVMUrmcETkvXUc 6OM7NJZRK5x5GQYwSrMdnGtj2mL7uv1rlEB4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>