From: Stephen Boyd <swboyd@chromium•org>
To: Andre Przywara <andre.przywara@arm•com>,
Catalin Marinas <catalin.marinas@arm•com>,
Douglas Anderson <dianders@chromium•org>,
Marc Zyngier <maz@kernel•org>,
Mark Rutland <mark.rutland@arm•com>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora•org>,
Will Deacon <will@kernel•org>
Cc: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora•org>,
Jeffrey Hugo <jhugo@codeaurora•org>,
linux-arm-msm@vger•kernel.org, linux-kernel@vger•kernel.org,
Bjorn Andersson <bjorn.andersson@linaro•org>,
Matthias Kaehlcke <mka@chromium•org>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCHv2] arm64: Add KRYO{3, 4}XX CPU cores to spectre-v2 safe list
Date: Thu, 16 Jan 2020 18:26:36 -0800 [thread overview]
Message-ID: <5e211b5d.1c69fb81.dd7e.0ff7@mx.google.com> (raw)
In-Reply-To: <7a8c9a5a39d9d95b9bfca1de3b1f63489d3a4d2d.1579203281.git.saiprakash.ranjan@codeaurora.org>
Quoting Sai Prakash Ranjan (2020-01-16 12:03:53)
> KRYO3XX silver CPU cores and KRYO4XX silver, gold CPU cores
> are not affected by Spectre variant 2. Add them to spectre_v2
> safe list to correct ARM_SMCCC_ARCH_WORKAROUND_1 warning and
> vulnerability sysfs value.
>
> Signed-off-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora•org>
> ---
Reviewed-by: Stephen Boyd <swboyd@chromium•org>
Tested-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
prev parent reply other threads:[~2020-01-17 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 20:03 [PATCHv2] arm64: Add KRYO{3,4}XX CPU cores to spectre-v2 safe list Sai Prakash Ranjan
2020-01-17 2:26 ` Stephen Boyd [this message]
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=5e211b5d.1c69fb81.dd7e.0ff7@mx.google.com \
--to=swboyd@chromium$(echo .)org \
--cc=andre.przywara@arm$(echo .)com \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=dianders@chromium$(echo .)org \
--cc=jhugo@codeaurora$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=maz@kernel$(echo .)org \
--cc=mka@chromium$(echo .)org \
--cc=saiprakash.ranjan@codeaurora$(echo .)org \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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