* [PATCH v3] multiboot2: clarify usage of the address tag
@ 2018-06-11 11:49 Roger Pau Monne
2018-06-11 13:02 ` Daniel Kiper
2018-06-11 13:02 ` Daniel Kiper
0 siblings, 2 replies; 4+ messages in thread
From: Roger Pau Monne @ 2018-06-11 11:49 UTC (permalink / raw)
To: grub-devel; +Cc: Roger Pau Monne, Daniel Kiper, xen-devel
Add a note to spell out that if the address tag is not present the
file should be loaded using the elf header.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Cc: xen-devel@lists.xenproject.org
---
Changes since v2:
- Clarify that the address tag must be used if present.
Changes since v1:
- s/elf/@sc{elf}/
- s/Multiboot/Multiboot2/
---
doc/multiboot.texi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 2e2d7e74a..df8a0d056 100644
--- a/doc/multiboot.texi
+++ b/doc/multiboot.texi
@@ -509,6 +509,14 @@ assumes that no bss segment is present.
@end table
+Note: This information does not need to be provided if the kernel image
+is in @sc{elf} format, but it must be provided if the image is in a.out
+format or in some other format. When the address tag is present it must
+be used in order to load the image, regardless of whether an @sc{elf}
+header is also present. Compliant boot loaders must be able to load
+images that are either in @sc{elf} format or contain the address tag
+embedded in the Multiboot2 header.
+
@subsection The entry address tag of Multiboot2 header
@example
--
2.17.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v3] multiboot2: clarify usage of the address tag
2018-06-11 11:49 [PATCH v3] multiboot2: clarify usage of the address tag Roger Pau Monne
2018-06-11 13:02 ` Daniel Kiper
@ 2018-06-11 13:02 ` Daniel Kiper
1 sibling, 0 replies; 4+ messages in thread
From: Daniel Kiper @ 2018-06-11 13:02 UTC (permalink / raw)
To: Roger Pau Monne; +Cc: grub-devel, xen-devel
On Mon, Jun 11, 2018 at 01:49:02PM +0200, Roger Pau Monne wrote:
> Add a note to spell out that if the address tag is not present the
> file should be loaded using the elf header.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
If there are no objections I will apply this in a week or so.
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v3] multiboot2: clarify usage of the address tag
2018-06-11 11:49 [PATCH v3] multiboot2: clarify usage of the address tag Roger Pau Monne
@ 2018-06-11 13:02 ` Daniel Kiper
2018-06-11 13:02 ` Daniel Kiper
1 sibling, 0 replies; 4+ messages in thread
From: Daniel Kiper @ 2018-06-11 13:02 UTC (permalink / raw)
To: Roger Pau Monne; +Cc: grub-devel, xen-devel
On Mon, Jun 11, 2018 at 01:49:02PM +0200, Roger Pau Monne wrote:
> Add a note to spell out that if the address tag is not present the
> file should be loaded using the elf header.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
If there are no objections I will apply this in a week or so.
Daniel
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH v3] multiboot2: clarify usage of the address tag
@ 2018-06-11 11:49 Roger Pau Monne
0 siblings, 0 replies; 4+ messages in thread
From: Roger Pau Monne @ 2018-06-11 11:49 UTC (permalink / raw)
To: grub-devel; +Cc: xen-devel, Daniel Kiper, Roger Pau Monne
Add a note to spell out that if the address tag is not present the
file should be loaded using the elf header.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Cc: xen-devel@lists.xenproject.org
---
Changes since v2:
- Clarify that the address tag must be used if present.
Changes since v1:
- s/elf/@sc{elf}/
- s/Multiboot/Multiboot2/
---
doc/multiboot.texi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 2e2d7e74a..df8a0d056 100644
--- a/doc/multiboot.texi
+++ b/doc/multiboot.texi
@@ -509,6 +509,14 @@ assumes that no bss segment is present.
@end table
+Note: This information does not need to be provided if the kernel image
+is in @sc{elf} format, but it must be provided if the image is in a.out
+format or in some other format. When the address tag is present it must
+be used in order to load the image, regardless of whether an @sc{elf}
+header is also present. Compliant boot loaders must be able to load
+images that are either in @sc{elf} format or contain the address tag
+embedded in the Multiboot2 header.
+
@subsection The entry address tag of Multiboot2 header
@example
--
2.17.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply related [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-06-11 13:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-11 11:49 [PATCH v3] multiboot2: clarify usage of the address tag Roger Pau Monne
2018-06-11 13:02 ` Daniel Kiper
2018-06-11 13:02 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2018-06-11 11:49 Roger Pau Monne
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.