From: Dave Young <dyoung@redhat.com>
To: Alex Thorlton <athorlton@sgi.com>
Cc: "Fleming, Matt" <matt.fleming@intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
vgoyal@redhat.com
Subject: Re: [PATCH] export efi.flags to sysfs
Date: Thu, 29 May 2014 10:37:59 +0800 [thread overview]
Message-ID: <20140529023759.GF2068@darkstar.nay.redhat.com> (raw)
In-Reply-To: <20140528155104.GW10771@sgi.com>
> > Question to Alex, if userspace can get the firmware version there might
> > be another option that kexec-tools checking the firmware version and
> > switch to old noefi way automaticlly. Is it doable?
>
> Userspace can get the firmware version easily, as long as our hwperf
> module is installed (as it should be on any supported SGI machine). The
> firmware version can be found in /proc/sgi_uv/bios_version on any
> machine where hwperf is loaded.
>
> I don't know if that's really an ideal method for what you're doing, but
> that's the only way I know of to get the firmware version in userspace.
>
> A side note, though: We're going to have to figure out some way to
> determine whether or not to apply the old_map quirk on during boot
> anyway, so if it's easiest for you to just determine how the original
> kernel was booted and key off of that, then I wouldn't worry about
> finding a different method to get the firmware version in userspace,
> unless there are other reasons for you to do it that way.
I'm dropping the idea to check firmware version in user space, your kernel
fix to automaticlly select mapping method based on firmware version is still
needed.
I'm tending to use the idea from Vivek in kexec-tools to check the virt addr
in /sys/firmware/efi/runtime-map/*/virt_addr
Thanks
Dave
next prev parent reply other threads:[~2014-05-29 2:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 8:39 [PATCH] export efi.flags to sysfs Dave Young
2014-05-27 3:00 ` Dave Young
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 [this message]
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=20140529023759.GF2068@darkstar.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=athorlton@sgi.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;
as well as URLs for NNTP newsgroup(s).