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-ia64-devel

RE: [Xen-devel] Re: [Xen-ia64-devel] [PATCH 0/3] IA64: add cpufreq suppo

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: [Xen-ia64-devel] [PATCH 0/3] IA64: add cpufreq support
From: "Yu, Ke" <ke.yu@xxxxxxxxx>
Date: Fri, 3 Oct 2008 14:16:54 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-ia64-devel@xxxxxxxxxxxxxxxxxxx" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 02 Oct 2008 23:17:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20081002081805.GE10658%yamahata@xxxxxxxxxxxxx>
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>
References: <49582C73AC36CC4C8C6C42390304E81C0887A9D794@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20081002081805.GE10658%yamahata@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckkZ6+00mEahbTsTZCOhhFSVmAmMAAtbHTg
Thread-topic: [Xen-devel] Re: [Xen-ia64-devel] [PATCH 0/3] IA64: add cpufreq support
Hi Isaku,

I tried your updated patch, and xenpm works in my IPF box. the attached is the 
xenpm output.

>From you xenpm output, one possible reason is that the DBS (alias of Px) 
>feature is not enabled in BIOS, thus xen can not get enough Px information to 
>initialize cpufreq driver. You can double confirm by:
- check BIOS to see if DBS is enabled.
- or try the native linux (e.g. RHEL5), to see if the cpufreq works.

Also, it will be helpful if you can attach the xen serial log. please add 
"loglvl=info" to elilo xen option, to make sure cpufreq information is printed.

Best Regards
Ke

Isaku Yamahata wrote:
> Hi, Yu.
> Thnaks for updating the patches while you're off.
>
> I applied your patch with some style fixes and tried xenpm.
> (I attached the fixed patch. Please confirm I didn't breake them.)
> Then I got the followings. (NOTE: I added cpufreq=xen to xen boot
> option) Doesn't xenpm work on ia64? Or is there another way to test
> them?
>
> # xenpm
> Xen cpuidle is not enabled!
> failed to get max P-state
>
> thanks,
>
> On Sat, Sep 27, 2008 at 10:11:29AM +0800, Yu, Ke wrote:
>> This patchset add cpufreq support for ia64 platform. The logic is
>> borrowed from linux kernel and ported to xen. The common cpufreq
>> infrastructure is already in xen and works in x86 side, so this
>> patchset reuse the common infrastructure and add ia64 specific
>> driver and cpufreq notify hypercall.
>>
>> Hypervisor side:
>> 1. px-xen-ipf-driver: add cpufreq ia64 driver
>> 2 .px-xen-ipf-hypercall: implement ia64 cpufreq notify hypercall
>>
>> Dom0 side:
>> 1. px-dom0-add-ia64-hypercall.patch: add ia64 cpufreq notify
>> hypercall
>>
>> Signed-off-by:  Liu Jinsong <jinsong.liu@xxxxxxxxx>
>>                 Yu Ke <ke.yu@xxxxxxxxx>
>>
>> BTW, this patchset depends on the xen-unstable tree
>> (http://xenbits.xensource.com/staging/xen-unstable.hg) cset 18550,
>> 18551, 18552, and linux xen tree
>> (http://xenbits.xensource.com/linux-2.6.18-xen.hg) cset 681, which
>> restructure the common cpufreq code for ia64. so ia64 tree need to
>> sync before applying this patchset.
>>
>>
>> _______________________________________________
>> Xen-ia64-devel mailing list
>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-ia64-devel

Attachment: xenpm.log
Description: xenpm.log

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