From: Arjan van de Ven <arjan@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Saravana Kannan <skannan@codeaurora.org>,
cpufreq <cpufreq@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Dave Jones <davej@redhat.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Thomas Renninger <trenn@suse.de>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: CPUfreq - udelay() interaction issues
Date: Sat, 24 Apr 2010 16:20:36 -0700 [thread overview]
Message-ID: <20100424162036.47cba620@infradead.org> (raw)
In-Reply-To: <20100424210042.GA2371@Krystal>
On Sat, 24 Apr 2010 17:00:42 -0400
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> > Case 2: multi core or HT, TSC is variable with CPU frequency.
> > This is the really sucky case, since logical CPU 0's tsc frequency
> > in part depends on what logical CPU 1 will do etc. No good answer
> > for this other than assuming the worst. Based on your document
> > these do actually exist in early P4 cpus.
>
> Keeping track of the cpu frequency changes can help here. Along with
> periodic resynchronization if cpu clocks drift too far apart. I've
> done that for the LTTng omap3 trace clock.
it's not enough; voting does not work that way.
the way voting ends up working is that the hardware runs the maximum of
the various frequency requests ... but for the threads that are not
idle.
so if cpu 1 goes to a high frequency, cpu 0 goes up to.. until cpu 1
goes idle; then only cpu 0's value is in use.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2010-04-24 23:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 3:34 CPUfreq - udelay() interaction issues Saravana Kannan
2010-04-22 21:22 ` Saravana Kannan
2010-04-22 23:18 ` Thomas Renninger
2010-04-22 23:37 ` Saravana Kannan
2010-04-22 23:21 ` Saravana Kannan
2010-04-23 18:40 ` Mathieu Desnoyers
2010-04-23 19:22 ` Arjan van de Ven
2010-04-23 19:55 ` Mathieu Desnoyers
2010-04-24 18:56 ` Arjan van de Ven
2010-04-24 21:00 ` Mathieu Desnoyers
2010-04-24 23:20 ` Arjan van de Ven [this message]
2010-04-24 2:57 ` Saravana Kannan
2010-04-24 2:49 ` Saravana Kannan
2010-04-24 5:56 ` Pavel Machek
2010-04-24 13:58 ` Mathieu Desnoyers
2010-04-27 23:41 ` Saravana Kannan
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=20100424162036.47cba620@infradead.org \
--to=arjan@infradead.org \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=skannan@codeaurora.org \
--cc=trenn@suse.de \
--cc=venkatesh.pallipadi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).