From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ionela Voinescu <ionela.voinescu@arm.com>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH V3 1/2] topology: Allow multiple entities to provide sched_freq_tick() callback
Date: Fri, 19 Feb 2021 15:18:09 +0530 [thread overview]
Message-ID: <20210219094809.ktvwx3pggnvatl3q@vireshk-i7> (raw)
In-Reply-To: <20210219094440.GA29843@arm.com>
On 19-02-21, 09:44, Ionela Voinescu wrote:
> On Friday 19 Feb 2021 at 10:28:23 (+0530), Viresh Kumar wrote:
> > The very core routines (cpufreq_freq_transition_end() and
> > cpufreq_driver_fast_switch()) of the cpufreq core call
> > arch_set_freq_scale() today and this isn't going to change anytime
> > soon. If something gets changed there someone will need to see other
> > parts of the kernel which may get broken with that.
> >
>
> Yes, but it won't really be straightforward to notice this breakage if
> that happens, so in my opinion it was worth to keep that condition.
Right, but chances of that happening are close to zero right now. I
don't see any changes being made there in near future and so as we
agreed, lets leave it as is.
Btw, thanks for your feedback, it was indeed very valuable.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ionela Voinescu <ionela.voinescu@arm.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
linux-pm@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 1/2] topology: Allow multiple entities to provide sched_freq_tick() callback
Date: Fri, 19 Feb 2021 15:18:09 +0530 [thread overview]
Message-ID: <20210219094809.ktvwx3pggnvatl3q@vireshk-i7> (raw)
In-Reply-To: <20210219094440.GA29843@arm.com>
On 19-02-21, 09:44, Ionela Voinescu wrote:
> On Friday 19 Feb 2021 at 10:28:23 (+0530), Viresh Kumar wrote:
> > The very core routines (cpufreq_freq_transition_end() and
> > cpufreq_driver_fast_switch()) of the cpufreq core call
> > arch_set_freq_scale() today and this isn't going to change anytime
> > soon. If something gets changed there someone will need to see other
> > parts of the kernel which may get broken with that.
> >
>
> Yes, but it won't really be straightforward to notice this breakage if
> that happens, so in my opinion it was worth to keep that condition.
Right, but chances of that happening are close to zero right now. I
don't see any changes being made there in near future and so as we
agreed, lets leave it as is.
Btw, thanks for your feedback, it was indeed very valuable.
--
viresh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-19 9:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 10:48 [PATCH V3 0/2] cpufreq: cppc: Add support for frequency invariance Viresh Kumar
2021-01-28 10:48 ` Viresh Kumar
2021-01-28 10:48 ` [PATCH V3 1/2] topology: Allow multiple entities to provide sched_freq_tick() callback Viresh Kumar
2021-01-28 10:48 ` Viresh Kumar
2021-02-03 11:45 ` Ionela Voinescu
2021-02-03 11:45 ` Ionela Voinescu
2021-02-05 9:14 ` Viresh Kumar
2021-02-05 9:14 ` Viresh Kumar
2021-02-17 0:24 ` Ionela Voinescu
2021-02-17 0:24 ` Ionela Voinescu
2021-02-17 4:25 ` Viresh Kumar
2021-02-17 4:25 ` Viresh Kumar
2021-02-17 11:30 ` Ionela Voinescu
2021-02-17 11:30 ` Ionela Voinescu
2021-02-17 11:40 ` Viresh Kumar
2021-02-17 11:40 ` Viresh Kumar
2021-02-17 11:57 ` Ionela Voinescu
2021-02-17 11:57 ` Ionela Voinescu
2021-02-18 7:23 ` Viresh Kumar
2021-02-18 7:23 ` Viresh Kumar
2021-02-18 9:33 ` Viresh Kumar
2021-02-18 9:33 ` Viresh Kumar
2021-02-18 16:36 ` Ionela Voinescu
2021-02-18 16:36 ` Ionela Voinescu
2021-02-19 4:58 ` Viresh Kumar
2021-02-19 4:58 ` Viresh Kumar
2021-02-19 9:44 ` Ionela Voinescu
2021-02-19 9:44 ` Ionela Voinescu
2021-02-19 9:48 ` Viresh Kumar [this message]
2021-02-19 9:48 ` Viresh Kumar
2021-01-28 10:48 ` [PATCH V3 2/2] cpufreq: cppc: Add support for frequency invariance Viresh Kumar
2021-01-28 10:48 ` Viresh Kumar
2021-02-18 16:35 ` Ionela Voinescu
2021-02-18 16:35 ` Ionela Voinescu
2021-02-22 11:00 ` Ionela Voinescu
2021-02-22 11:00 ` Ionela Voinescu
2021-02-22 11:04 ` Viresh Kumar
2021-02-22 11:04 ` Viresh Kumar
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=20210219094809.ktvwx3pggnvatl3q@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=will@kernel.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 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.