From: Dave Young <dyoung@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: horms@verge.net.au, kexec@lists.infradead.org,
Borislav Petkov <bp@suse.de>,
matt.fleming@intel.com
Subject: Re: [PATCH] x86: do not enable efi boot for sgi uv machine
Date: Mon, 26 May 2014 09:52:56 +0800 [thread overview]
Message-ID: <20140526015255.GA2863@darkstar.nay.redhat.com> (raw)
In-Reply-To: <20140523155427.GF2126@redhat.com>
On Fri, May 23, 2014 at 11:54:27AM -0400, Vivek Goyal wrote:
> On Fri, May 23, 2014 at 09:47:08AM -0400, Dave Young wrote:
> > Hi,
> >
> > Vivek, replying with webmail, sorry for the formatting issue.
> >
> > Another way is export the mapping scheme in sysfs. So if kernel boot
> > with efi=old_map we can detect it as well. OTOH in future there's probably
> > other quirk system.
> >
> > So kexec-tools can switch to use old way if kernel use ioremap.
>
> Exporting type of mapping being used in current kernel and automatically
> deciding that whether to boot with efi or noefi sounds reasonable to me.
> I am assuming that once type of mapping got fixed in first kernel boot
> it can't be changed in subsequent kernel boots?
Right, 2nd kernel will continue to use the original mapping because we can
only call the firmware function once to enter virtual mode.
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-05-26 1:53 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
2014-05-23 15:54 ` Vivek Goyal
2014-05-26 1:52 ` Dave Young [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=20140526015255.GA2863@darkstar.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=bp@suse.de \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=matt.fleming@intel.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.