From: Marc Zyngier <maz@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
James Morse <james.morse@arm.com>,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM: arm64: Enable Cortex-A510 erratum 2077057 by default
Date: Wed, 02 Mar 2022 15:01:31 +0000 [thread overview]
Message-ID: <87zgm81jqs.wl-maz@kernel.org> (raw)
In-Reply-To: <Yh96ggLwtKAhu7xe@arm.com>
On Wed, 02 Mar 2022 14:09:06 +0000,
Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Fri, Feb 25, 2022 at 06:46:58PM +0000, Mark Brown wrote:
> > The recently added configuration option for Cortex A510 erratum 2077057 does
> > not have a "default y" unlike other errata fixes. This appears to simply be
> > an oversight since the help text suggests enabling the option if unsure and
> > there's nothing in the commit log to suggest it is intentional.
> >
> > Fixes: 1dd498e5e26ad ("KVM: arm64: Workaround Cortex-A510's single-step and PAC trap errata")
> > Signed-off-by: Mark Brown <broonie@kernel.org>
>
> The fixed commit went in through Marc's KVM tree, so this patch can go
> in via the same route. I don't think it's critical for 5.17 (unless
> there are pending fixes from Marc already; I don't have any for arm64).
I don't have anything at the moment, so unless something really urgent
crops up next week, I'll punt that to 5.18.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
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-03-02 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 18:46 [PATCH] KVM: arm64: Enable Cortex-A510 erratum 2077057 by default Mark Brown
2022-03-02 14:09 ` Catalin Marinas
2022-03-02 15:01 ` Marc Zyngier [this message]
2022-03-02 15:05 ` Marc Zyngier
2022-03-08 18:42 ` Catalin Marinas
2022-03-08 18:44 ` Catalin Marinas
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=87zgm81jqs.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--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).