From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <gregkh@linuxfoundation.org>,
"Bryan O'Donoghue" <bryan.odonoghue.lkml@nexus-software.ie>
Cc: matt@console-pimps.org, matthew.garrett@nebula.com,
linux-efi@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, darren.hart@intel.com,
josh@joshtriplett.org, mingo@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] Remove warning in efi_enter_virtual_mode V2
Date: Thu, 18 Apr 2013 23:00:27 -0700 [thread overview]
Message-ID: <bb2db2a1-835f-47d0-830d-0dd3785343a9@email.android.com> (raw)
In-Reply-To: <20130419055813.GA16443@kroah.com>
The only real use for command line options is to be able to get users to test something during troubleshooting.
Greg KH <gregkh@linuxfoundation.org> wrote:
>On Wed, Apr 17, 2013 at 11:05:41PM +0100, Bryan O'Donoghue wrote:
>> Some EFI BIOS stores BGRT data in the wrong place and some EFI based
>> BIOS also requires mapping of boot code/data when doing
>> efi_enter_virtual_mode.
>>
>> Current code in efi_enter_virtual_mode maps both EFI_RUNTIME_MEMORY
>and
>> BIOS boot code/data.
>>
>> This patch gives the option to switch off that behavior - if your
>BIOS
>> has neither BGRT - nor bugs that require mapping of EFI boot
>code/data
>
>No, never add new boot options, no users, or distros, know to set them.
>Isn't there some way we can dynamically determine this instead?
>
>thanks,
>
>greg k-h
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-04-19 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 22:05 Bryan O'Donoghue
2013-04-19 5:58 ` Greg KH
2013-04-19 6:00 ` H. Peter Anvin [this message]
2013-04-19 6:11 ` Greg KH
2013-04-19 6:17 ` H. Peter Anvin
2013-04-19 11:15 ` Bryan O'Donoghue
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=bb2db2a1-835f-47d0-830d-0dd3785343a9@email.android.com \
--to=hpa@zytor.com \
--cc=bryan.odonoghue.lkml@nexus-software.ie \
--cc=darren.hart@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=josh@joshtriplett.org \
--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
Powered by JetHome