From: Borislav Petkov <bp@alien8.de>
To: Lai Jiangshan <jiangshanlai+lkml@gmail.com>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/6] x86/cpu: Remove "noclflush"
Date: Mon, 15 Nov 2021 10:12:38 +0100 [thread overview]
Message-ID: <YZIkhnqSq9SgL7k6@zn.tnic> (raw)
In-Reply-To: <CAJhGHyCm2O6uj29cAQNfaHX3Wq2NyO+s4=nQAS+3PadDqhiZtw@mail.gmail.com>
On Mon, Nov 15, 2021 at 05:03:29PM +0800, Lai Jiangshan wrote:
> The patch is definitely good for me, but I have no idea what
> "BUGS=" relates to here.
> (In the commit 191679fdfa63 ("x86: add noclflush option"))
>
> In Documentation/admin-guide/kernel-parameters.rst:
> BUGS= Relates to possible processor bugs on the said processor.
Probably some CLFLUSH-related erratum from more than 10 years ago.
Probably not relevant anymore - otherwise we would have heard about it.
> For patch 3,4,5, they can have my reviewed-by:
>
> Reviewed-by: Lai Jiangshan <jiangshanlai@gmail.com>
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-11-15 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 10:32 [PATCH 0/6] x86/cpu: Do some janitorial work Borislav Petkov
2021-11-12 10:32 ` [PATCH 1/6] x86/cpu: Allow feature bit names from /proc/cpuinfo in clearcpuid= Borislav Petkov
2022-01-25 11:45 ` [PATCH v1.1] " Borislav Petkov
2021-11-12 10:32 ` [PATCH 2/6] x86/cpu: Remove "nosep" Borislav Petkov
2021-11-12 10:32 ` [PATCH 3/6] x86/cpu: Remove CONFIG_X86_SMAP and "nosmap" Borislav Petkov
2021-11-12 10:32 ` [PATCH 4/6] x86/cpu: Remove "nosmep" Borislav Petkov
2021-11-12 10:32 ` [PATCH 5/6] x86/cpu: Remove "noexec" Borislav Petkov
2021-11-12 10:32 ` [PATCH 6/6] x86/cpu: Remove "noclflush" Borislav Petkov
2021-11-15 9:03 ` Lai Jiangshan
2021-11-15 9:12 ` Borislav Petkov [this message]
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=YZIkhnqSq9SgL7k6@zn.tnic \
--to=bp@alien8.de \
--cc=jiangshanlai+lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®