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: Tue, 29 Jan 2008 09:53:26 +0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 29 Jan 2008 01:54:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1449F58C868D8D4E9C72945771150BDF0207726A@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/P2j0ABsqr4AB6NDvwABlGPxs=
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 28/1/08 21:52, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> wrote:

>> Please test with latest xen-unstable. As of changeset 16897 I
>> have fixed the vcpu affinity change, so that should actually
>> work,
> 
> It doesn't, for some reason.  It seems to lock up on the
> 
> v->arch.schedule_tail = continue_hypercall_on_cpu_helper
> 
> for no reason that I can tell.  If I comment out that line,
> the system boots fine, but if that is in Xen, the machine
> softlocks shortly after starting cpufreq.  Unfortunately,
> cpufreq starts well before any console, so I can't get a
> lot of information out the system.
> 
> I'll continue working on this, but any advance would be
> appreciated.

As promised I've instrumented and kicked that code path, and I execute it
with no problems, with the VCPU concerned being correctly migrated before
and after the continue_hypercall_on_cpu() is executed. I've tried it with
'dom0_vcpus_pin' and also I've tried making fairly extreme calls to
cpu_frequency_change() inside the hypercall-continuation 'helper' function.
None of this causes my dom0 boot to hang. So it looks like something a bit
subtle must be going wrong on your test system.

 -- Keir



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

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