From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] ARM: Silence proc-v7-bugs.c spam about disabled Spectre workarounds
Date: Tue, 28 Jun 2022 10:23:06 +0300 [thread overview]
Message-ID: <253e9ec1-bcd8-c790-95b8-afbcc21e7163@collabora.com> (raw)
In-Reply-To: <20220519161310.1489625-1-dmitry.osipenko@collabora.com>
On 5/19/22 19:13, Dmitry Osipenko wrote:
> Print message about disabled Spectre workarounds only once to stop
> endless spam into KSMG each time CPU goes out from idling state.
> This spam makes system unusable with CONFIG_HARDEN_BRANCH_PREDICTOR=n
> for those who don't care about security and wants maximum performance.
>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> ---
> arch/arm/mm/proc-v7-bugs.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/arm/mm/proc-v7-bugs.c b/arch/arm/mm/proc-v7-bugs.c
> index fb9f3eb6bf48..f9730eba0632 100644
> --- a/arch/arm/mm/proc-v7-bugs.c
> +++ b/arch/arm/mm/proc-v7-bugs.c
> @@ -108,8 +108,7 @@ static unsigned int spectre_v2_install_workaround(unsigned int method)
> #else
> static unsigned int spectre_v2_install_workaround(unsigned int method)
> {
> - pr_info("CPU%u: Spectre V2: workarounds disabled by configuration\n",
> - smp_processor_id());
> + pr_info_once("Spectre V2: workarounds disabled by configuration\n");
>
> return SPECTRE_VULNERABLE;
> }
Hello Russell,
Could you please apply this patch? I tried to use yours patch tracker
today and it doesn't allow me to recover my password (server error: MAIL
FROM command failed Detail: Space shortage).
Thanks!
--
Best regards,
Dmitry
next prev parent reply other threads:[~2022-06-28 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 16:13 Dmitry Osipenko
2022-06-28 7:23 ` Dmitry Osipenko [this message]
2022-06-28 7:31 ` Russell King (Oracle)
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=253e9ec1-bcd8-c790-95b8-afbcc21e7163@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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®