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 v3 0/2] sched/topology: Asymmetric topologies fixes
Date: Tue, 15 Oct 2019 16:42:48 +0100 [thread overview]
Message-ID: <20191015154250.12951-1-valentin.schneider@arm.com> (raw)
Hi,
I got a nice splat while testing out the toggling of
sched_asym_cpucapacity, so this gets a new 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)
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 | 8 ++++++++
kernel/sched/topology.c | 11 +++++++++--
2 files changed, 17 insertions(+), 2 deletions(-)
--
2.22.0
next reply other threads:[~2019-10-15 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 15:42 Valentin Schneider [this message]
2019-10-15 15:42 ` [PATCH v3 1/2] sched/topology: Don't try to build empty sched domains Valentin Schneider
2019-10-22 11:43 ` Dietmar Eggemann
2019-10-22 12:46 ` Valentin Schneider
2019-10-23 11:46 ` Dietmar Eggemann
2019-10-23 14:12 ` Valentin Schneider
2019-10-15 15:42 ` [PATCH v3 2/2] sched/topology: Allow sched_asym_cpucapacity to be disabled Valentin Schneider
2019-10-23 8:45 ` Dietmar Eggemann
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=20191015154250.12951-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