From: "H. Peter Anvin" <hpa@zytor.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: "Bryan O'Donoghue" <bryan.odonoghue.lkml@nexus-software.ie>,
Matt Fleming <matt@console-pimps.org>,
matthew.garrett@nebula.com, linux-efi@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
Darren Hart <darren.hart@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Boyer <jwboyer@redhat.com>
Subject: Re: [PATCH] Remove warning in efi_enter_virtual_mode
Date: Thu, 18 Apr 2013 16:44:49 -0700 [thread overview]
Message-ID: <51708571.8080805@zytor.com> (raw)
In-Reply-To: <20130418230120.GA7078@jtriplet-mobl1>
On 04/18/2013 04:01 PM, Josh Triplett wrote:
>
> I'd much rather see the code do the right thing automatically, rather
> than requiring an "unbreak me" command-line parameter.
>
> But in any case, since BGRT is a "make my system look prettier" feature
> rather than core functionality, giving up on it on 32-bit EFI seems
> fairly reasonable, especially since it may still work if stored
> sufficiently low in memory.
>
No, it really isn't. Quite frankly, I don't understand why HIGHMEM
makes it any harder... in a lot of ways HIGHMEM memory is easier to deal
with because it is touched much later in the process. Sure, it has to
be mapped before you can copy it out, but that usually isn't a big deal.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2013-04-18 23:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 15:58 [PATCH] Remove warning in efi_enter_virtual_mode Bryan O'Donoghue
2013-04-17 14:06 ` Matt Fleming
2013-04-17 22:00 ` Bryan O'Donoghue
2013-04-18 11:00 ` Matt Fleming
2013-04-18 13:40 ` Josh Boyer
2013-04-18 15:01 ` Matthew Garrett
2013-04-18 15:17 ` Josh Boyer
2013-04-18 14:51 ` Darren Hart
2013-04-18 16:19 ` Matt Fleming
2013-04-19 0:18 ` Darren Hart
2013-04-19 7:50 ` Matt Fleming
2013-04-19 12:01 ` Josh Boyer
2013-09-10 17:43 ` Darren Hart
2013-09-12 7:55 ` Matt Fleming
2013-09-12 22:30 ` Darren Hart
2013-04-18 16:33 ` Josh Triplett
2013-04-18 16:38 ` H. Peter Anvin
2013-04-18 16:44 ` Josh Triplett
2013-04-18 19:55 ` Matt Fleming
2013-04-18 19:57 ` H. Peter Anvin
2013-04-18 19:58 ` Matthew Garrett
2013-04-18 20:11 ` Darren Hart
2013-04-18 20:13 ` H. Peter Anvin
2013-04-18 20:17 ` Darren Hart
2013-04-18 20:45 ` H. Peter Anvin
2013-04-18 22:07 ` Bryan O'Donoghue
2013-04-18 23:01 ` Josh Triplett
2013-04-18 23:44 ` H. Peter Anvin [this message]
2013-04-18 23:42 ` H. Peter Anvin
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=51708571.8080805@zytor.com \
--to=hpa@zytor.com \
--cc=bryan.odonoghue.lkml@nexus-software.ie \
--cc=darren.hart@intel.com \
--cc=josh@joshtriplett.org \
--cc=jwboyer@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=matthew.garrett@nebula.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).