From: "matt@console-pimps.org" <matt@console-pimps.org>
To: Zachary Bobroff <zacharyb@ami.com>
Cc: "'H. Peter Anvin'" <hpa@zytor.com>,
'Jan Beulich' <jbeulich@suse.com>,
"matt.fleming@intel.com" <matt.fleming@intel.com>,
"mjg59@srcf.ucam.org" <mjg59@srcf.ucam.org>,
Joey Lee <JLee@suse.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] x86, efi: retry ExitBootServices() on failure
Date: Wed, 26 Jun 2013 14:12:00 +0100 [thread overview]
Message-ID: <20130626131200.GN22026@console-pimps.org> (raw)
In-Reply-To: <7BD74F8E52BFD147B6C83AE7A1E893FFE28622FD@atlms1.us.megatrends.com>
On Thu, 20 Jun, at 06:04:50PM, Zachary Bobroff wrote:
> All,
>
> I am attaching a further updated version of eboot.c . We removed the
> low_alloc routine from the exit_boot function only. We also removed
> the goto statements(sorry we just aren’t huge fans of goto's in c, you
> can change it back to be goto oriented if you want though) and put it
> in a loop that is counting down from retry count. You can see the
> loop is based upon this conditional:
It would be much easier to review these changes if you sent them as a
patch against a git tree, using git to generate the patch. Failing that,
even a plain old diff-format file would be acceptable.
> while((ExitRetryCount > 0) && (status != EFI_SUCCESS)) {
>
> So we have currently set ExitRetryCount to 2 (a couple of lines above):
> int ExitRetryCount = 2;
>
> However, I have a suggestion and im not entirely sure how difficult it
> would be, im just suggesting it might not be a bad idea. We can
> initialize this ExitRetryCount to be some default value, but if
> grub(or a different bootloader) passes some updated value,
> ExitRetryCount could be updated with this value. Myself, I don’t know
> the level of complexity it creates pulling a kernel parameter, but
> given a decent example, I could see about adding that support.
> Allowing passing of a parameter could eliminate problems with the
> systems that may be out of specification.
We try to pull workarounds for these problems into the kernel, rather
than relying on bootloaders to pass in the necessary flags. People
rarely want to update their boot loaders, but most distributions release
updates for installed kernels semi-regularly.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2013-06-26 13:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 6:52 [PATCH] x86, efi: retry ExitBootServices() on failure Matt Fleming
2013-06-11 7:22 ` Matt Fleming
2013-06-13 16:00 ` joeyli
2013-06-17 9:21 ` Matt Fleming
2013-06-17 9:46 ` Jan Beulich
2013-06-17 10:17 ` Matt Fleming
2013-06-17 10:41 ` joeyli
2013-06-17 11:02 ` Jan Beulich
2013-06-17 12:30 ` Matt Fleming
2013-06-18 0:18 ` Zachary Bobroff
2013-06-18 2:47 ` joeyli
2013-06-18 4:20 ` Zachary Bobroff
2013-06-18 7:34 ` joeyli
2013-06-18 13:03 ` Jan Beulich
2013-06-18 22:12 ` Zachary Bobroff
2013-06-19 8:43 ` matt
2013-06-19 8:53 ` H. Peter Anvin
2013-06-20 18:04 ` Zachary Bobroff
2013-06-26 13:12 ` matt [this message]
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=20130626131200.GN22026@console-pimps.org \
--to=matt@console-pimps.org \
--cc=JLee@suse.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=stable@vger.kernel.org \
--cc=zacharyb@ami.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