From: Alex Thorlton <athorlton@sgi.com>
To: Dave Young <dyoung@redhat.com>
Cc: Russ Anderson <rja@sgi.com>,
matt.fleming@intel.com, kexec@lists.infradead.org,
horms@verge.net.au, Alex Thorlton <athorlton@sgi.com>,
Borislav Petkov <bp@suse.de>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] x86: do not enable efi boot for sgi uv machine
Date: Tue, 27 May 2014 11:08:14 -0500 [thread overview]
Message-ID: <20140527160814.GJ10771@sgi.com> (raw)
In-Reply-To: <20140527032816.GD2372@darkstar.nay.redhat.com>
On Tue, May 27, 2014 at 11:28:16AM +0800, Dave Young 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.
>
> The quirk will quirk out all uv system, will SGI people provide a patch
> to only add quirk for old firmware version or just removing the quirk
> after the update is out?
Yes - I'm working on that now. I'll make sure you're copied on the
patch when I do get it all worked out.
> Thanks
> Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-05-27 16:07 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 [this message]
2014-05-27 13:23 ` Vivek Goyal
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=20140527160814.GJ10771@sgi.com \
--to=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 \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.