From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Stephen Boyd <swboyd@chromium.org>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH v3] KVM: arm64: ARM_SMCCC_ARCH_WORKAROUND_1 doesn't return SMCCC_RET_NOT_REQUIRED
Date: Wed, 28 Oct 2020 15:12:36 +0000 [thread overview]
Message-ID: <160388361710.744976.4736349542337915760.b4-ty@kernel.org> (raw)
In-Reply-To: <20201023154751.1973872-1-swboyd@chromium.org>
On Fri, 23 Oct 2020 08:47:50 -0700, Stephen Boyd wrote:
> According to the SMCCC spec[1](7.5.2 Discovery) the
> ARM_SMCCC_ARCH_WORKAROUND_1 function id only returns 0, 1, and
> SMCCC_RET_NOT_SUPPORTED.
>
> 0 is "workaround required and safe to call this function"
> 1 is "workaround not required but safe to call this function"
> SMCCC_RET_NOT_SUPPORTED is "might be vulnerable or might not be, who knows, I give up!"
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] KVM: arm64: ARM_SMCCC_ARCH_WORKAROUND_1 doesn't return SMCCC_RET_NOT_REQUIRED
https://git.kernel.org/arm64/c/1de111b51b82
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2020-10-28 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 15:47 [PATCH v3] KVM: arm64: ARM_SMCCC_ARCH_WORKAROUND_1 doesn't return SMCCC_RET_NOT_REQUIRED Stephen Boyd
2020-10-26 13:25 ` Will Deacon
2020-10-27 21:41 ` Stephen Boyd
2020-10-28 10:03 ` Marc Zyngier
2020-10-28 15:12 ` Will Deacon [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=160388361710.744976.4736349542337915760.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=stable@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=swboyd@chromium.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).