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 16:58:23 -0700 [thread overview]
Message-ID: <3a4bf401-0781-492f-a952-3c96c1507551@intel.com> (raw)
In-Reply-To: <d76126be-9eda-d426-1fa5-a35fd4ca3d57@intel.com>
On 8/11/2023 4:42 PM, Dave Hansen wrote:
> On 8/11/23 16:27, Jo Van Bulck wrote:
>> Not sure which option would best match kernel coding guidelines?
>
> This sound like it's getting a bit out of hand and reaching far beyond
> cleaning up some (mostly) harmless warnings.
>
I agree this doesn't have to be this complex. PTI_FORCE_AUTO is unnecessary.
> pti=auto does *not* need to override mitigations=off.
I think only pti=on needs to override mitigations=off i.e. the User is
saying turn off mitigations but keep PTI enabled. This should be fairly
easy to achieve with the current enum. If it is not then it's not worth
the hassle.
next prev parent reply other threads:[~2023-08-11 23:58 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 [this message]
2023-08-12 0:08 ` Dave Hansen
2023-08-12 0:15 ` Sohil Mehta
2023-08-12 15:53 ` Jo Van Bulck
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=3a4bf401-0781-492f-a952-3c96c1507551@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
all inboxes | Powered by JetHome®