From: Marc Zyngier <maz@kernel.org>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-msm@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Andre Przywara <andre.przywara@arm.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Add KRYO4XX gold CPU core to spectre-v2 safe list
Date: Fri, 14 Aug 2020 09:17:08 +0100 [thread overview]
Message-ID: <961724681d6d3f8c37a4e3c8facbdea3@kernel.org> (raw)
In-Reply-To: <d4ad5ade9815632f450374c9b6bbe9d2@codeaurora.org>
On 2020-08-14 05:34, Sai Prakash Ranjan wrote:
> On 2020-08-13 23:29, Marc Zyngier wrote:
[...]
>> We'd need to disable the late onlining of CPUs that would change
>> the mitigation state, and this is... ugly.
>>
>
> Ugh, yes indeed and here I was thinking that these things are
> straightforward :(
It never is. Big-little is a broken concept. I'll try and think of
something next week, as I'm pretty swamped at the moment.
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
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-08-14 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 8:18 [PATCH] arm64: Add KRYO4XX gold CPU core to spectre-v2 safe list Sai Prakash Ranjan
2020-08-13 9:03 ` Will Deacon
2020-08-13 9:19 ` Sai Prakash Ranjan
2020-08-13 9:40 ` Will Deacon
2020-08-13 10:39 ` Marc Zyngier
2020-08-13 12:33 ` Sai Prakash Ranjan
2020-08-13 17:59 ` Marc Zyngier
2020-08-14 4:34 ` Sai Prakash Ranjan
2020-08-14 8:17 ` Marc Zyngier [this message]
2020-08-14 8:32 ` Sai Prakash Ranjan
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=961724681d6d3f8c37a4e3c8facbdea3@kernel.org \
--to=maz@kernel.org \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=suzuki.poulose@arm.com \
--cc=swboyd@chromium.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).