From: Suzuki.Poulose@arm•com (Suzuki K. Poulose)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] UEFI stub pre-boot compat checks
Date: Fri, 29 Jan 2016 17:30:46 +0000 [thread overview]
Message-ID: <56ABA1C6.5090307@arm.com> (raw)
In-Reply-To: <1454000549-9189-1-git-send-email-ard.biesheuvel@linaro.org>
On 28/01/16 17:02, Ard Biesheuvel wrote:
> As discussed earlier today [1], and last year [2], it makes sense for the
> UEFI stub to perform some basic checks on the hardware for missing features
> that would prevent the kernel from booting to a state where it can even
> complain about this.
>
> So implements this for ARM, to check on LPAE builds whether the CPU supports
> it (patch #1), and for arm64, to check whether the build time granule is
> implemented by the CPU (patch #2). Patch #3 wires it up into the shared init
> code.
>
> [1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/472880
> [2] http://thread.gmane.org/gmane.linux.ports.arm.kernel/447370
Ard,
Thanks for the quick solution. I tested this on Juno for 16K granule.
So, for arm64:
Tested-by: Suzuki K Poulose <suzuki.poulose@arm•com>
Cheers
Suzuki
next prev parent reply other threads:[~2016-01-29 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 17:02 [PATCH 0/3] UEFI stub pre-boot compat checks Ard Biesheuvel
2016-01-28 17:02 ` [PATCH 1/3] ARM: efistub: check for LPAE support before booting a LPAE kernel Ard Biesheuvel
2016-01-28 17:02 ` [PATCH 2/3] arm64: efistub: check for h/w support before booting a >4 KB granule kernel Ard Biesheuvel
2016-01-28 17:02 ` [PATCH 3/3] ARM/arm64: efistub: perform hardware compatibility check Ard Biesheuvel
2016-01-29 17:30 ` Suzuki K. Poulose [this message]
2016-02-01 15:47 ` [PATCH 0/3] UEFI stub pre-boot compat checks Jeremy Linton
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=56ABA1C6.5090307@arm.com \
--to=suzuki.poulose@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.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