public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Guo Heyi <heyi.guo@linaro.org>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Heyi Guo <heyi.guo@linaro.org>,
	leif.lindholm@linaro.org, linaro-uefi@lists.linaro.org,
	edk2-devel@lists.01.org, graeme.gregory@linaro.org,
	huangming23@huawei.com, ard.biesheuvel@linaro.org,
	john.garry@huawei.com, zhangjinsong2@huawei.com,
	wanghuiqiang@huawei.com, guoheyi@huawei.com, waip23@126.com,
	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 11:17:35 +0800	[thread overview]
Message-ID: <20180223031735.GE95440@SZX1000114654> (raw)
In-Reply-To: <a4a07a8a-eb9b-6692-1422-6878e288d4ff@arm.com>

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?

Thanks and regards,

Heyi

On Thu, Feb 22, 2018 at 08:37:11PM -0600, Jeremy Linton wrote:
> Hi,
> 
> On 02/02/2018 05:57 AM, Heyi Guo wrote:
> >1 Workarounds for CVE-2017-5715 on Cortex A57/A72/A73 and A75 #1214.
> 
> I've been trying to verify spectre fixes, and I don't get a smccc version
> from this firmware (see this kernel branch
> https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=kpti)
> image.
> 
> This means that the spectre BP hardening isn't activating on the D05. So,
> unless i'm doing something wrong (quite possible) it appears that this image
> isn't utilizing the correct ATF patches.
> 
> Can someone please verify/check this image with a SMCCC enabled kernel?
> 
> Thanks,
> 
> 
> >2 Upgrade trusted firmware to 1.4
> >
> >Contributed-under: TianoCore Contribution Agreement 1.1
> >Signed-off-by: Ming Huang <huangming23@huawei.com>
> >Signed-off-by: Heyi Guo <heyi.guo@linaro.org>
> >Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> >Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >---
> >  Platform/Hisilicon/D05/bl1.bin | Bin 14344 -> 12424 bytes
> >  Platform/Hisilicon/D05/fip.bin | Bin 41493 -> 37546 bytes
> >  2 files changed, 0 insertions(+), 0 deletions(-)
> >
> >diff --git a/Platform/Hisilicon/D05/bl1.bin b/Platform/Hisilicon/D05/bl1.bin
> >index 7341476..b95257c 100644
> >Binary files a/Platform/Hisilicon/D05/bl1.bin and b/Platform/Hisilicon/D05/bl1.bin differ
> >diff --git a/Platform/Hisilicon/D05/fip.bin b/Platform/Hisilicon/D05/fip.bin
> >index 496a9b8..5958293 100644
> >Binary files a/Platform/Hisilicon/D05/fip.bin and b/Platform/Hisilicon/D05/fip.bin differ
> >
> 


  reply	other threads:[~2018-02-23  3:11 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 [this message]
2018-02-23  9:02       ` Ard Biesheuvel
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=20180223031735.GE95440@SZX1000114654 \
    --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