From: ian.campbell@citrix•com (Ian Campbell)
To: linux-arm-kernel@lists•infradead.org
Subject: [Xen-devel] [PATCH] efi/libstub/fdt: Standardize the names of EFI stub parameters
Date: Thu, 10 Sep 2015 13:58:25 +0100 [thread overview]
Message-ID: <1441889905.24450.382.camel@citrix.com> (raw)
In-Reply-To: <20150910121514.GE29293@leverpostej>
On Thu, 2015-09-10 at 13:15 +0100, Mark Rutland wrote:
> > In any case this should be separate from the shim ABI discussion.
>
> I disagree; I think this is very much relevant to the ABI discussion.
> That's not to say that I insist on a particular approach, but I think
> that they need to be considered together.
Taking a step back, the reason for using the EFI stub parameters is only
(AFAIK) in order to be able to locate the ACPI RDSP (the root table
pointer), which as it happens is normally passed via one of the EFI
firmware tables.
If there was a way to achieve that goal (i.e. another way to find the RSDP)
without opening the can of UEFI worms then we could consider that opiton
too.
a way != the legacy x86 thing of scanning low memory of the signature, of
course.
Ian.
next prev parent reply other threads:[~2015-09-10 12:58 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 8:41 [PATCH] efi/libstub/fdt: Standardize the names of EFI stub parameters Shannon Zhao
2015-09-10 9:52 ` Mark Rutland
2015-09-10 10:19 ` Stefano Stabellini
2015-09-10 11:24 ` Mark Rutland
2015-09-10 11:37 ` Stefano Stabellini
2015-09-10 12:15 ` Mark Rutland
2015-09-10 12:58 ` Ian Campbell [this message]
2015-09-10 13:08 ` [Xen-devel] " Jan Beulich
2015-09-10 13:30 ` Ian Campbell
2015-09-10 13:52 ` Stefano Stabellini
2015-09-10 14:13 ` Leif Lindholm
2015-09-10 14:49 ` Mark Rutland
2015-09-10 16:10 ` Stefano Stabellini
2015-09-10 16:23 ` Mark Rutland
2015-09-11 12:46 ` Daniel Kiper
2015-09-11 13:14 ` Stefano Stabellini
2015-09-11 13:30 ` Ard Biesheuvel
2015-09-11 15:45 ` Daniel Kiper
2015-09-14 8:42 ` Shannon Zhao
2015-09-14 9:09 ` Ard Biesheuvel
2015-09-14 9:31 ` Shannon Zhao
2015-09-14 9:36 ` Ard Biesheuvel
2015-09-14 10:39 ` [Xen-devel] " Jan Beulich
2015-09-14 11:16 ` Ard Biesheuvel
2015-09-14 11:34 ` Jan Beulich
2015-09-11 16:33 ` Mark Rutland
2015-09-11 16:25 ` Mark Rutland
2015-09-12 11:36 ` Daniel Kiper
2015-09-14 9:25 ` Mark Rutland
2015-09-14 9:43 ` Ard Biesheuvel
2015-09-14 9:57 ` Ian Campbell
2015-09-14 10:02 ` Ard Biesheuvel
2015-09-14 10:25 ` Ian Campbell
2015-09-14 12:28 ` Daniel Kiper
2015-09-14 13:09 ` Ard Biesheuvel
2015-09-14 13:57 ` Daniel Kiper
2015-09-14 9:47 ` Stefano Stabellini
2015-09-14 12:19 ` Daniel Kiper
2015-09-11 11:00 ` Ian Campbell
2015-09-10 12:55 ` Jan Beulich
2015-09-10 14:53 ` Mark Rutland
2015-09-10 15:06 ` Jan Beulich
2015-09-11 16:36 ` Mark Rutland
2015-09-10 11:32 ` Andrew Turner
2015-09-10 11:48 ` Julien Grall
2015-09-10 12:05 ` Roger Pau Monné
2015-09-10 12:53 ` [Xen-devel] " Julien Grall
2015-09-17 11:43 ` Shannon Zhao
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=1441889905.24450.382.camel@citrix.com \
--to=ian.campbell@citrix$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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