From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Guo Heyi <heyi.guo@linaro.org>
Cc: Jeremy Linton <jeremy.linton@arm.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
linaro-uefi <linaro-uefi@lists.linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Graeme Gregory <graeme.gregory@linaro.org>,
huangming <huangming23@huawei.com>,
John Garry <john.garry@huawei.com>,
Jason Zhang <zhangjinsong2@huawei.com>,
wanghuiqiang <wanghuiqiang@huawei.com>,
guoheyi@huawei.com, waip23@126.com,
Mengfanrong <mengfanrong@huawei.com>,
huangdaode@hisilicon.com
Subject: Re: [PATCH edk2-non-osi v3 7/7] Hisilicon/D05: Update binary of trusted-firmware
Date: Fri, 23 Feb 2018 09:02:46 +0000 [thread overview]
Message-ID: <CAKv+Gu-pOueTh8w5T4_Sv0hhsALXzrCBrOHEcdRcLaZ8FfagOg@mail.gmail.com> (raw)
In-Reply-To: <20180223031735.GE95440@SZX1000114654>
On 23 February 2018 at 03:17, Guo Heyi <heyi.guo@linaro.org> wrote:
> Hi Jeremy,
>
> This TF binaries have not been patched the latest SMCCC workaround; it is based
> on v1.4 release and was only
> patched with "disable/enable MMU in PSCI SMC call", as the commit in upstream TF
> code:
> f62ad322695d16178db464dc062fe0af592c6780
>
> When we generated these binaries, SMCCC patches had not come out so they are not
> contained in these binaries.
>
> Do you recommend using the latest smccc patches?
>
Yes.
The Spectre v2 mitigations that landed in v4.16 and were backported to
v4.15 and v4.14 LTS do not use the PSCI_VERSION call anymore to
perform branch predictor invalidation. Instead, it checks for
SMCCCv1.1, and uses the ARCH_WORKAROUND_1 SMC call if supported. If
not, no BP maintenance is performed.
next prev parent reply other threads:[~2018-02-23 8:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 11:57 [PATCH edk2-non-osi v3 0/7] Improve D0x platforms and bug fix Heyi Guo
2018-02-02 11:57 ` [PATCH edk2-non-osi v3 1/7] Hisilicon D03/D05: Delete SasPlatform Heyi Guo
2018-02-02 11:57 ` [PATCH edk2-non-osi v3 2/7] Hisilicon D0x: Fix network interface order issue Heyi Guo
2018-02-02 11:57 ` [PATCH edk2-non-osi v3 3/7] Hisilicon D0x: Delete SnpPlatform Heyi Guo
2018-02-02 11:57 ` [PATCH edk2-non-osi v3 4/7] Hisilicon D03/D05: Update SasDriverDxe binary Heyi Guo
2018-02-02 11:57 ` [PATCH edk2-non-osi v3 5/7] Hisilicon D03/D05: Update NativeOhci binary Heyi Guo
2018-02-02 11:57 ` [PATCH edk2-non-osi v3 6/7] Hisilicon/D03: Update binary of trusted-firmware Heyi Guo
2018-02-02 11:57 ` [PATCH edk2-non-osi v3 7/7] Hisilicon/D05: " Heyi Guo
2018-02-23 2:37 ` Jeremy Linton
2018-02-23 3:17 ` Guo Heyi
2018-02-23 9:02 ` Ard Biesheuvel [this message]
2018-02-24 1:53 ` Guo Heyi
2018-02-07 15:39 ` [PATCH edk2-non-osi v3 0/7] Improve D0x platforms and bug fix Leif Lindholm
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-list 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=CAKv+Gu-pOueTh8w5T4_Sv0hhsALXzrCBrOHEcdRcLaZ8FfagOg@mail.gmail.com \
--to=devel@edk2.groups.io \
/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