[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [MULTIBOOT2 DOC PATCH v2 06/11] multiboot2: Add description of EFI image handle tags
24.11.2016 23:40, Daniel Kiper пишет: > Signed-off-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx> > --- > doc/multiboot.texi | 28 ++++++++++++++++++++++++++++ > doc/multiboot2.h | 16 ++++++++++++++++ > 2 files changed, 44 insertions(+) > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > index cc1edab..dca3e62 100644 > --- a/doc/multiboot.texi > +++ b/doc/multiboot.texi > @@ -1288,6 +1288,34 @@ u32 | size = 8 | > > This tag indicates ExitBootServices wasn't called > > +@subsection EFI 32-bit image handle pointer > +@example > +@group > + +-------------------+ > +u32 | type = 19 | > +u32 | size = 12 | > +u32 | pointer | Why it is not u_phys or u_virt as appropriate? > + +-------------------+ > +@end group > +@end example > + > +This tag contains pointer to EFI i386 image handle. > +Usually it is boot loader image handle. > + > +@subsection EFI 64-bit image handle pointer > +@example > +@group > + +-------------------+ > +u32 | type = 20 | > +u32 | size = 16 | > +u64 | pointer | Same. Again, why there are two tags in the first place? It sounds like perfect fit for "data of the same size as target architecture [virtual|physical] address size". _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |