From: Valentin Schneider <valentin.schneider@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Benjamin GAIGNARD <benjamin.gaignard@st.com>,
Hugues FRUCHET <hugues.fruchet@st.com>,
"mchehab\@kernel.org" <mchehab@kernel.org>,
"mcoquelin.stm32\@gmail.com" <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"linux-media\@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-stm32\@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rjw\@rjwysocki.net" <rjw@rjwysocki.net>
Subject: Re: [PATCH] media: stm32-dcmi: Set minimum cpufreq requirement
Date: Wed, 03 Jun 2020 10:41:41 +0100 [thread overview]
Message-ID: <jhjmu5kiizu.mognet@arm.com> (raw)
In-Reply-To: <CAKfTPtCbM-w_0VrTB5tsSM5PKRtC44f3sSmAR=U=P3e3KQ+cMw@mail.gmail.com>
On 03/06/20 08:50, Vincent Guittot wrote:
> On Wed, 3 Jun 2020 at 09:34, Benjamin GAIGNARD <benjamin.gaignard@st.com> wrote:
>> On 6/2/20 3:35 PM, Valentin Schneider wrote:
>> > AFAIA streaming_start() is not necessarily executing on the same CPU as the
>> > one that will handle the interrupt. I was thinking you could use the IRQ's
>> > effective affinity as a hint of which CPU(s) to boost, i.e. something like:
>> >
>> > ---
>> > struct cpumask_var_t visited;
>> > struct irq_data *d = irq_get_irq_data(irq);
>> >
>> > err = alloc_cpumask_var(visited, GFP_KERNEL);
>> > /* ... */
>> > for_each_cpu(cpu, irq_data_get_effective_affinity_mask(d)) {
>> > /* check if not already spanned */
>> > if (cpumask_test_cpu(cpu, visited))
>> > continue;
>> >
>> > policy = cpufreq_cpu_get(cpu);
>> > cpumask_or(visited, visited, policy->cpus);
>> > /* do the boost for that policy here */
>> > /* ... */
>> > cpufreq_cpu_put(policy);
>> > }
>> > ---
>> >
>> > That of course falls apart when hotplug gets involved, and the effective
>> > affinity changes... There's irq_set_affinity_notifier() out there, but it
>> > seems it's only about the affinity, not the effective_affinity, I'm not
>> > sure how valid it would be to query the effective_affinity in that
>> > notifier.
>> If I wait to be in the irq it will be too late so I think I will do a
>> loop over all possible CPUs
>> before start the streaming to change the policies.
>
Yes, that's what I was thinking as well.
> Can't you use irq_get_affinity_mask and loop over it ?
>
In the end that's the only usable option, I think.
I was looking at alternatives because on arm64 (and AFAICT that applies
to arm too; see irq-gic.c::gic_set_affinity()) the affinity mask spans
all CPUs by default, while the effective affinity mask spans only the
CPU that will actually handle the IRQ (+ where its thread should run).
That said, using the effective mask that way does feel like an
implementation leak. Sadly I couldn't find any better way to minimize
the number of boosted frequency domains.
> Also You should better use freq_qos_add/remove_request during probe
> and remove of the driver and use freq_qos_update_request in
> dcmi_start/stop_streaming to set/unset your constraint.
>
prev parent reply other threads:[~2020-06-03 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 15:16 [PATCH] media: stm32-dcmi: Set minimum cpufreq requirement Benjamin Gaignard
2020-06-02 8:29 ` Hugues FRUCHET
2020-06-02 9:31 ` Valentin Schneider
2020-06-02 11:37 ` Benjamin GAIGNARD
2020-06-02 13:35 ` Valentin Schneider
2020-06-03 7:34 ` Benjamin GAIGNARD
2020-06-03 7:50 ` Vincent Guittot
2020-06-03 9:41 ` Valentin Schneider [this message]
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=jhjmu5kiizu.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=hugues.fruchet@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@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;
as well as URLs for NNTP newsgroup(s).