From: Lina Iyer <lina.iyer@linaro.org>
To: Kevin Hilman <khilman@linaro.org>
Cc: daniel.lezcano@linaro.org, ulf.hansson@linaro.org,
linux-pm@vger.kernel.org, tglx@linutronix.de, rjw@rjwysocki.net,
Praveen Chidambaram <pchidamb@codeaurora.org>
Subject: Re: [PATCH v2 2/4] QoS: Enhance framework to support per-cpu PM QoS request
Date: Mon, 18 Aug 2014 18:34:05 -0600 [thread overview]
Message-ID: <20140819003405.GB52513@ilina-mac.local> (raw)
In-Reply-To: <7h4mx9wdxe.fsf@paris.lan>
On Mon, Aug 18, 2014 at 04:55:41PM -0700, Kevin Hilman wrote:
>Hi Lina,
>
>Lina Iyer <lina.iyer@linaro.org> writes:
>
>> QoS request can be better optimized if the request can be set only for
>> the required cpus and not all cpus. This helps save power on other
>> cores, while still gauranteeing the quality of service on the desired
>> cores.
>>
>> Add a new enumeration to specify the PM QoS request type. The enums help
>> specify what is the intended target cpu of the request.
>>
>> Enhance the QoS constraints data structures to support target value for
>> each core. Requests specify if the QoS is applicable to all cores
>> (default) or to a selective subset of the cores or to a core(s).
>>
>> Idle and interested drivers can request a PM QoS value for a constraint
>> across all cpus, or a specific cpu or a set of cpus. Separate APIs have
>> been added to request for individual cpu or a cpumask. The default
>> behaviour of PM QoS is maintained i.e, requests that do not specify a
>> type of the request will continue to be effected on all cores.
>>
>> The userspace sysfs interface does not support setting cpumask of a PM
>> QoS request.
>>
>> Signed-off-by: Praveen Chidambaram <pchidamb@codeaurora.org>
>> Signed-off-by: Lina Iyer <lina.iyer@linaro.org>
>
>I agree this is a needed feature. I didn't study it in detail yet, but
>after a quick glance, it looks like a good approach.
>
>However, I did start to wonder how this will behave in the context of
>the hotplug. For example, what if a constraint is setup with a cpumask,
>then one of those CPUs is hotplugged away.
>
Thanks for bringing it up. I forgot to mention this in the series, but
well, it can be addressed.
When a core is hotplugged, the IRQ migrates to the next online in the
smp_affinity. The QoS code would work in the hotplug case as well, with
a simple change. The current code does not send affinity_notifications
correctly because of a direct call to irq_chip->irq_set_affinity()
instead of calling the generic irq affinity api.
This is the simple change that needs to be made. I will submit a patch
for that.
In arm64/kernel/irq.c
- c = irq_data_get_irq_chip(d);
- if (!c->irq_set_affinity)
- pr_debug("IRQ%u: unable to set affinity\n", d->irq);
- else if (c->irq_set_affinity(d, affinity, true) == IRQ_SET_MASK_OK && ret)
- cpumask_copy(d->affinity, affinity);
-
- return ret;
+ return __irq_set_affinity_locked(d, affinity) == 0;
>Kevin
next prev parent reply other threads:[~2014-08-19 0:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 16:01 [PATCH v2 0/4] PM QoS: per-cpu PM QoS support Lina Iyer
2014-08-13 16:01 ` [PATCH v2 1/4] QoS: Modify data structures and function arguments for scalability Lina Iyer
2014-08-18 23:38 ` Kevin Hilman
2014-08-27 17:44 ` Kevin Hilman
2014-08-13 16:01 ` [PATCH v2 2/4] QoS: Enhance framework to support per-cpu PM QoS request Lina Iyer
2014-08-15 12:37 ` Javi Merino
2014-08-15 15:06 ` Lina Iyer
2014-08-18 23:55 ` Kevin Hilman
2014-08-19 0:34 ` Lina Iyer [this message]
2014-08-27 18:01 ` Kevin Hilman
2014-08-27 20:13 ` Lina Iyer
2014-08-13 16:01 ` [PATCH v2 3/4] irq: Allow multiple clients to register for irq affinity notification Lina Iyer
2014-08-19 0:04 ` Kevin Hilman
2014-08-19 0:17 ` Lina Iyer
2014-08-13 16:01 ` [PATCH v2 4/4] QoS: Enable PM QoS requests to apply only on smp_affinity of an IRQ Lina Iyer
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=20140819003405.GB52513@ilina-mac.local \
--to=lina.iyer@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=khilman@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=pchidamb@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@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