From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Cc: lizefan@huawei.com, tj@kernel.org, hannes@cmpxchg.org,
mingo@kernel.org, peterz@infradead.org,
vincent.guittot@linaro.org, Dietmar.Eggemann@arm.com,
morten.rasmussen@arm.com, qperret@google.com
Subject: [PATCH v4 0/2] sched/topology: Asymmetric topologies fixes
Date: Wed, 23 Oct 2019 16:37:43 +0100 [thread overview]
Message-ID: <20191023153745.19515-1-valentin.schneider@arm.com> (raw)
Hi,
I got a nice splat while testing out the toggling of
sched_asym_cpucapacity, so this is a cpuset fix plus a topology patch.
Details are in the logs.
v2 changes:
- Use static_branch_{inc,dec} rather than enable/disable
v3 changes:
- New patch: add fix for empty cpumap in sched domain rebuild
- Move static_branch_dec outside of RCU read-side section (Quentin)
v4 changes:
- Patch 1/2: Directly tweak the cpuset array (Dietmar)
- Patch 2/2: Add an example to the changelog (Dietmar)
Cheers,
Valentin
Valentin Schneider (2):
sched/topology: Don't try to build empty sched domains
sched/topology: Allow sched_asym_cpucapacity to be disabled
kernel/cgroup/cpuset.c | 3 ++-
kernel/sched/topology.c | 11 +++++++++--
2 files changed, 11 insertions(+), 3 deletions(-)
--
2.22.0
next reply other threads:[~2019-10-23 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 15:37 Valentin Schneider [this message]
2019-10-23 15:37 ` [PATCH v4 1/2] sched/topology: Don't try to build empty sched domains Valentin Schneider
2019-10-24 16:19 ` Dietmar Eggemann
2019-10-24 16:45 ` Valentin Schneider
2019-10-29 9:52 ` [tip: sched/urgent] " tip-bot2 for Valentin Schneider
2019-10-31 16:23 ` [PATCH v4 1/2] " Michal Koutný
2019-10-31 17:23 ` Valentin Schneider
2019-11-01 10:08 ` Michal Koutný
2019-10-23 15:37 ` [PATCH v4 2/2] sched/topology: Allow sched_asym_cpucapacity to be disabled Valentin Schneider
2019-10-29 9:52 ` [tip: sched/urgent] " tip-bot2 for Valentin Schneider
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=20191023153745.19515-1-valentin.schneider@arm.com \
--to=valentin.schneider@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=tj@kernel.org \
--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).