mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Saravana Kannan <skannan@codeaurora.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Rafael Wysocki <rjw@rjwysocki.net>,
	Ingo Molnar <mingo@redhat.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	smuckle.linux@gmail.com, eas-dev@lists.linaro.org
Subject: Re: [Eas-dev] [PATCH V3 2/3] cpufreq: schedutil: Process remote callback for shared policies
Date: Thu, 20 Jul 2017 16:11:38 +0100	[thread overview]
Message-ID: <fec9b074-49d2-18ea-a259-4b1b372deae7@arm.com> (raw)
In-Reply-To: <20170720122239.licc6yjd7jwipcvk@hirez.programming.kicks-ass.net>



On 20/07/17 13:22, Peter Zijlstra wrote:
> 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.
> 

But, if ARM decides to architect and move to it to a system/machine
register, we will end up with the same limitation :( IMO.

For now with SCMI kind of interface, there's no such limitation as
yoalready mentioned in the follow up email.
-- 
Regards,
Sudeep

  reply	other threads:[~2017-07-20 15:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  6:44 [PATCH V3 0/3] sched: cpufreq: Allow remote callbacks Viresh Kumar
2017-07-13  6:44 ` [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks Viresh Kumar
2017-07-21 13:03   ` Peter Zijlstra
2017-07-24 11:01     ` Viresh Kumar
2017-07-24 13:47       ` Peter Zijlstra
2017-07-26  6:29         ` Viresh Kumar
2017-07-26  8:12           ` Peter Zijlstra
2017-07-26 17:26           ` Rafael J. Wysocki
2017-07-26 21:00     ` [Eas-dev] " Saravana Kannan
2017-07-27  3:30       ` Viresh Kumar
2017-07-27 19:55         ` Saravana Kannan
2017-07-28  4:33           ` Joel Fernandes (Google)
2017-07-28  6:00           ` Viresh Kumar
2017-07-28 21:05             ` Saravana Kannan
2017-07-31  3:58               ` Viresh Kumar
2017-07-13  6:44 ` [PATCH V3 2/3] cpufreq: schedutil: Process remote callback for shared policies Viresh Kumar
2017-07-14  2:02   ` [Eas-dev] " Saravana Kannan
2017-07-14  5:03     ` Viresh Kumar
2017-07-20 13:58       ` Peter Zijlstra
2017-07-20 12:22     ` Peter Zijlstra
2017-07-20 15:11       ` Sudeep Holla [this message]
2017-07-26 20:56       ` Saravana Kannan
2017-07-13  6:44 ` [PATCH V3 3/3] cpufreq: governor: " Viresh Kumar
2017-07-13 15:17 ` [PATCH V3 0/3] sched: cpufreq: Allow remote callbacks Rafael J. Wysocki

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=fec9b074-49d2-18ea-a259-4b1b372deae7@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=eas-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=skannan@codeaurora.org \
    --cc=smuckle.linux@gmail.com \
    --cc=viresh.kumar@linaro.org \
    /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

all inboxes | Powered by JetHome®