From: "Luis R. Rodriguez" <[email protected]>
While at it, also refer to the 32 bit entry file.
Cc: H. Peter Anvin <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Signed-off-by: Luis R. Rodriguez <[email protected]>
---
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
On Mon, Dec 08, 2014 at 02:54:01PM -0800, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <[email protected]>
>
> While at it, also refer to the 32 bit entry file.
>
> Cc: H. Peter Anvin <[email protected]>
> Cc: Borislav Petkov <[email protected]>
> Cc: [email protected]
> Cc: [email protected]
> Cc: [email protected]
> Signed-off-by: Luis R. Rodriguez <[email protected]>
> ---
> 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.
--
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" <[email protected]>
> >
> > While at it, also refer to the 32 bit entry file.
> >
> > Cc: H. Peter Anvin <[email protected]>
> > Cc: Borislav Petkov <[email protected]>
> > Cc: [email protected]
> > Cc: [email protected]
> > Cc: [email protected]
> > Signed-off-by: Luis R. Rodriguez <[email protected]>
> > ---
> > 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