linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, Jeffrey Hugo <jhugo@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Clark <robdclark@gmail.com>,
	Leif Lindholm <leif@nuviainc.com>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] efi: stub: override RT_PROP table supported mask based on EFI variable
Date: Sun, 7 Mar 2021 19:02:29 +0800	[thread overview]
Message-ID: <20210307110228.GP17424@dragon> (raw)
In-Reply-To: <20210306113519.294287-1-ardb@kernel.org>

On Sat, Mar 06, 2021 at 12:35:19PM +0100, Ard Biesheuvel wrote:
> Allow EFI systems to override the set of supported runtime services
> declared via the RT_PROP table, by checking for the existence of a
> 'OverrideSupported' EFI variable of the appropriate size under the
> RT_PROP table GUID, and if it does, combine the supported mask using
> logical AND. (This means the override can only remove support, not
> add it back).
> 
> Cc: Jeffrey Hugo <jhugo@codeaurora.org>,
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Cc: Rob Clark <robdclark@gmail.com>
> Cc: Leif Lindholm <leif@nuviainc.com>
> Cc: linux-arm-msm@vger.kernel.org
> 
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>

Awesome, Ard!  On both Lenovo Yoga C630 and Flex 5G latops:

Tested-by: Shawn Guo <shawn.guo@linaro.org>

With 'OverrideSupported' EFI variable added from UEFI Shell, we can drop
'efi=novamap' kernel cmdline and get around the broken poweroff runtime
services nicely.  Thanks!

Shawn

  reply	other threads:[~2021-03-07 11:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 11:35 [PATCH] efi: stub: override RT_PROP table supported mask based on EFI variable Ard Biesheuvel
2021-03-07 11:02 ` Shawn Guo [this message]
2021-03-08 13:34   ` Ard Biesheuvel
2021-03-09  3:22     ` Shawn Guo
2021-03-09  8:51       ` Ard Biesheuvel
2021-03-09 18:13       ` Rob Clark
2021-03-09 18:47         ` Ard Biesheuvel
2021-03-09 21:19           ` Rob Clark
2021-03-15  3:11           ` Shawn Guo
2021-03-15 13:07             ` Ard Biesheuvel
2021-03-16  7:42               ` Heinrich Schuchardt
2021-03-16  7:52                 ` Ard Biesheuvel
2021-03-16  8:04                   ` Ilias Apalodimas
2021-03-16  8:14                     ` Ard Biesheuvel
2021-03-16  8:27                       ` Ilias Apalodimas
2021-03-16  7:52               ` Shawn Guo
2021-03-16  7:57                 ` Ard Biesheuvel
2021-03-16  9:06                   ` Shawn Guo
2021-03-16  9:33                     ` Ard Biesheuvel
2021-03-17  6:36                       ` Shawn Guo
2021-03-17  6:58                         ` Ard Biesheuvel
2021-03-16  9:33                     ` Ilias Apalodimas
2021-03-16 13:25                       ` Heinrich Schuchardt
2021-03-16 14:06                         ` Ard Biesheuvel
2021-03-16 14:45                           ` Heinrich Schuchardt
2021-03-16 14:55                             ` Ard Biesheuvel
2021-03-16 16:06                               ` Heinrich Schuchardt

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=20210307110228.GP17424@dragon \
    --to=shawn.guo@linaro.org \
    --cc=ardb@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=jhugo@codeaurora.org \
    --cc=leif@nuviainc.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=robdclark@gmail.com \
    /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).