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] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen

To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 26 Jan 2008 08:16:12 +0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 26 Jan 2008 00:16:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1449F58C868D8D4E9C72945771150BDF02077261@xxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchfqSS0Yzu1EMucEdyNUQAWy6hiGQAC1IswAA/P2j0=
Thread-topic: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
User-agent: Microsoft-Entourage/11.3.6.070618
On 26/1/08 00:54, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> wrote:

>> It'd be useful to have each tracing line stamped with the CPU
>> that it comes from. As it is the tracing looks very suspect
>> because the systimes on adjacent lines are much less than
>> one second, and calibration is supposed to happen no more
>> than once per second.
> 
> Keir -
> 
> There seems to be a bug in continue_hypercall_on_cpu().
> I'm getting vcpu_set_affinity() failures with error code
> -22.  Any idea what that is?

Oh crap, of course:
 * cpufreq=dom0-kernel implies dom0_vcpus_pin
 * dom0_vcpus_pin stops dom0 from migrating its VCPUs among physical CPUs
 * The check is enforced in vcpu_set_affinity(), and unfortunately causes
continue_hypercall_on_cpu() to fail

That is such an obvious bug. :-(

vcpu_set_affinity() needs to not check dom0_vcpus_pin when called from
continue_hypercall_on_cpu(). I will cook up a patch...

 Thanks!
 Keir



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

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