Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1692884

Re: [Eas-dev] [PATCH V3 2/3] cpufreq: schedutil: Process remote callback for shared policies

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [Eas-dev] [PATCH V3 2/3] cpufreq: schedutil: Process remote callback for shared policies
Date 2017-07-20 14:30 +0200
Message-ID <u5iKF-7kM-71@gated-at.bofh.it> (permalink)
References <u2G6J-2a4-3@gated-at.bofh.it> <u2G6J-2a4-1@gated-at.bofh.it> <u2Ydj-5eG-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Jul 13, 2017 at 07:02:37PM -0700, Saravana Kannan wrote:
> In all Qualcomm chipsets (well, at least the ones that have been used in
> Android devices so far), we can switch the frequency of any CPU from any
> other CPU. If we can do that even without fast switching, why wouldn't any
> theoretical fast switching be incapable of supporting this? Is this a
> limitation specific to x86 that we are assuming all architectures and
> platforms are going to have?

So the typical implementation of fast switching we're thinking of is the
CPU writing the DVFS request into a machine register. Now machine
registers are typically per logical CPU.

What style of fast switching were you thinking of?

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [Eas-dev] [PATCH V3 2/3] cpufreq: schedutil: Process remote  callback for shared policies Peter Zijlstra <peterz@infradead.org> - 2017-07-20 14:30 +0200
  Re: [Eas-dev] [PATCH V3 2/3] cpufreq: schedutil: Process remote  callback for shared policies Sudeep Holla <sudeep.holla@arm.com> - 2017-07-20 17:20 +0200
  Re: [Eas-dev] [PATCH V3 2/3] cpufreq: schedutil: Process remote callback  for shared policies Saravana Kannan <skannan@codeaurora.org> - 2017-07-26 23:00 +0200

csiph-web