From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Josh Boyer <jwboyer-rxtnV0ftBwyoClj4AeEUq9i2O/JbrIOy@public.gmane.org>
Cc: "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: EFI mode after running kexec
Date: Thu, 29 Aug 2013 12:15:43 -0700 [thread overview]
Message-ID: <20130829191543.GA11624@kroah.com> (raw)
In-Reply-To: <CA+5PVA7jec5DAxgKachkBw1VFobz4rVMQwcqzYQ7ynk7=+d+zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Aug 29, 2013 at 08:18:39AM -0400, Josh Boyer wrote:
> On Wed, Aug 28, 2013 at 10:26 PM, Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org> wrote:
> > Hi all,
> >
> > I've been messing with UEFI booting a kernel and then later on, using
> > kexec to boot another kernel, and noticed that the kexec'ed kernel is
> > not really in EFI mode, although the EFI framebuffer seems present and
> > able to be used.
> >
> > Is this to be expected? I'd think that the EFI framebuffer wouldn't be
> > around anymore. Odds are this is a BIOS bug, given that the machine I'm
> > using is a really old UEFI mode (i.e. before secure boot mode ever
> > showed up), but should it work this way?
>
> AFAIK, it's to be expected at this point. kexec doesn't work as it
> should with UEFI.
How "should" it work? It seems to boot a kernel just fine, although not
in EFI mode, which makes sense (I had forgotten about the BootServices
stuff.)
> I believe Matthew and/or Matt can elaborate further, but it has to do
> with only being able to call ExitBootServices once and providing
> mappings to the UEFI Runtime services functions.
That makes sense.
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-29 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 2:26 EFI mode after running kexec Greg KH
[not found] ` <20130829022632.GA26862-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-08-29 12:18 ` Josh Boyer
[not found] ` <CA+5PVA7jec5DAxgKachkBw1VFobz4rVMQwcqzYQ7ynk7=+d+zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-29 12:35 ` James Bottomley
2013-08-29 19:20 ` Greg KH
[not found] ` <20130829192001.GB11624-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-08-30 16:44 ` H. Peter Anvin
[not found] ` <5220CBEE.20706-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-08-31 4:52 ` Borislav Petkov
[not found] ` <20130831045244.GA12617-W2mmg7yuTz0QF/eBCRgRTA@public.gmane.org>
2013-08-31 4:59 ` Greg KH
2013-08-29 19:15 ` Greg KH [this message]
[not found] ` <20130829191543.GA11624-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-08-29 20:36 ` Josh Boyer
[not found] ` <CA+5PVA5PHc4vOcWwCgTHS=CP8oei-Jc5GK2dfi=EdD_wGVZpXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-29 20:53 ` Greg KH
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=20130829191543.GA11624@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=jwboyer-rxtnV0ftBwyoClj4AeEUq9i2O/JbrIOy@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.