From: Waiman Long <longman@redhat.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Kaplan <David.Kaplan@amd.com>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] cpu/bugs: cgroup: Add a cgroup knob to bypass CPU mitigations
Date: Sat, 21 Sep 2024 03:30:07 -0400 [thread overview]
Message-ID: <031a122c-f480-4dbc-8022-ca829f4ce500@redhat.com> (raw)
In-Reply-To: <20240920075448.djesnjetefwa4yl4@desk>
On 9/20/24 03:54, Pawan Gupta wrote:
>>> static int cpu_local_stat_show(struct seq_file *seq, void *v)
>>> {
>>> struct cgroup __maybe_unused *cgrp = seq_css(seq)->cgroup;
>>> @@ -5290,6 +5326,12 @@ static struct cftype cgroup_base_files[] = {
>>> .name = "cpu.stat.local",
>>> .seq_show = cpu_local_stat_show,
>>> },
>>> + {
>>> + .name = "cpu.skip_mitigation",
>>> + .flags = CFTYPE_NOT_ON_ROOT,
>>> + .seq_show = cpu_skip_mitigation_show,
>>> + .write = cgroup_skip_mitigation_write,
>>> + },
>>> { } /* terminate */
>>> };
>> Since this control knob is effective only for x86_64, should we enable this
>> only for this architecture?
> This should be under a CONFIG option that depends on the architecture
> selected. I don't see a reason why it will not be useful for other archs.
Using a CONFIG option looks fine to me. I just want to make sure that
arches that don't support it won't have a useless control knob show up.
Cheers,
Longman
next prev parent reply other threads:[~2024-09-21 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 21:52 [PATCH RFC 0/2] Selective mitigation for trusted userspace Pawan Gupta
2024-09-19 21:52 ` [PATCH RFC 1/2] x86/entry_64: Add a separate unmitigated entry/exit path Pawan Gupta
2024-09-20 6:57 ` Waiman Long
2024-09-20 7:24 ` Pawan Gupta
2024-09-19 21:52 ` [PATCH RFC 2/2] cpu/bugs: cgroup: Add a cgroup knob to bypass CPU mitigations Pawan Gupta
2024-09-20 7:05 ` Waiman Long
2024-09-20 7:54 ` Pawan Gupta
2024-09-21 7:30 ` Waiman Long [this message]
2024-09-27 15:52 ` [PATCH RFC 0/2] Selective mitigation for trusted userspace Michal Koutný
2024-09-27 22:01 ` Pawan Gupta
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=031a122c-f480-4dbc-8022-ca829f4ce500@redhat.com \
--to=longman@redhat.com \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=cgroups@vger.kernel.org \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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®