From: Stephen Boyd <swboyd@chromium.org>
To: Marc Zyngier <maz@kernel.org>, linux-arm-kernel@lists.infradead.org
Cc: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
dianders@google.com, kernel-team@android.com
Subject: Re: [PATCH v3 1/2] arm64: Move handling of erratum 1418040 into C code
Date: Fri, 31 Jul 2020 11:00:57 -0700 [thread overview]
Message-ID: <159621845789.1360974.10290066284448705136@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200731173824.107480-2-maz@kernel.org>
Quoting Marc Zyngier (2020-07-31 10:38:23)
> Instead of dealing with erratum 1418040 on each entry and exit,
> let's move the handling to __switch_to() instead, which has
> several advantages:
>
> - It can be applied when it matters (switching between 32 and 64
> bit tasks).
> - It is written in C (yay!)
> - It can rely on static keys rather than alternatives
>
> Tested-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
> Acked-by: Will Deacon <will@kernel.org>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
_______________________________________________
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:[~2020-07-31 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 17:38 [PATCH v3 0/2] arm64: Allow erratum 1418040 for late CPUs Marc Zyngier
2020-07-31 17:38 ` [PATCH v3 1/2] arm64: Move handling of erratum 1418040 into C code Marc Zyngier
2020-07-31 18:00 ` Stephen Boyd [this message]
2020-07-31 17:38 ` [PATCH v3 2/2] arm64: Allow booting of late CPUs affected by erratum 1418040 Marc Zyngier
[not found] ` <159803353178.13439.17036526669146072985.b4-ty@arm.com>
2020-09-09 14:53 ` [PATCH v3 0/2] arm64: Allow erratum 1418040 for late CPUs Doug Anderson
2020-09-10 13:43 ` Sai Prakash Ranjan
[not found] ` <3d5f6d5289304c558830d5fb8820e6cb@codeaurora.org>
2020-09-11 13:30 ` Marc Zyngier
2020-09-11 16:34 ` Sai Prakash Ranjan
[not found] ` <51c30228d9fe3dd6e2a55991831e95b0@codeaurora.org>
2020-09-11 16:42 ` Will Deacon
2020-09-11 17:47 ` Marc Zyngier
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=159621845789.1360974.10290066284448705136@swboyd.mtv.corp.google.com \
--to=swboyd@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=dianders@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=suzuki.poulose@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.