public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	linux-doc@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86-64, doc: update to account for file shuffling
Date: Tue, 9 Dec 2014 18:27:09 +0100	[thread overview]
Message-ID: <20141209172709.GC4147@pd.tnic> (raw)
In-Reply-To: <1418079241-4362-1-git-send-email-mcgrof@do-not-panic.com>

On Mon, Dec 08, 2014 at 02:54:01PM -0800, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
> 
> While at it, also refer to the 32 bit entry file.
> 
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-doc@vger.kernel.org
> Cc: x86@kernel.org
> Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
> ---
>  Documentation/x86/entry_64.txt | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/x86/entry_64.txt b/Documentation/x86/entry_64.txt
> index bc7226e..4796392 100644
> --- a/Documentation/x86/entry_64.txt
> +++ b/Documentation/x86/entry_64.txt
> @@ -7,9 +7,11 @@ http://lkml.kernel.org/r/<20110529191055.GC9835%40elte.hu>
>  The x86 architecture has quite a few different ways to jump into
>  kernel code.  Most of these entry points are registered in
>  arch/x86/kernel/traps.c and implemented in arch/x86/kernel/entry_64.S
> -and arch/x86/ia32/ia32entry.S.
> +for 64-bit, arch/x86/kernel/entry_32.S for 32-bit and finally
> +arch/x86/ia32/ia32entry.S which allows to run legacy 32-bit programs
> +under a 64-bit kernel.

Make that "... which implements the 32-bit compatibility syscall entry
points and thus provides for 32-bit processes to execute syscalls when
running on 64-bit kernels."

Or something like that. In any case, a bit more precise sounds better to
me.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-12-09 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 22:54 [PATCH] x86-64, doc: update to account for file shuffling Luis R. Rodriguez
2014-12-09 17:27 ` Borislav Petkov [this message]
2014-12-09 22:51   ` Luis R. Rodriguez

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=20141209172709.GC4147@pd.tnic \
    --to=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mcgrof@suse.com \
    --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