From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <ak@suse.de>
Cc: huang ying <huang.ying.caritas@gmail.com>,
Etienne Lorrain <etienne_lorrain@yahoo.fr>,
linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Re: [PATCH 5/5] x86_64 EFI support -v3: EFI document
Date: Thu, 09 Aug 2007 10:25:58 -0700 [thread overview]
Message-ID: <46BB4E26.6010007@zytor.com> (raw)
In-Reply-To: <200708091901.11146.ak@suse.de>
Andi Kleen wrote:
>
> Ah i didn't realize this. Ok then kexec is also quite broken.
> Somehow this must have been missed this fundamental flaw when this code was
> reviewed.
>
It wasn't missed. It was given the "there is no other way" defence, and
somehow that was considered sufficient.
Now, one could argue that kexec can just pass the boot_params from the
previous kernel boot, except there is no way to read them out, and so
it's not how it actually works.
-hpa
next prev parent reply other threads:[~2007-08-09 17:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 9:47 [PATCH 5/5] x86_64 EFI support -v3: EFI document Etienne Lorrain
2007-08-09 10:51 ` Andi Kleen
2007-08-09 11:23 ` RE : " Etienne Lorrain
2007-08-09 14:09 ` huang ying
2007-08-09 16:29 ` H. Peter Anvin
2007-08-09 17:01 ` Andi Kleen
2007-08-09 17:25 ` H. Peter Anvin [this message]
2007-08-10 13:03 ` Huang, Ying
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 3:13 Huang, Ying
2007-07-31 4:40 ` Eric W. Biederman
2007-07-31 6:58 ` Huang, Ying
2007-08-01 17:16 ` Eric W. Biederman
2007-08-07 9:29 ` Huang, Ying
2007-08-07 9:54 ` Andi Kleen
2007-08-08 8:18 ` Huang, Ying
2007-08-08 10:08 ` Andi Kleen
2007-08-08 13:46 ` Huang, Ying
2007-08-08 14:09 ` Andi Kleen
2007-08-08 15:11 ` huang ying
2007-08-08 16:23 ` Andi Kleen
2007-08-08 16:10 ` Eric W. Biederman
2007-08-08 16:22 ` Andi Kleen
2007-08-08 17:17 ` Eric W. Biederman
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=46BB4E26.6010007@zytor.com \
--to=hpa@zytor.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=etienne_lorrain@yahoo.fr \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.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.