Commit 864d5bb9 authored by James C Boyd's avatar James C Boyd Committed by Ingo Molnar

x86/asm/entry/64: Update path names

The paths mentioned in this file weren't updated through some file
rename commits. Fix them to refer to the correct path.
Signed-off-by: default avatarJames C Boyd <jcboyd.dev@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: corbet@lwn.net
Cc: trivial@kernel.org
Link: http://lkml.kernel.org/r/1435781606-3037-1-git-send-email-jcboyd.dev@gmail.comSigned-off-by: default avatarIngo Molnar <mingo@kernel.org>
parent dc5fb575
This file documents some of the kernel entries in This file documents some of the kernel entries in
arch/x86/kernel/entry_64.S. A lot of this explanation is adapted from arch/x86/entry/entry_64.S. A lot of this explanation is adapted from
an email from Ingo Molnar: an email from Ingo Molnar:
http://lkml.kernel.org/r/<20110529191055.GC9835%40elte.hu> http://lkml.kernel.org/r/<20110529191055.GC9835%40elte.hu>
The x86 architecture has quite a few different ways to jump into The x86 architecture has quite a few different ways to jump into
kernel code. Most of these entry points are registered in kernel code. Most of these entry points are registered in
arch/x86/kernel/traps.c and implemented in arch/x86/kernel/entry_64.S arch/x86/kernel/traps.c and implemented in arch/x86/entry/entry_64.S
for 64-bit, arch/x86/kernel/entry_32.S for 32-bit and finally for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
arch/x86/ia32/ia32entry.S which implements the 32-bit compatibility arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
syscall entry points and thus provides for 32-bit processes the syscall entry points and thus provides for 32-bit processes the
ability to execute syscalls when running on 64-bit kernels. ability to execute syscalls when running on 64-bit kernels.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment