linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jeremy.linton@arm.com (Jeremy Linton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] UEFI stub pre-boot compat checks
Date: Mon, 1 Feb 2016 09:47:00 -0600	[thread overview]
Message-ID: <56AF7DF4.3050504@arm.com> (raw)
In-Reply-To: <1454000549-9189-1-git-send-email-ard.biesheuvel@linaro.org>

On 01/28/2016 11:02 AM, 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.

Ard,

This version looks good, and addresses all the reservations from the 16k 
page thread. Thanks!

Reviewed-by: Jeremy Linton <jeremy.linton@arm.com>

      parent reply	other threads:[~2016-02-01 15:47 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 ` [PATCH 0/3] UEFI stub pre-boot compat checks Suzuki K. Poulose
2016-02-01 15:47 ` Jeremy Linton [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=56AF7DF4.3050504@arm.com \
    --to=jeremy.linton@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).