mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Philipp Kohlbecher <xt28@gmx.de>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: documentation fix regarding boot protocol
Date: Mon, 15 Dec 2008 11:34:22 +0000	[thread overview]
Message-ID: <1229340862.25349.95.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <49463F1C.1070401@gmx.de>

On Mon, 2008-12-15 at 12:27 +0100, Philipp Kohlbecher wrote:
> Ian Campbell wrote:
> > On Sun, 2008-12-14 at 18:50 +0100, Philipp Kohlbecher wrote:
> >> Documentation/x86/boot.txt describes payload_offset as the offset
> >> from the end of the real-mode code. In fact, it is more accurately
> >> described as the offset from the beginning of the protected-mode
> >> code, as (a) this is how it is actually calculated and (b) the padding
> >> after the real-mode code is not included in the offset.
> >>
> >> Signed-off-by: Philipp Kohlbecher <xt28@gmx.de>
> > 
> > Acked-by: Ian Campbell <ijc@hellion.org.uk>
> > 
> > The padding after the real-mode code which you mention is just the
> > implicit padding because the size of the real-mode code is specified in
> > sectors (and hence is rounded up), isn't it?
> 
> Yes, it is. You can certainly view the padding as an implicit part of 
> the real-mode code, which is why the current statement isn't wrong -- 
> there is simply room for improvement.

Agreed.

> > Is it worth saying that the payload_offset is relative to (setup_sectors
> > +1) * 512?
> 
> The fact that the protected-mode code starts at that address is already 
> mentioned under the heading "LOADING THE REST OF THE KERNEL" (where 
> protected mode is for some reason referred to as "non-real-mode").

I'd missed/forgotten that section, I don't think anything extra is
needed then.

Ian.

-- 
Ian Campbell
Current Noise: Orange Goblin - Made Of Rats

Fatal Error: Found [MS-Windows] System -> Repartitioning Disk for Linux...
(By cbbrown@io.org, Christopher Browne)


  reply	other threads:[~2008-12-15 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 17:50 Philipp Kohlbecher
2008-12-15  9:22 ` Ian Campbell
2008-12-15 11:27   ` Philipp Kohlbecher
2008-12-15 11:34     ` Ian Campbell [this message]
2008-12-15 14:27   ` H. Peter Anvin
2008-12-16 21:06 ` Ingo Molnar

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=1229340862.25349.95.camel@zakaz.uk.xensource.com \
    --to=ijc@hellion.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=xt28@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®