From: Dave Young <dyoung@redhat.com>
To: matt.fleming@intel.com, bp@alien8.de,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
vgoyal@redhat.com
Subject: Re: [PATCH] export efi.flags to sysfs
Date: Tue, 27 May 2014 11:00:58 +0800 [thread overview]
Message-ID: <20140527030058.GB2372@darkstar.nay.redhat.com> (raw)
In-Reply-To: <20140526083935.GA19682@dhcp-16-198.nay.redhat.com>
On 05/26/14 at 04:39pm, Dave Young wrote:
>
> For efi=old_map and any old_map quirks like SGI UV in current
> tree kexec/kdump will fail because it depends on the new 1:1 mapping.
>
> Thus export the mapping method to sysfs so kexec tools can switch
> to original way to boot.
>
> Since we have efi.flags for all efi facilities so let's just export the
> efi.flags itself, it maybe useful for other arches and use cases.
Rethink about this issue, export flags will expose the efi facility
macros to userspace, Matt, what's your opinion? It might be better to export
a file 'old_map' only which is '0|1'
>
> Signed-off-by: Dave Young <dyoung@redhat.com>
> ---
> drivers/firmware/efi/efi.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> Index: linux-2.6/drivers/firmware/efi/efi.c
> ===================================================================
> --- linux-2.6.orig/drivers/firmware/efi/efi.c
> +++ linux-2.6/drivers/firmware/efi/efi.c
> @@ -86,16 +86,19 @@ static ssize_t name##_show(struct kobjec
> EFI_ATTR_SHOW(fw_vendor);
> EFI_ATTR_SHOW(runtime);
> EFI_ATTR_SHOW(config_table);
> +EFI_ATTR_SHOW(flags);
>
> static struct kobj_attribute efi_attr_fw_vendor = __ATTR_RO(fw_vendor);
> static struct kobj_attribute efi_attr_runtime = __ATTR_RO(runtime);
> static struct kobj_attribute efi_attr_config_table = __ATTR_RO(config_table);
> +static struct kobj_attribute efi_attr_flags = __ATTR_RO(flags);
>
> static struct attribute *efi_subsys_attrs[] = {
> &efi_attr_systab.attr,
> &efi_attr_fw_vendor.attr,
> &efi_attr_runtime.attr,
> &efi_attr_config_table.attr,
> + &efi_attr_flags.attr,
> NULL,
> };
>
next prev parent reply other threads:[~2014-05-27 2:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 8:39 Dave Young
2014-05-27 3:00 ` Dave Young [this message]
2014-05-27 13:36 ` Fleming, Matt
2014-05-28 2:09 ` Dave Young
2014-05-28 9:47 ` Dave Young
2014-05-28 15:51 ` Alex Thorlton
2014-05-28 19:04 ` Vivek Goyal
2014-05-28 20:11 ` Alex Thorlton
2014-05-29 11:58 ` Fleming, Matt
2014-05-29 2:37 ` Dave Young
2014-05-28 14:51 ` Vivek Goyal
2014-05-29 11:53 ` Fleming, Matt
2014-05-29 12:59 ` Vivek Goyal
2014-05-29 13:10 ` Fleming, Matt
2014-05-30 1:53 ` Dave Young
2014-05-27 13:34 ` Vivek Goyal
2014-05-28 2:13 ` Dave Young
2014-05-28 12:40 ` Vivek Goyal
2014-05-29 2:08 ` Dave Young
2014-05-29 9:09 ` Dave Young
2014-05-29 12:45 ` Vivek Goyal
2014-05-29 12:50 ` Borislav Petkov
2014-05-30 2:24 ` Dave Young
2014-05-30 7:33 ` Borislav Petkov
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=20140527030058.GB2372@darkstar.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=bp@alien8.de \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=vgoyal@redhat.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
all inboxes | Powered by JetHome®