From: Bjoern Doebel <doebel@amazon.de>
To: <xen-devel@lists.xenproject.org>
Cc: Michael Kurth <mku@amazon.de>,
Martin Pohlack <mpohlack@amazon.de>,
Roger Pau Monne <roger.pau@citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Bjoern Doebel <doebel@amazon.de>
Subject: [PATCH 0/2] Livepatch: support for livepatching CET functions
Date: Mon, 7 Mar 2022 11:53:51 +0000 [thread overview]
Message-ID: <cover.1646653825.git.doebel@amazon.de> (raw)
This series enables support for livepatching functions compiled with
Intel CET support where we have to make sure we leave a potential
leading ENDBR64 instruction intact on livepatch application.
The series also requires a change to generic livepatching code: we need
to make sure that the address of the patched function is known at the
time Xen tries to verify the livepatch for applicability, hence we need
to resolve this address before verifying the patch.
Bjoern Doebel (2):
Livepatch: resolve old address before function verification
xen/x86: Livepatch: support patching CET-enhanced functions
xen/arch/x86/livepatch.c | 63 +++++++++++++++++++++++++++++++++++-----
xen/common/livepatch.c | 4 +--
2 files changed, 57 insertions(+), 10 deletions(-)
--
2.32.0
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next reply other threads:[~2022-03-07 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 11:53 Bjoern Doebel [this message]
2022-03-07 11:53 ` [PATCH 1/2] Livepatch: resolve old address before function verification Bjoern Doebel
2022-03-08 14:33 ` Ross Lagerwall
2022-03-07 11:53 ` [PATCH 2/2] xen/x86: Livepatch: support patching CET-enhanced functions Bjoern Doebel
2022-03-07 14:03 ` Jan Beulich
2022-03-07 14:21 ` David Vrabel
2022-03-07 14:26 ` Jan Beulich
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.1646653825.git.doebel@amazon.de \
--to=doebel@amazon.de \
--cc=Andrew.Cooper3@citrix.com \
--cc=mku@amazon.de \
--cc=mpohlack@amazon.de \
--cc=roger.pau@citrix.com \
--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.