public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Joey Lee <JLee@suse.com>, Zach Bobroff <zacharyb@ami.com>,
	Matt Fleming <matt.fleming@intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] x86, efi: retry ExitBootServices() on failure
Date: Mon, 17 Jun 2013 11:17:45 +0100	[thread overview]
Message-ID: <20130617101745.GB8569@console-pimps.org> (raw)
In-Reply-To: <51BEF71402000078000DEC12@nat28.tlf.novell.com>

On Mon, 17 Jun, at 10:46:28AM, Jan Beulich wrote:
> To me, all this looks like it is being done on phenomenological basis,
> taking a particular build of a particular firmware implementation as
> the reference. Imo we shouldn't change the code in this way. This
> also applies to the fact that the step is being doubled rather than
> e.g. tripled: With it ending up a "again" anyway (see below), what's
> the point of avoiding one more of the iterations?
> 
> Generic considerations would result in the increment being at least
> 3 * element size; twice the element size assumes that the allocator
> would behave in certain ways (like returning the head or tail part of
> a larger piece of memory).
 
I have no issue with changing the multiplier. But let's get
clarification from Zach as to what exactly is going on here.

> I agree that there ought to be an upper limit. But a single retry here
> again looks like a tailored solution to a particular observed (mis-)
> behavior, rather than something resulting from general considerations.

What value would you suggest for the retry?

-- 
Matt Fleming, Intel Open Source Technology Center

  reply	other threads:[~2013-06-17 10:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11  6:52 [PATCH] x86, efi: retry ExitBootServices() on failure Matt Fleming
     [not found] ` <1370933558-10128-1-git-send-email-matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-06-11  7:22   ` Matt Fleming
2013-06-13 16:00   ` joeyli
     [not found]     ` <1371139233.6523.272.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
2013-06-17  9:21       ` Matt Fleming
     [not found]         ` <20130617092107.GA5440-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-06-17  9:46           ` Jan Beulich
2013-06-17 10:17             ` Matt Fleming [this message]
     [not found]               ` <20130617101745.GB8569-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
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
     [not found]                           ` <B0277B82-F2C5-4BA9-B42C-F554E12F6961-gH/BEeFdNRQ@public.gmane.org>
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
  -- strict thread matches above, loose matches on Subject: below --
2013-05-22 14:15 Matt Fleming

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=20130617101745.GB8569@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=JBeulich@suse.com \
    --cc=JLee@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