From: matt@console-pimps.org (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] efi/x86: move UEFI Runtime Services wrappers to generic code
Date: Tue, 1 Jul 2014 14:30:33 +0100 [thread overview]
Message-ID: <20140701133033.GD7539@console-pimps.org> (raw)
In-Reply-To: <1403777346-28629-2-git-send-email-ard.biesheuvel@linaro.org>
On Thu, 26 Jun, at 12:09:05PM, Ard Biesheuvel wrote:
> In order for other archs (such as arm64) to be able to reuse the virtual mode
> function call wrappers, move them to drivers/firmware/efi/runtime-wrappers.c.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
[...]
> @@ -54,6 +54,13 @@ config EFI_PARAMS_FROM_FDT
> the EFI runtime support gets system table address, memory
> map address, and other parameters from the device tree.
>
> +config EFI_RUNTIME_WRAPPERS
> + bool
> + help
> + Selected by the arch if it needs to wrap UEFI Runtime Services calls,
> + in which case it needs to provide #definitions of efi_call_virt and
> + __efi_call_virt in <asm/efi.h>
> +
> endmenu
Actually, could we drop this help text?
That may seem like a backwards step, but I have concerns that we'll fail
to keep this help text in sync with the code. Furthermore, by providing
help text that kinda says, "casual users need the help text to
understand when to enable this feature". Clearly that's not what this
Kconfig symbol is for.
Most of the other guard Kconfig symbols don't provide this kind of text,
and I think there's good reason to follow suit.
What do you think?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-07-01 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 10:09 [PATCH v2 0/2] efi: preserve NEON registers on UEFI services calls Ard Biesheuvel
2014-06-26 10:09 ` [PATCH v2 1/2] efi/x86: move UEFI Runtime Services wrappers to generic code Ard Biesheuvel
2014-07-01 13:30 ` Matt Fleming [this message]
2014-07-01 13:35 ` Ard Biesheuvel
2014-07-01 13:48 ` Matt Fleming
2014-06-26 10:09 ` [PATCH v2 2/2] efi/arm64: preserve FP/SIMD registers on UEFI runtime services calls Ard Biesheuvel
2014-07-04 15:45 ` Catalin Marinas
2014-07-04 15:51 ` Ard Biesheuvel
2014-07-04 16:59 ` Catalin Marinas
2014-07-04 17:15 ` Ard Biesheuvel
2014-06-26 13:58 ` [PATCH v2 0/2] efi: preserve NEON registers on UEFI " Mark Salter
2014-06-26 14:22 ` Ard Biesheuvel
2014-07-01 13:26 ` Matt Fleming
2014-07-01 13:46 ` Ard Biesheuvel
2014-07-08 15:33 ` Olivier Martin
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=20140701133033.GD7539@console-pimps.org \
--to=matt@console-pimps.org \
--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).