kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Russ Anderson <rja@sgi.com>
Cc: matt.fleming@intel.com, kexec@lists.infradead.org,
	horms@verge.net.au, Alex Thorlton <athorlton@sgi.com>,
	Borislav Petkov <bp@suse.de>, Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH] x86: do not enable efi boot for sgi uv machine
Date: Tue, 27 May 2014 09:23:48 -0400	[thread overview]
Message-ID: <20140527132348.GE10994@redhat.com> (raw)
In-Reply-To: <20140523161930.GB4212@sgi.com>

On Fri, May 23, 2014 at 11:19:30AM -0500, Russ Anderson wrote:

[..]
> 
> > Well, we did find the bug in a combined debug session and SGI will be
> > issuing a fix soon. I don't know whether any quirk will be needed for
> > systems which don't have the fix - I guess that's something for SGI
> > people to decide. CCed and leaving in the rest for reference.
> > 
> > @Alex, Russ: this is about using kexec on UEFI boxes.
> 
> Thanks for the heads up.  Our bios made an assumption about
> mapping that was valid with the old mapping scheme but not
> with the new.  Fortunately the fix will work with both old
> and new kernels, so the fix can be added in the next bios
> update.  But we still have to be careful when removing the
> quirk, to avoid someone trying a new kernel with old bios
> and not being able to boot.

Hi,

So is there is a way for kernel to know whether BIOS has fix or not?
IOW, I am wondering how would one remove quirk or how one can be
reasonably sure that kernel is not booting with Old BIOS.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2014-05-27 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 10:14 [PATCH] x86: do not enable efi boot for sgi uv machine Dave Young
2014-05-23 13:28 ` Vivek Goyal
2014-05-23 13:47   ` Dave Young
2014-05-23 15:54     ` Borislav Petkov
2014-05-23 16:19       ` Russ Anderson
2014-05-23 19:02         ` Alex Thorlton
2014-05-26  1:58           ` Dave Young
2014-05-27  3:28         ` Dave Young
2014-05-27 16:08           ` Alex Thorlton
2014-05-27 13:23         ` Vivek Goyal [this message]
2014-05-23 15:54     ` Vivek Goyal
2014-05-26  1:52       ` Dave Young

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=20140527132348.GE10994@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=athorlton@sgi.com \
    --cc=bp@suse.de \
    --cc=dyoung@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=matt.fleming@intel.com \
    --cc=rja@sgi.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).