From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<hpa@zytor.com>, <corbet@lwn.net>
Subject: Re: [PATCH] Documentation/x86/boot.rst: minor improvement
Date: Tue, 1 Sep 2020 13:25:53 +0800 [thread overview]
Message-ID: <da11d436-8910-f560-e132-827132576f1d@cn.fujitsu.com> (raw)
In-Reply-To: <20200901034157.5482-1-caoj.fnst@cn.fujitsu.com>
Sorry, I mis-copied 2 addresses. make sure they are CCed.
On 9/1/20 11:41 AM, Cao jin wrote:
> Typo fix & file name update
>
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
> Documentation/x86/boot.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/x86/boot.rst b/Documentation/x86/boot.rst
> index 7fafc7ac00d7..c04afec90486 100644
> --- a/Documentation/x86/boot.rst
> +++ b/Documentation/x86/boot.rst
> @@ -1379,7 +1379,7 @@ can be calculated as follows::
> In addition to read/modify/write the setup header of the struct
> boot_params as that of 16-bit boot protocol, the boot loader should
> also fill the additional fields of the struct boot_params as described
> -in zero-page.txt.
> +in zero-page.rst.
>
> After setting up the struct boot_params, the boot loader can load
> 64-bit kernel in the same way as that of 16-bit boot protocol, but
> @@ -1391,7 +1391,7 @@ In 64-bit boot protocol, the kernel is started by jumping to the
>
> At entry, the CPU must be in 64-bit mode with paging enabled.
> The range with setup_header.init_size from start address of loaded
> -kernel and zero page and command line buffer get ident mapping;
> +kernel and zero page and command line buffer get identity mapping;
> a GDT must be loaded with the descriptors for selectors
> __BOOT_CS(0x10) and __BOOT_DS(0x18); both descriptors must be 4G flat
> segment; __BOOT_CS must have execute/read permission, and __BOOT_DS
>
--
Sincerely,
Cao jin
next prev parent reply other threads:[~2020-09-01 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 3:41 Cao jin
2020-09-01 5:25 ` Cao jin [this message]
2020-09-01 5:35 ` H. Peter Anvin
2020-09-01 6:23 ` Cao jin
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=da11d436-8910-f560-e132-827132576f1d@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®