From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Shea Levy <shea@shealevy.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: EFI Boot Stub Early Console
Date: Tue, 20 Mar 2012 16:45:17 +0100 [thread overview]
Message-ID: <4F68A60D.2020303@gmail.com> (raw)
In-Reply-To: <1332172989.4041.52.camel@mfleming-mobl1.ger.corp.intel.com>
Hey Matt,
Op 19-03-12 17:03, Matt Fleming schreef:
> On Mon, 2012-03-19 at 15:56 +0000, Alan Cox wrote:
>>>> any bootloader (including the bootstub) will call ExitBootServices()
>>>> before any printk'ing actually happens?? Or am I misunderstanding the
>>>> spec somehow? I suppose I could just try it and see what happens...
>>> Oops. Good point, that isn't going to work.
>> Surely it works fine if you are using bootstub directly from EFI ?
> Yeah, up until the point you call ExitBootServices(), which is very
> early in the boot process. After that you can't rely on the validity of
> the console pointers in the system table.
>
I think my system spontaneously rebooted when I tried to
do some output right after ExitBootServices when debugging
the efi stub, so not only is this unreliable, it will fail to boot for
at least some systems out there.
~Maarten
next prev parent reply other threads:[~2012-03-20 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 18:56 EFI Boot Stub Early Console Shea Levy
2012-03-12 19:00 ` Shea Levy
2012-03-12 22:11 ` H. Peter Anvin
2012-03-12 22:18 ` Shea Levy
2012-03-12 22:23 ` H. Peter Anvin
2012-03-12 22:28 ` Shea Levy
2012-03-17 13:12 ` Shea Levy
2012-03-18 11:21 ` Matt Fleming
2012-03-18 12:10 ` Shea Levy
2012-03-19 8:47 ` Matt Fleming
2012-03-19 15:56 ` Alan Cox
2012-03-19 16:02 ` Shea Levy
2012-03-19 16:03 ` Matt Fleming
2012-03-20 15:45 ` Maarten Lankhorst [this message]
2012-03-20 16:43 ` H. Peter Anvin
[not found] ` <CAOhV88Om7hKHeaGNp-PtFkn=y0T9EBQCbPSBE58vOYQ2+Genew@mail.gmail.com>
2012-03-18 4:29 ` Shea Levy
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=4F68A60D.2020303@gmail.com \
--to=m.b.lankhorst@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=shea@shealevy.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