From: "linyujun (C)" <linyujun809@huawei.com>
To: <corbet@lwn.net>, <bp@suse.de>, <keescook@chromium.org>,
<aarcange@redhat.com>, <daniel.sneddon@linux.intel.com>,
<longman@redhat.com>, <lukas.bulwahn@gmail.com>,
<peterz@infradead.org>, <kim.phillips@amd.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] Documentation/hw-vuln: Update spectre doc
Date: Tue, 13 Sep 2022 17:38:49 +0800 [thread overview]
Message-ID: <7e615e37-ba5f-4e50-17c6-8f742a366808@huawei.com> (raw)
In-Reply-To: <20220830123614.23007-1-linyujun809@huawei.com>
kindly ping
On 2022/8/30 20:36, Lin Yujun writed:
> commit 7c693f54c873691 ("x86/speculation: Add spectre_v2=ibrs
> option to support Kernel IBRS") adds the "ibrs " option in
> Documentation/admin-guide/kernel-parameters.txt but omits it to
> Documentation/admin-guide/hw-vuln/spectre.rst, add it.
>
> Signed-off-by: Lin Yujun <linyujun809@huawei.com>
> ---
> Documentation/admin-guide/hw-vuln/spectre.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/admin-guide/hw-vuln/spectre.rst b/Documentation/admin-guide/hw-vuln/spectre.rst
> index 2ce2a38cdd55..c4dcdb3d0d45 100644
> --- a/Documentation/admin-guide/hw-vuln/spectre.rst
> +++ b/Documentation/admin-guide/hw-vuln/spectre.rst
> @@ -613,6 +613,7 @@ kernel command line.
> eibrs enhanced IBRS
> eibrs,retpoline enhanced IBRS + Retpolines
> eibrs,lfence enhanced IBRS + LFENCE
> + ibrs use IBRS to protect kernel
>
> Not specifying this option is equivalent to
> spectre_v2=auto.
next prev parent reply other threads:[~2022-09-13 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 12:36 Lin Yujun
2022-09-13 9:38 ` linyujun (C) [this message]
2022-09-21 20:09 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2022-08-26 6:51 Lin Yujun
2022-08-26 12:56 ` Bagas Sanjaya
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=7e615e37-ba5f-4e50-17c6-8f742a366808@huawei.com \
--to=linyujun809@huawei.com \
--cc=aarcange@redhat.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=daniel.sneddon@linux.intel.com \
--cc=keescook@chromium.org \
--cc=kim.phillips@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lukas.bulwahn@gmail.com \
--cc=peterz@infradead.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®