From: Jonathan Corbet <corbet@lwn.net>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH 6/7] docs: remove nompx kernel parameter and intel_mpx from index.rst
Date: Tue, 25 Feb 2020 03:06:42 -0700 [thread overview]
Message-ID: <20200225030642.0c0e84a8@lwn.net> (raw)
In-Reply-To: <a4d6c6c7-7901-7584-fc90-a8f933b2e238@intel.com>
On Mon, 24 Feb 2020 09:30:09 -0800
Dave Hansen <dave.hansen@intel.com> wrote:
> On 2/22/20 1:00 AM, Mauro Carvalho Chehab wrote:
> > - nompx [X86] Disables Intel Memory Protection Extensions.
> > - See Documentation/x86/intel_mpx.rst for more
> > - information about the feature.
>
> Thanks for finding this.
>
> But, it does make me wonder if we should remove it outright or leave a
> stub reminding folks that "nompx" probably shouldn't be reused for a
> while. Maybe something like:
>
> nompx [X86] Previously, disabled Intel Memory Protection
> Extensions. Code removed in v5.6.
>
Is the concern that people might still be booting kernels with that
option, even though it's gone? If that's the case, probably what should
really happen is a check within the code to issue a warning telling those
users that MPX is an ex-parrot. That would also have the effect of
deterring reuse... ?
Thanks,
jon
next prev parent reply other threads:[~2020-02-25 10:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 9:00 [PATCH 0/7] Some cross-reference fixes due to fixes renames Mauro Carvalho Chehab
2020-02-22 9:00 ` [PATCH 1/7] scripts: documentation-file-ref-check: improve :doc: handling Mauro Carvalho Chehab
2020-02-22 9:00 ` [PATCH 2/7] docs: dt: fix several broken references due to renames Mauro Carvalho Chehab
2020-02-24 0:07 ` Andrew Jeffery
2020-02-24 13:02 ` Dan Murphy
2020-02-24 14:55 ` Amit Kucheria
2020-02-24 18:14 ` Rob Herring
2020-02-27 9:16 ` Daniel Lezcano
2020-02-22 9:00 ` [PATCH 3/7] docs: fix broken references to text files Mauro Carvalho Chehab
2020-02-22 17:51 ` Daniel Vetter
2020-02-24 9:26 ` Federico Vaga
2020-03-25 2:42 ` Stephen Boyd
2020-02-22 9:00 ` [PATCH 4/7] docs: adm1177: fix a broken reference Mauro Carvalho Chehab
2020-02-22 15:48 ` Guenter Roeck
2020-02-22 9:00 ` [PATCH 5/7] docs: fix broken references for ReST files that moved around Mauro Carvalho Chehab
2020-02-23 8:12 ` Paolo Bonzini
2020-02-22 9:00 ` [PATCH 6/7] docs: remove nompx kernel parameter and intel_mpx from index.rst Mauro Carvalho Chehab
2020-02-24 17:30 ` Dave Hansen
2020-02-25 10:06 ` Jonathan Corbet [this message]
2020-02-22 9:00 ` [PATCH 7/7] docs: gpu: i915.rst: fix warnings due to file renames Mauro Carvalho Chehab
2020-02-25 23:36 ` Rodrigo Vivi
2020-02-25 10:05 ` [PATCH 0/7] Some cross-reference fixes due to fixes renames Jonathan Corbet
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=20200225030642.0c0e84a8@lwn.net \
--to=corbet@lwn.net \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).