From: Xavian-Anderson Macpherson <Shingoshi@comcast.net>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
Date: Fri, 25 Jan 2008 15:31:07 -0800 [thread overview]
Message-ID: <479A713B.5040507@comcast.net> (raw)
In-Reply-To: <C3C01FB1.12D87%Keir.Fraser@cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1508 bytes --]
Are we in fact talking about the new Barcelona chips? If so, their
frequency settings are independent per core. Unless I have misunderstood
the question.
Shingoshi
Keir Fraser wrote:
> On 25/1/08 22:58, "Mark Langsdorf" <mark.langsdorf@amd.com> wrote:
>
>
>> I tried this suggestion and also implemented the trace function in
>> cpu_frequency_change() and local_time_calibration() you suggested in
>> a previous message.
>>
>> It made no discernable difference in my tests. I did high to low
>> and low to high changes roughly every five minutes, and always got
>> an excessive difference inside of Xen and usually got error messages
>> in Linux.
>>
>
> It's a bit confusing as to what is going on since there are 4 CPUs in the
> system. Are arbitrary or all CPUs changing frequency, or just one of them?
> Is the single-step PSTATE_CTRL MSR being used, or the multi-step FID_VID
> method where voltage adjustments are under software control? What is the
> system's CPU topology, and do any of the cores have their frequency controls
> tied together?
>
> 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
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2.1: Type: text/html, Size: 2298 bytes --]
[-- Attachment #1.2.2: 175753_mail.png --]
[-- Type: image/png, Size: 7620 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-01-25 23:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 17:52 [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors Mark Langsdorf
2008-01-22 21:16 ` Ian Pratt
2008-01-22 21:51 ` Keir Fraser
2008-01-23 2:04 ` [PATCH] Disable Xen PowerNow! support on Opteron2nd " Tian, Kevin
2008-01-23 15:17 ` [PATCH] Disable Xen PowerNow! support on Opteron 2nd " Langsdorf, Mark
2008-01-23 15:26 ` Keir Fraser
2008-01-23 15:31 ` Langsdorf, Mark
2008-01-23 15:41 ` Keir Fraser
2008-01-25 17:19 ` Stephen C. Tweedie
2008-01-25 17:46 ` John Levon
2008-01-25 18:18 ` Keir Fraser
2008-01-25 18:12 ` Keir Fraser
2008-01-23 20:27 ` Ian Pratt
2008-01-23 21:34 ` Langsdorf, Mark
2008-01-23 22:34 ` Ian Pratt
2008-01-23 23:04 ` Langsdorf, Mark
2008-01-23 23:06 ` Keir Fraser
2008-01-25 22:58 ` Mark Langsdorf
2008-01-25 23:22 ` Keir Fraser
2008-01-25 23:31 ` Xavian-Anderson Macpherson [this message]
2008-01-25 23:41 ` [PATCH] Disable Xen PowerNow! support on Opteron2nd " Ian Pratt
2008-01-26 0:32 ` [PATCH] Disable Xen PowerNow! support on Opteron 2nd " Langsdorf, Mark
2008-01-26 0:54 ` Langsdorf, Mark
2008-01-26 8:16 ` Keir Fraser
2008-01-26 11:30 ` Keir Fraser
2008-01-28 21:52 ` Langsdorf, Mark
2008-01-28 22:00 ` Keir Fraser
2008-01-29 9:53 ` Keir Fraser
2008-01-29 10:32 ` Keir Fraser
2008-01-29 11:20 ` Keir Fraser
2008-01-29 16:13 ` Langsdorf, Mark
2008-02-11 11:27 ` Ralf Schenk
2008-02-01 16:39 ` Langsdorf, Mark
2008-02-02 10:34 ` Keir Fraser
2008-02-04 21:52 ` Langsdorf, Mark
2008-02-04 22:41 ` Keir Fraser
2008-01-25 23:39 ` Ian Pratt
2008-01-26 0:21 ` Langsdorf, Mark
2008-01-23 22:34 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=479A713B.5040507@comcast.net \
--to=shingoshi@comcast.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.