* [PATCH] multiboot2: clarify usage of the address tag
@ 2018-06-05 9:55 Roger Pau Monne
2018-06-06 17:28 ` Daniel Kiper
2018-06-06 17:28 ` Daniel Kiper
0 siblings, 2 replies; 8+ messages in thread
From: Roger Pau Monne @ 2018-06-05 9:55 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
---
doc/multiboot.texi | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 2e2d7e74a..196f9c17a 100644
--- a/doc/multiboot.texi
+++ b/doc/multiboot.texi
@@ -509,6 +509,12 @@ assumes that no bss segment is present.
@end table
+Note: This information does not need to be provided if the kernel
+image is in elf format, but it must be provided if the image is in
+a.out format or in some other format. Compliant boot loaders must be
+able to load images that are either in elf format or contain the
+address tag embedded in the Multiboot header.
+
@subsection The entry address tag of Multiboot2 header
@example
--
2.17.0
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH] multiboot2: clarify usage of the address tag
2018-06-05 9:55 [PATCH] multiboot2: clarify usage of the address tag Roger Pau Monne
@ 2018-06-06 17:28 ` Daniel Kiper
2018-06-07 14:46 ` Roger Pau Monné
2018-06-07 14:46 ` Roger Pau Monné
2018-06-06 17:28 ` Daniel Kiper
1 sibling, 2 replies; 8+ messages in thread
From: Daniel Kiper @ 2018-06-06 17:28 UTC (permalink / raw)
To: Roger Pau Monne; +Cc: grub-devel, xen-devel
On Tue, Jun 05, 2018 at 11:55:36AM +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>
> ---
> Cc: Daniel Kiper <daniel.kiper@oracle.com>
> Cc: xen-devel@lists.xenproject.org
> ---
> doc/multiboot.texi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> index 2e2d7e74a..196f9c17a 100644
> --- a/doc/multiboot.texi
> +++ b/doc/multiboot.texi
> @@ -509,6 +509,12 @@ assumes that no bss segment is present.
>
> @end table
>
> +Note: This information does not need to be provided if the kernel
> +image is in elf format, but it must be provided if the image is in
s/elf/@sc{elf}/
> +a.out format or in some other format. Compliant boot loaders must be
> +able to load images that are either in elf format or contain the
Ditto.
> +address tag embedded in the Multiboot header.
s/Multiboot/Multiboot2/
I think that it is also worth mentioning that the address tag has
preference over relevant data provided in ELF header.
Additionally, may I ask you to provide similar patch for Multiboot spec?
You can find it in multiboot branch. Please look for "The address fields
of Multiboot header" paragraph.
Daniel
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] multiboot2: clarify usage of the address tag
2018-06-06 17:28 ` Daniel Kiper
@ 2018-06-07 14:46 ` Roger Pau Monné
2018-06-07 15:38 ` Daniel Kiper
2018-06-07 15:38 ` Daniel Kiper
2018-06-07 14:46 ` Roger Pau Monné
1 sibling, 2 replies; 8+ messages in thread
From: Roger Pau Monné @ 2018-06-07 14:46 UTC (permalink / raw)
To: Daniel Kiper; +Cc: grub-devel, xen-devel
On Wed, Jun 06, 2018 at 07:28:20PM +0200, Daniel Kiper wrote:
> On Tue, Jun 05, 2018 at 11:55:36AM +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>
> > ---
> > Cc: Daniel Kiper <daniel.kiper@oracle.com>
> > Cc: xen-devel@lists.xenproject.org
> > ---
> > doc/multiboot.texi | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> > index 2e2d7e74a..196f9c17a 100644
> > --- a/doc/multiboot.texi
> > +++ b/doc/multiboot.texi
> > @@ -509,6 +509,12 @@ assumes that no bss segment is present.
> >
> > @end table
> >
> > +Note: This information does not need to be provided if the kernel
> > +image is in elf format, but it must be provided if the image is in
>
> s/elf/@sc{elf}/
>
> > +a.out format or in some other format. Compliant boot loaders must be
> > +able to load images that are either in elf format or contain the
>
> Ditto.
>
> > +address tag embedded in the Multiboot header.
>
> s/Multiboot/Multiboot2/
>
> I think that it is also worth mentioning that the address tag has
> preference over relevant data provided in ELF header.
>
> Additionally, may I ask you to provide similar patch for Multiboot spec?
> You can find it in multiboot branch. Please look for "The address fields
> of Multiboot header" paragraph.
Multiboot1 already has such paragraph in the "3.1.2 The magic fields
of Multiboot header" section.
Thanks, Roger.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] multiboot2: clarify usage of the address tag
2018-06-07 14:46 ` Roger Pau Monné
@ 2018-06-07 15:38 ` Daniel Kiper
2018-06-07 15:38 ` Daniel Kiper
1 sibling, 0 replies; 8+ messages in thread
From: Daniel Kiper @ 2018-06-07 15:38 UTC (permalink / raw)
To: Roger Pau Monné; +Cc: grub-devel, xen-devel
On Thu, Jun 07, 2018 at 04:46:37PM +0200, Roger Pau Monné wrote:
> On Wed, Jun 06, 2018 at 07:28:20PM +0200, Daniel Kiper wrote:
> > On Tue, Jun 05, 2018 at 11:55:36AM +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>
> > > ---
> > > Cc: Daniel Kiper <daniel.kiper@oracle.com>
> > > Cc: xen-devel@lists.xenproject.org
> > > ---
> > > doc/multiboot.texi | 6 ++++++
> > > 1 file changed, 6 insertions(+)
> > >
> > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> > > index 2e2d7e74a..196f9c17a 100644
> > > --- a/doc/multiboot.texi
> > > +++ b/doc/multiboot.texi
> > > @@ -509,6 +509,12 @@ assumes that no bss segment is present.
> > >
> > > @end table
> > >
> > > +Note: This information does not need to be provided if the kernel
> > > +image is in elf format, but it must be provided if the image is in
> >
> > s/elf/@sc{elf}/
> >
> > > +a.out format or in some other format. Compliant boot loaders must be
> > > +able to load images that are either in elf format or contain the
> >
> > Ditto.
> >
> > > +address tag embedded in the Multiboot header.
> >
> > s/Multiboot/Multiboot2/
> >
> > I think that it is also worth mentioning that the address tag has
> > preference over relevant data provided in ELF header.
> >
> > Additionally, may I ask you to provide similar patch for Multiboot spec?
> > You can find it in multiboot branch. Please look for "The address fields
> > of Multiboot header" paragraph.
>
> Multiboot1 already has such paragraph in the "3.1.2 The magic fields
> of Multiboot header" section.
Yep, you are right. So, please just send me updated Multiboot2 spec patch.
Daniel
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] multiboot2: clarify usage of the address tag
2018-06-07 14:46 ` Roger Pau Monné
2018-06-07 15:38 ` Daniel Kiper
@ 2018-06-07 15:38 ` Daniel Kiper
1 sibling, 0 replies; 8+ messages in thread
From: Daniel Kiper @ 2018-06-07 15:38 UTC (permalink / raw)
To: Roger Pau Monné; +Cc: grub-devel, xen-devel
On Thu, Jun 07, 2018 at 04:46:37PM +0200, Roger Pau Monné wrote:
> On Wed, Jun 06, 2018 at 07:28:20PM +0200, Daniel Kiper wrote:
> > On Tue, Jun 05, 2018 at 11:55:36AM +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>
> > > ---
> > > Cc: Daniel Kiper <daniel.kiper@oracle.com>
> > > Cc: xen-devel@lists.xenproject.org
> > > ---
> > > doc/multiboot.texi | 6 ++++++
> > > 1 file changed, 6 insertions(+)
> > >
> > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> > > index 2e2d7e74a..196f9c17a 100644
> > > --- a/doc/multiboot.texi
> > > +++ b/doc/multiboot.texi
> > > @@ -509,6 +509,12 @@ assumes that no bss segment is present.
> > >
> > > @end table
> > >
> > > +Note: This information does not need to be provided if the kernel
> > > +image is in elf format, but it must be provided if the image is in
> >
> > s/elf/@sc{elf}/
> >
> > > +a.out format or in some other format. Compliant boot loaders must be
> > > +able to load images that are either in elf format or contain the
> >
> > Ditto.
> >
> > > +address tag embedded in the Multiboot header.
> >
> > s/Multiboot/Multiboot2/
> >
> > I think that it is also worth mentioning that the address tag has
> > preference over relevant data provided in ELF header.
> >
> > Additionally, may I ask you to provide similar patch for Multiboot spec?
> > You can find it in multiboot branch. Please look for "The address fields
> > of Multiboot header" paragraph.
>
> Multiboot1 already has such paragraph in the "3.1.2 The magic fields
> of Multiboot header" section.
Yep, you are right. So, please just send me updated Multiboot2 spec patch.
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] multiboot2: clarify usage of the address tag
2018-06-06 17:28 ` Daniel Kiper
2018-06-07 14:46 ` Roger Pau Monné
@ 2018-06-07 14:46 ` Roger Pau Monné
1 sibling, 0 replies; 8+ messages in thread
From: Roger Pau Monné @ 2018-06-07 14:46 UTC (permalink / raw)
To: Daniel Kiper; +Cc: grub-devel, xen-devel
On Wed, Jun 06, 2018 at 07:28:20PM +0200, Daniel Kiper wrote:
> On Tue, Jun 05, 2018 at 11:55:36AM +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>
> > ---
> > Cc: Daniel Kiper <daniel.kiper@oracle.com>
> > Cc: xen-devel@lists.xenproject.org
> > ---
> > doc/multiboot.texi | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> > index 2e2d7e74a..196f9c17a 100644
> > --- a/doc/multiboot.texi
> > +++ b/doc/multiboot.texi
> > @@ -509,6 +509,12 @@ assumes that no bss segment is present.
> >
> > @end table
> >
> > +Note: This information does not need to be provided if the kernel
> > +image is in elf format, but it must be provided if the image is in
>
> s/elf/@sc{elf}/
>
> > +a.out format or in some other format. Compliant boot loaders must be
> > +able to load images that are either in elf format or contain the
>
> Ditto.
>
> > +address tag embedded in the Multiboot header.
>
> s/Multiboot/Multiboot2/
>
> I think that it is also worth mentioning that the address tag has
> preference over relevant data provided in ELF header.
>
> Additionally, may I ask you to provide similar patch for Multiboot spec?
> You can find it in multiboot branch. Please look for "The address fields
> of Multiboot header" paragraph.
Multiboot1 already has such paragraph in the "3.1.2 The magic fields
of Multiboot header" section.
Thanks, Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] multiboot2: clarify usage of the address tag
2018-06-05 9:55 [PATCH] multiboot2: clarify usage of the address tag Roger Pau Monne
2018-06-06 17:28 ` Daniel Kiper
@ 2018-06-06 17:28 ` Daniel Kiper
1 sibling, 0 replies; 8+ messages in thread
From: Daniel Kiper @ 2018-06-06 17:28 UTC (permalink / raw)
To: Roger Pau Monne; +Cc: grub-devel, xen-devel
On Tue, Jun 05, 2018 at 11:55:36AM +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>
> ---
> Cc: Daniel Kiper <daniel.kiper@oracle.com>
> Cc: xen-devel@lists.xenproject.org
> ---
> doc/multiboot.texi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> index 2e2d7e74a..196f9c17a 100644
> --- a/doc/multiboot.texi
> +++ b/doc/multiboot.texi
> @@ -509,6 +509,12 @@ assumes that no bss segment is present.
>
> @end table
>
> +Note: This information does not need to be provided if the kernel
> +image is in elf format, but it must be provided if the image is in
s/elf/@sc{elf}/
> +a.out format or in some other format. Compliant boot loaders must be
> +able to load images that are either in elf format or contain the
Ditto.
> +address tag embedded in the Multiboot header.
s/Multiboot/Multiboot2/
I think that it is also worth mentioning that the address tag has
preference over relevant data provided in ELF header.
Additionally, may I ask you to provide similar patch for Multiboot spec?
You can find it in multiboot branch. Please look for "The address fields
of Multiboot header" paragraph.
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH] multiboot2: clarify usage of the address tag
@ 2018-06-05 9:55 Roger Pau Monne
0 siblings, 0 replies; 8+ messages in thread
From: Roger Pau Monne @ 2018-06-05 9:55 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
---
doc/multiboot.texi | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 2e2d7e74a..196f9c17a 100644
--- a/doc/multiboot.texi
+++ b/doc/multiboot.texi
@@ -509,6 +509,12 @@ assumes that no bss segment is present.
@end table
+Note: This information does not need to be provided if the kernel
+image is in elf format, but it must be provided if the image is in
+a.out format or in some other format. Compliant boot loaders must be
+able to load images that are either in elf format or contain the
+address tag embedded in the Multiboot header.
+
@subsection The entry address tag of Multiboot2 header
@example
--
2.17.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply related [flat|nested] 8+ messages in thread
end of thread, other threads:[~2018-06-07 15:38 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-06-05 9:55 [PATCH] multiboot2: clarify usage of the address tag Roger Pau Monne
2018-06-06 17:28 ` Daniel Kiper
2018-06-07 14:46 ` Roger Pau Monné
2018-06-07 15:38 ` Daniel Kiper
2018-06-07 15:38 ` Daniel Kiper
2018-06-07 14:46 ` Roger Pau Monné
2018-06-06 17:28 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2018-06-05 9:55 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.