From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
morten.rasmussen@arm.com, qperret@google.com,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH v2 0/2] sched, arm64: enable CONFIG_SCHED_SMT for arm64
Date: Thu, 27 Feb 2020 19:14:31 +0000 [thread overview]
Message-ID: <20200227191433.31994-1-valentin.schneider@arm.com> (raw)
Hi,
Strictly speaking those two patches are independent, but I figured it would
make sense to send them together (since one led to the other).
Patch 1 adds a sanity check against EAS + SMT.
Patch 2 enables CONFIG_SCHED_SMT in the arm64 defconfig.
Cheers,
Valentin
Revisions
=========
v1 -> v2
--------
o Collected Reviewed-by, Acked-by (Dietmar, Quentin)
o Added a warning when disabling EAS due to SMT (Dietmar)
Valentin Schneider (2):
sched/topology: Don't enable EAS on SMT systems
arm64: defconfig: enable CONFIG_SCHED_SMT
arch/arm64/configs/defconfig | 1 +
kernel/sched/topology.c | 12 ++++++++++--
2 files changed, 11 insertions(+), 2 deletions(-)
--
2.24.0
next reply other threads:[~2020-02-27 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 19:14 Valentin Schneider [this message]
2020-02-27 19:14 ` [PATCH v2 1/2] sched/topology: Don't enable EAS on SMT systems Valentin Schneider
2020-03-06 14:42 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2020-02-27 19:14 ` [PATCH v2 2/2] arm64: defconfig: enable CONFIG_SCHED_SMT Valentin Schneider
2020-03-06 14:42 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2020-03-02 13:42 ` [PATCH v2 0/2] sched, arm64: enable CONFIG_SCHED_SMT for arm64 Peter Zijlstra
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=20200227191433.31994-1-valentin.schneider@arm.com \
--to=valentin.schneider@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=qperret@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®