From: Tejun Heo <tj@kernel.org>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: Valentin Schneider <vschneid@redhat.com>,
kprateek.nayak@amd.com, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org, tglx@kernel.org,
mgorman@suse.de, bsegall@google.com, arighi@nvidia.com,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, vincent.guittot@linaro.org
Subject: Re: [PATCH 2/3] sched: Simplify ifdeffery around cpu_smt_mask
Date: Mon, 11 May 2026 08:46:04 -1000 [thread overview]
Message-ID: <agIj7Eq9sMoWS9bX@slm.duckdns.org> (raw)
In-Reply-To: <09edb32d-774a-4780-bb05-cb227f6cddb7@linux.ibm.com>
Hello,
On Mon, May 11, 2026 at 08:07:23PM +0530, Shrikanth Hegde wrote:
> sched_ext just added the ifdefs for the masks i think.
> It has sched_smt_active() already.
Yeah, sched_ext parts look good to me.
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2026-05-11 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 11:00 [PATCH 0/3] sched: Simplify ifdeffery around CONFIG_SCHED_SMT Shrikanth Hegde
2026-05-06 11:00 ` [PATCH 1/3] topology: Introduce cpu_smt_mask for CONFIG_SCHED_SMT=n Shrikanth Hegde
2026-05-06 11:00 ` [PATCH 2/3] sched: Simplify ifdeffery around cpu_smt_mask Shrikanth Hegde
2026-05-11 12:53 ` Valentin Schneider
2026-05-11 14:37 ` Shrikanth Hegde
2026-05-11 18:46 ` Tejun Heo [this message]
2026-05-12 10:13 ` Shrikanth Hegde
2026-05-12 10:58 ` Valentin Schneider
2026-05-06 11:00 ` [PATCH 3/3] sched/fair: Add compile time check in fastpaths for CONFIG_SCHED_SMT=n Shrikanth Hegde
2026-05-12 10:59 ` [PATCH 0/3] sched: Simplify ifdeffery around CONFIG_SCHED_SMT Valentin Schneider
2026-05-12 12:25 ` Shrikanth Hegde
2026-05-12 15:32 ` 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=agIj7Eq9sMoWS9bX@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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