From: Catalin Marinas <catalin.marinas@arm.com>
To: Liu Song <liusong@linux.alibaba.com>
Cc: will@kernel.org, james.morse@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: spectre: increase parameters that can be used to turn off bhb mitigation individually
Date: Wed, 7 Sep 2022 15:29:05 +0100 [thread overview]
Message-ID: <YxiqsXjQQGe0dNuA@arm.com> (raw)
In-Reply-To: <1661514050-22263-1-git-send-email-liusong@linux.alibaba.com>
On Fri, Aug 26, 2022 at 07:40:50PM +0800, Liu Song wrote:
> From: Liu Song <liusong@linux.alibaba.com>
>
> In our environment, it was found that the mitigation BHB has a great
> impact on the benchmark performance. For example, in the lmbench test,
> the "process fork && exit" test performance drops by 20%.
> So it is necessary to have the ability to turn off the mitigation
> individually through cmdline, thus avoiding having to compile the
> kernel by adjusting the config.
>
> Signed-off-by: Liu Song <liusong@linux.alibaba.com>
If people want to disable this mitigation and know what they are doing,
I have no objection:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
(I guess that's more like 6.1 material)
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-07 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 11:40 [PATCH v2] arm64: spectre: increase parameters that can be used to turn off bhb mitigation individually Liu Song
2022-09-07 14:29 ` Catalin Marinas [this message]
2022-09-07 16:29 ` Will Deacon
2022-09-09 18:08 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2022-08-26 11:08 [PATCH] " Liu Song
2022-08-26 12:44 ` [PATCH v2] " Liu Song
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=YxiqsXjQQGe0dNuA@arm.com \
--to=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liusong@linux.alibaba.com \
--cc=will@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).