From: Alex Thorlton <athorlton@sgi.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Alex Thorlton <athorlton@sgi.com>, Dave Young <dyoung@redhat.com>,
"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>
Subject: Re: [PATCH] export efi.flags to sysfs
Date: Wed, 28 May 2014 15:11:25 -0500 [thread overview]
Message-ID: <20140528201125.GZ10771@sgi.com> (raw)
In-Reply-To: <20140528190400.GR14863@redhat.com>
On Wed, May 28, 2014 at 03:04:00PM -0400, Vivek Goyal wrote:
> On Wed, May 28, 2014 at 10:51:04AM -0500, Alex Thorlton wrote:
>
> [..]
> > 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.
>
> Agreed. Let kernel and firmware figure it out when to apply quirk and
> user space should not worry about firmware version.
>
> I liked the other approach better where user space just needs to know
> if 1:1 mapping are in effect or not and take decision based on that.
>
> So once SGI firmware gets fixed for 1:1 mapping, and kernel knows it,
> then user space will not have to be changed at all.
Sounds good to me. Working on a potential kernel fix as we speak.
- Alex
next prev parent reply other threads:[~2014-05-28 20:11 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
[not found] ` <20140526083935.GA19682-je1gSBvt1Tc/CGXRbJeUwh/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2014-05-27 3:00 ` Dave Young
[not found] ` <20140527030058.GB2372-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2014-05-27 13:36 ` Fleming, Matt
[not found] ` <CAL01qpvqa-8u2MZ=8wE8gsiprFLbN4U3AbEX9+h7FuemXNR93Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-28 2:09 ` Dave Young
2014-05-28 9:47 ` Dave Young
2014-05-28 15:51 ` Alex Thorlton
[not found] ` <20140528155104.GW10771-sJ/iWh9BUns@public.gmane.org>
2014-05-28 19:04 ` Vivek Goyal
2014-05-28 20:11 ` Alex Thorlton [this message]
[not found] ` <20140528190400.GR14863-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-29 11:58 ` Fleming, Matt
2014-05-29 2:37 ` Dave Young
[not found] ` <20140528020935.GB2820-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2014-05-28 14:51 ` Vivek Goyal
[not found] ` <20140528145140.GN14863-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-29 11:53 ` Fleming, Matt
[not found] ` <CAL01qpsb5_Gh31uqm7yB6HP2rKQkhFWWTu+U4JAR54XR5bfbZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-29 12:59 ` Vivek Goyal
[not found] ` <20140529125910.GE14570-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-29 13:10 ` Fleming, Matt
[not found] ` <CAL01qpuNS0u89gaR9pCKUoCVRkADhPO4mZueEyK8nP84=OfDaA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-30 1:53 ` Dave Young
2014-05-27 13:34 ` Vivek Goyal
[not found] ` <20140527133411.GG10994-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-28 2:13 ` Dave Young
[not found] ` <20140528021359.GC2820-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2014-05-28 12:40 ` Vivek Goyal
[not found] ` <20140528124029.GF14863-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-29 2:08 ` Dave Young
2014-05-29 9:09 ` Dave Young
[not found] ` <20140529020837.GB2068-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2014-05-29 12:45 ` Vivek Goyal
[not found] ` <20140529124520.GC14570-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-29 12:50 ` Borislav Petkov
2014-05-30 2:24 ` Dave Young
[not found] ` <20140530022438.GC1985-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
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=20140528201125.GZ10771@sgi.com \
--to=athorlton@sgi.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--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).