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

Re: [Xen-devel] Frequency scaling not working

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Frequency scaling not working
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Tue, 24 Apr 2007 17:31:43 +0100
Cc: sriram govindan <sriram_ite@xxxxxxxxxxx>
Delivery-date: Tue, 24 Apr 2007 09:32:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <920121.94447.qm@xxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <920121.94447.qm@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6
> I installed the latest version of xen (3.0.4_1). I used userspace governor
> to change frequency of my xeon dual processor SMT. The driver used is
> p4-clockmod.
>
> Changes to the frequency (through the /sys interface) is not getting
> reflected to the hardware. From previous posts, i understand that rdmsr and
> wrmsr has to be replaced with dom0_msr operations. Even after doing the
> modifications, still the frequency is not getting changed and the domain0
> hypercall is returning a negative value when reads and writes are made to
> the dom0_msr.

I'm not sure frequency scaling is supported by 3.0.4, although I expect it 
will be one day.

> Also, In xen SMT seems to have some problems. cpumask (affected cpus) does
> not seem to include the hyperthread.

I'm not entirely sure I understand the question here...  The hyperthreads 
should be enumerated as separate processors and Just Work.  What behaviour 
are you seeing?

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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

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