From: Brian Gerst <brgerst@gmail.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Ingo Molnar <mingo@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Brian Gerst <brgerst@gmail.com>
Subject: [PATCH 0/5] x86/entry: Break up common.c
Date: Thu, 13 Mar 2025 14:22:31 -0400 [thread overview]
Message-ID: <20250313182236.655724-1-brgerst@gmail.com> (raw)
The syscall dispatch code originally was put into entry/common.c so that
common code for entry from and exit to userspace could be inlined. That
entry code has since been moved to the core kernel. There is no longer
a need to keep this code together, so move it to more appropriate
places.
This is code reorganization only, no functional changes.
Brian Gerst (5):
x86/xen: Move Xen upcall handler
x86/syscall/32: Move 32-bit syscall dispatch code
x86/syscall/64: Move 64-bit syscall dispatch code
x86/syscall/x32: Move x32 syscall table
x86/syscall: Move sys_ni_syscall()
arch/x86/entry/Makefile | 8 +-
arch/x86/entry/common.c | 524 -----------------------------------
arch/x86/entry/syscall_32.c | 336 +++++++++++++++++++++-
arch/x86/entry/syscall_64.c | 116 +++++++-
arch/x86/entry/syscall_x32.c | 25 --
arch/x86/kernel/process.c | 5 +
arch/x86/xen/enlighten_pv.c | 46 +++
include/xen/xen-ops.h | 19 ++
8 files changed, 522 insertions(+), 557 deletions(-)
delete mode 100644 arch/x86/entry/common.c
delete mode 100644 arch/x86/entry/syscall_x32.c
base-commit: d08c0d55110b7cbac186e5fa94b0c6d5f4d7905e
--
2.48.1
next reply other threads:[~2025-03-13 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 18:22 Brian Gerst [this message]
2025-03-13 18:22 ` [PATCH 1/5] x86/xen: Move Xen upcall handler Brian Gerst
2025-03-14 7:37 ` Juergen Gross
2025-03-14 9:47 ` [tip: x86/cpu] x86/xen: Move Xen upcall handler to Xen specific code files tip-bot2 for Brian Gerst
2025-03-14 9:53 ` Jürgen Groß
2025-03-14 10:08 ` Ingo Molnar
2025-03-14 10:14 ` Jürgen Groß
2025-03-13 18:22 ` [PATCH 2/5] x86/syscall/32: Move 32-bit syscall dispatch code Brian Gerst
2025-03-13 23:44 ` Sohil Mehta
2025-03-14 1:25 ` Brian Gerst
2025-03-14 9:27 ` Ingo Molnar
2025-03-14 9:46 ` [tip: x86/cpu] x86/syscall/32: Move the 32-bit syscall dispatch code to arch/x86/entry/syscall_32.c tip-bot2 for Brian Gerst
2025-03-13 18:22 ` [PATCH 3/5] x86/syscall/64: Move 64-bit syscall dispatch code Brian Gerst
2025-03-14 9:46 ` [tip: x86/cpu] x86/syscall/64: Move the 64-bit syscall dispatch code to arch/x86/entry/syscall_64.c tip-bot2 for Brian Gerst
2025-03-13 18:22 ` [PATCH 4/5] x86/syscall/x32: Move x32 syscall table Brian Gerst
2025-03-13 23:47 ` Sohil Mehta
2025-03-14 9:25 ` Ingo Molnar
2025-03-14 9:34 ` Ingo Molnar
2025-03-14 16:02 ` Sohil Mehta
2025-03-14 9:46 ` [tip: x86/cpu] x86/syscall/x32: Move the x32 syscall table to arch/x86/entry/syscall_64.c tip-bot2 for Brian Gerst
2025-03-13 18:22 ` [PATCH 5/5] x86/syscall: Move sys_ni_syscall() Brian Gerst
2025-03-14 9:46 ` [tip: x86/cpu] x86/syscall: Move sys_ni_syscall() to arch/x86/kernel/process.c tip-bot2 for Brian Gerst
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=20250313182236.655724-1-brgerst@gmail.com \
--to=brgerst@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--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