From: Sohil Mehta <sohil.mehta@intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
Jo Van Bulck <jo.vanbulck@cs.kuleuven.be>,
<linux-kernel@vger.kernel.org>, <dave.hansen@linux.intel.com>,
<luto@kernel.org>, <peterz@infradead.org>, <mingo@redhat.com>
Cc: <x86@kernel.org>, <bp@alien8.de>, <tglx@linutronix.de>, <hpa@zytor.com>
Subject: Re: [PATCH 1/1] x86/pti: Fix kernel warnings for pti= and nopti cmdline options.
Date: Fri, 11 Aug 2023 17:15:37 -0700 [thread overview]
Message-ID: <5b657203-3a02-4b7a-4726-2e5ab2d7f099@intel.com> (raw)
In-Reply-To: <b9bbb279-fa8f-0784-900f-114ce186cbb3@intel.com>
On 8/11/2023 5:08 PM, Dave Hansen wrote:
> It's worth *ZERO* hassle. The docs say:
>
>> mitigations=
> ...
>> off
>> Disable all optional CPU mitigations. This
>> improves system performance, but it may also
>> expose users to several CPU vulnerabilities.
>> Equivalent to:
> ...
>> nopti [X86,PPC]
>
> That's 100% unambiguous.
>
Ah! I missed that. Sorry about the trouble.
next prev parent reply other threads:[~2023-08-12 0:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 21:36 [PATCH v2 0/1] x86/pti: Fix kernel warnings for pti= and nopti cmdline Jo Van Bulck
2023-08-11 21:36 ` [PATCH 1/1] x86/pti: Fix kernel warnings for pti= and nopti cmdline options Jo Van Bulck
2023-08-11 23:27 ` Jo Van Bulck
2023-08-11 23:42 ` Dave Hansen
2023-08-11 23:58 ` Sohil Mehta
2023-08-12 0:08 ` Dave Hansen
2023-08-12 0:15 ` Sohil Mehta [this message]
2023-08-12 15:53 ` Jo Van Bulck
-- strict thread matches above, loose matches on Subject: below --
2023-08-12 15:54 [PATCH v2 0/1] " Jo Van Bulck
2023-08-12 15:54 ` [PATCH 1/1] " Jo Van Bulck
2023-08-14 21:12 ` Sohil Mehta
2023-08-18 22:33 ` Jo Van Bulck
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=5b657203-3a02-4b7a-4726-2e5ab2d7f099@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jo.vanbulck@cs.kuleuven.be \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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