public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] x86-64, doc: update to account for file shuffling
@ 2014-12-08 22:54 Luis R. Rodriguez
  2014-12-09 17:27 ` Borislav Petkov
  0 siblings, 1 reply; 3+ messages in thread
From: Luis R. Rodriguez @ 2014-12-08 22:54 UTC (permalink / raw)
  To: hpa; +Cc: linux-kernel, Luis R. Rodriguez, Borislav Petkov, linux-doc, x86

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.
 
-The IDT vector assignments are listed in arch/x86/include/irq_vectors.h.
+The IDT vector assignments are listed in arch/x86/include/asm/irq_vectors.h.
 
 Some of these entries are:
 
-- 
2.1.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] x86-64, doc: update to account for file shuffling
  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
  2014-12-09 22:51   ` Luis R. Rodriguez
  0 siblings, 1 reply; 3+ messages in thread
From: Borislav Petkov @ 2014-12-09 17:27 UTC (permalink / raw)
  To: Luis R. Rodriguez; +Cc: hpa, linux-kernel, Luis R. Rodriguez, linux-doc, x86

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.
--

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] x86-64, doc: update to account for file shuffling
  2014-12-09 17:27 ` Borislav Petkov
@ 2014-12-09 22:51   ` Luis R. Rodriguez
  0 siblings, 0 replies; 3+ messages in thread
From: Luis R. Rodriguez @ 2014-12-09 22:51 UTC (permalink / raw)
  To: Borislav Petkov; +Cc: Luis R. Rodriguez, hpa, linux-kernel, linux-doc, x86

On Tue, Dec 09, 2014 at 06:27:09PM +0100, Borislav Petkov wrote:
> 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.

OK thanks for the review.

 Luis

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-12-09 22:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2014-12-09 22:51   ` Luis R. Rodriguez

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox