From: "Hou Wenlong" <houwenlong.hwl@antgroup.com>
To: linux-kernel@vger.kernel.org
Cc: "Hou Wenlong" <houwenlong.hwl@antgroup.com>,
"Andy Shevchenko" <andy@infradead.org>,
"Borislav Petkov" <bp@alien8.de>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Darren Hart" <dvhart@infradead.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Juergen Gross" <jgross@suse.com>,
<platform-driver-x86@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>, <x86@kernel.org>,
<xen-devel@lists.xenproject.org>
Subject: [PATCH 0/2] x86/xen/pvh: Clean up stack canary setup in PVH entry
Date: Mon, 23 Oct 2023 17:09:37 +0800 [thread overview]
Message-ID: <cover.1698051454.git.houwenlong.hwl@antgroup.com> (raw)
Clean up the stack canary setup in the PVH entry. For a 64-bit kernel,
use fixed_percpu_data to set up GSBASE. For a 32-bit kernel, set up the
%fs register explicitly.
Hou Wenlong (2):
x86/xen/pvh: Set up percpu for stack canary in 32-bit kernel entry
x86/xen/pvh: Use fixed_percpu_data to set up GS base
arch/x86/platform/pvh/head.S | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
base-commit: 50dcc2e0d62e3c4a54f39673c4dc3dcde7c74d52
--
2.31.1
next reply other threads:[~2023-10-23 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 9:09 Hou Wenlong [this message]
2023-10-23 9:09 ` [PATCH 1/2] x86/xen/pvh: Set up percpu for stack canary in 32-bit kernel entry Hou Wenlong
2023-10-23 12:02 ` Andy Shevchenko
2023-10-24 2:33 ` Hou Wenlong
2023-10-23 9:09 ` [PATCH 2/2] x86/xen/pvh: Use fixed_percpu_data to set up GS base Hou Wenlong
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.1698051454.git.houwenlong.hwl@antgroup.com \
--to=houwenlong.hwl@antgroup.com \
--cc=andy@infradead.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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.