From: Andy Lutomirski <luto@kernel.org>
To: X86 ML <x86@kernel.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/2] x86_64, xen: Simplify Xen SYSCALL handling
Date: Sun, 26 Jul 2015 16:29:08 -0700 [thread overview]
Message-ID: <cover.1437951794.git.luto@kernel.org> (raw)
Xen's SYSCALL hooks are overcomplicated and add unnecessary places
where RSP is user controlled. Simplify it and get rid of those user
RSP code paths under Xen.
Tested as an Intel KVM guest. Not tested under Xen or on AMD, both
of which are important.
Andy Lutomirski (2):
x86/entry/64: Rearrange SYSCALL entry points for Xen's benefit
x86/xen/64: Rearrange the SYSCALL entries
arch/x86/entry/entry_64.S | 29 +++++++++++++++--------------
arch/x86/entry/entry_64_compat.S | 12 +++++++-----
arch/x86/xen/xen-asm_64.S | 24 ++++++++++--------------
3 files changed, 32 insertions(+), 33 deletions(-)
--
2.4.3
next reply other threads:[~2015-07-26 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 23:29 Andy Lutomirski [this message]
2015-07-26 23:29 ` [PATCH 1/2] x86/entry/64: Rearrange SYSCALL entry points for Xen's benefit Andy Lutomirski
2015-07-26 23:29 ` Andy Lutomirski
2015-07-26 23:29 ` [PATCH 2/2] x86/xen/64: Rearrange the SYSCALL entries Andy Lutomirski
2015-07-26 23:29 ` Andy Lutomirski
-- strict thread matches above, loose matches on Subject: below --
2015-07-26 23:29 [PATCH 0/2] x86_64, xen: Simplify Xen SYSCALL handling Andy Lutomirski
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=cover.1437951794.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.