From: Dave Young <dyoung@redhat.com>
To: "Fleming, Matt" <matt.fleming@intel.com>
Cc: Vivek Goyal <vgoyal@redhat.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>
Subject: Re: [PATCH] export efi.flags to sysfs
Date: Fri, 30 May 2014 09:53:15 +0800 [thread overview]
Message-ID: <20140530015315.GA1985@darkstar.nay.redhat.com> (raw)
In-Reply-To: <CAL01qpuNS0u89gaR9pCKUoCVRkADhPO4mZueEyK8nP84=OfDaA@mail.gmail.com>
On 05/29/14 at 02:10pm, Fleming, Matt wrote:
> On 29 May 2014 13:59, Vivek Goyal <vgoyal@redhat.com> wrote:
> >
> > Only second kernel boots with "noefi" and this parameter is appened by
> > kexec-tools to second kernel command line. So first kernel will still
> > boot *without noefi* and kexec-tools wil think that this system support
> > booting second kernel with UEFI enabled.
> >
> > I don't know if we export /sys/firmware/efi/runtime-map/ in case of
> > non 1:1 mapping or not. Dave and Boris will know better.
>
> Looking at the code the answer is: yes. I think that's the bug right there.
>
> By exporting entries in /sys/firmware/efi/runtime-map we're saying
> "These mappings persist across kexec, you can trust that they won't
> change", for SGI UV (which currently uses the quirk) or if you boot
> with efi=old_map on the command line, that's simply not true.
>
> So, it would seem to me that we're missing a "if
> (efi_enabled(OLD_MAP))" in drivers/firmware/efi/runtime-map.c.
> Borislav, Dave? What do you guys think?
Yes, I missed the old_map case when I did the patchset.
Only exporting runtime map in case 1:1 map looks good. Thus kexec-tools can
easily just check the existance of the sysfs files.
Will send out a patch soon.
Thanks
Dave
next prev parent reply other threads:[~2014-05-30 1:52 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
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 [this message]
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=20140530015315.GA1985@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;
as well as URLs for NNTP newsgroup(s).