All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
	kernel-team@android.com,
	Catalin Marinas <catalin.marinas@arm.com>,
	Doug Anderson <dianders@google.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Allow CPUs unffected by ARM erratum 1418040 to come in late
Date: Fri, 11 Sep 2020 11:59:03 -0700	[thread overview]
Message-ID: <20200911185903.GA942772@google.com> (raw)
In-Reply-To: <20200911181611.2073183-1-maz@kernel.org>

On Fri, Sep 11, 2020 at 07:16:11PM +0100, Marc Zyngier wrote:
> Now that we allow CPUs affected by erratum 1418040 to come in late,
> this prevents their unaffected sibblings from coming in late (or
> coming back after a suspend or hotplug-off, which amounts to the
> same thing).
> 
> To allow this, we need to add ARM64_CPUCAP_OPTIONAL_FOR_LATE_CPU,
> which amounts to set .type to ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE.
> 
> Reported-by: Doug Anderson <dianders@google.com>
> Tested-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
> Fixes: bf87bb0881d0 ("arm64: Allow booting of late CPUs affected by erratum 1418040")
> Signed-off-by: Marc Zyngier <maz@kernel.org>

Tested-by: Matthias Kaehlcke <mka@chromium.org>

And I guess I deserve brownie points for having found the problem
initially and identified the offending commit, even though it was
Doug who reported it to the list :)

Reported-by: Matthias Kaehlcke <mka@chromium.org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-09-11 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 18:16 [PATCH] arm64: Allow CPUs unffected by ARM erratum 1418040 to come in late Marc Zyngier
2020-09-11 18:31 ` Will Deacon
2020-09-11 18:59 ` Matthias Kaehlcke [this message]
2020-09-11 19:51   ` Doug Anderson

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=20200911185903.GA942772@google.com \
    --to=mka@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=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.