From: Alexander van Heukelum <heukelum@fastmail.fm>
To: Andy Lutomirski <luto@amacapital.net>,
x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Oleg Nesterov <oleg@redhat.com>, Borislav Petkov <bp@suse.de>,
Rik van Riel <riel@redhat.com>
Subject: [PATCH 0/3] x86_64, entry: some cleanup and simplification...
Date: Sun, 18 Jan 2015 02:17:39 +0100 [thread overview]
Message-ID: <1421543862-3552-1-git-send-email-heukelum@fastmail.fm> (raw)
Hi Andy,
Seems you are the person to talk now :). Good to see some activity in
the "entry" area of the kernel. I found some (very) old patches in this
area lying around and some time to dust them off.
Any chance you can review them?
They were redone on top of 22f2aa4a0361707a5cfb1de9d45260b39965dead
(x86/entry-devel in your tree) and this kernel is now running happily
on my laptop. I didn't try any benchmarking, though.
Greetings,
Alexander
Alexander van Heukelum (3):
x86_64: remove KERNEL_STACK_OFFSET from THREAD_INFO macro
x86_64: don't use KERNEL_STACK_OFFSET for syscall and sysenter
x86_64, entry: Create IRET-compatible stack frame at syscall entry
arch/x86/ia32/ia32entry.S | 34 ++++++++--------
arch/x86/include/asm/calling.h | 1 +
arch/x86/include/asm/thread_info.h | 8 ++--
arch/x86/kernel/cpu/common.c | 2 +-
arch/x86/kernel/entry_64.S | 82 ++++++++++++--------------------------
arch/x86/kernel/process_64.c | 3 +-
arch/x86/kernel/smpboot.c | 3 +-
arch/x86/xen/smp.c | 3 +-
8 files changed, 50 insertions(+), 86 deletions(-)
--
2.1.0
next reply other threads:[~2015-01-18 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 1:17 Alexander van Heukelum [this message]
2015-01-18 1:17 ` [PATCH 1/3] x86_64: remove KERNEL_STACK_OFFSET from THREAD_INFO macro Alexander van Heukelum
2015-01-18 1:17 ` [PATCH 2/3] x86_64: don't use KERNEL_STACK_OFFSET for syscall and sysenter Alexander van Heukelum
2015-01-18 1:17 ` [PATCH 3/3] x86_64, entry: Create IRET-compatible stack frame at syscall entry Alexander van Heukelum
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=1421543862-3552-1-git-send-email-heukelum@fastmail.fm \
--to=heukelum@fastmail.fm \
--cc=bp@suse.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=riel@redhat.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
all inboxes | Powered by JetHome®