From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
Klaus Kusche <klaus.kusche@computerix.info>
Subject: Re: [PATCH] x86/itmt: Don't make ITMT enablement depend on debugfs
Date: Tue, 11 Aug 2026 21:50:31 +0530 [thread overview]
Message-ID: <682cde5e-d002-4d20-a613-6cf65784748c@amd.com> (raw)
In-Reply-To: <20260811143643.378589-1-mario.limonciello@amd.com>
Hello Mario,
On 8/11/2026 8:06 PM, Mario Limonciello wrote:
> sched_set_itmt_support() treats debugfs file creation failures as fatal.
> When CONFIG_DEBUG_FS is disabled, debugfs stubs return ERR_PTR(-ENODEV),
> causing ITMT to be silently disabled.
>
> debugfs is a debug-only facility; its return values should be ignored.
> Drop the fatal error handling and enable ITMT unconditionally.
>
> Fixes: d04013a4b21b ("x86/itmt: Move the "sched_itmt_enabled" sysctl to debugfs")
> Reported-by: Klaus Kusche <klaus.kusche@computerix.info>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Feel free to include:
Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>
> ---
> arch/x86/kernel/itmt.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/arch/x86/kernel/itmt.c b/arch/x86/kernel/itmt.c
> index 243a769fdd97b..85ebde361d6ae 100644
> --- a/arch/x86/kernel/itmt.c
> +++ b/arch/x86/kernel/itmt.c
> @@ -110,18 +110,14 @@ int sched_set_itmt_support(void)
> arch_debugfs_dir,
> &sysctl_sched_itmt_enabled,
> &dfs_sched_itmt_fops);
> - if (IS_ERR_OR_NULL(dfs_sched_itmt)) {
> + if (IS_ERR(dfs_sched_itmt))
> dfs_sched_itmt = NULL;
> - return -ENOMEM;
> - }
>
> dfs_sched_core_prio = debugfs_create_file("sched_core_priority", 0644,
> arch_debugfs_dir, NULL,
> &sched_core_priority_fops);
> - if (IS_ERR_OR_NULL(dfs_sched_core_prio)) {
> + if (IS_ERR(dfs_sched_core_prio))
> dfs_sched_core_prio = NULL;
> - return -ENOMEM;
> - }
>
> sched_itmt_capable = true;
>
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2026-08-11 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 14:36 Mario Limonciello
2026-08-11 16:20 ` K Prateek Nayak [this message]
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=682cde5e-d002-4d20-a613-6cf65784748c@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=klaus.kusche@computerix.info \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@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®