From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xenproject.org, konrad@kernel.org,
ross.lagerwall@citrix.com
Cc: andrew.cooper3@citrix.com
Subject: [PATCH v5] Livepatch fixes and general features for Xen 4.8.
Date: Sun, 11 Sep 2016 11:48:28 -0400 [thread overview]
Message-ID: <1473608912-5913-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey!
Since v4: [https://lists.xenproject.org/archives/html/xen-devel/2016-08/msg02705.html]
- Committed Acked/Reviewed patches.
- Discarded couple of patches to address later.
Since v3: [https://lists.xen.org/archives/html/xen-devel/2016-08/msg01825.html]
- Acked on reviews
v2, v1:
- Left over fixes and features that didn't get quite done in 4.7
Included are:
- Bug-fixes
- NOP patching
The first two deal with .bss and replace the "livepatch: Clear .bss when
payload is reverted" which was posted in v4:
[PATCH v5 1/4] livepatch/docs: Document .bss not being cleared, and
[PATCH v5 2/4] livepatch: Add limit of 2MB to payload .bss sections.
The NOP patching mechanism is updated per Jan's thinking:
[PATCH v5 3/4] livepatch: NOP if func->new_addr is zero.
And the last one was slighty changed since the Review done in v4 (ditched
the BUG_ON test-case as .bss can have old values) so will need one more review.
[PATCH v5 4/4] livepach: Add .livepatch.hooks functions and test-case
Thanks!
The git tree `
git://xenbits.xen.org/people/konradwilk/xen.git livepatch.v4.8.v5
contains all the following patches (and more):
Konrad Rzeszutek Wilk (3):
livepatch/docs: Document .bss not being cleared, and .data potentially having changed values
livepatch: Add limit of 2MB to payload .bss sections.
livepatch: NOP if func->new_addr is zero.
Ross Lagerwall (1):
livepach: Add .livepatch.hooks functions and test-case
docs/misc/livepatch.markdown | 36 +++++++++++++++++++++++--
xen/arch/x86/alternative.c | 2 +-
xen/arch/x86/livepatch.c | 38 +++++++++++++++++---------
xen/arch/x86/test/xen_hello_world.c | 30 +++++++++++++++++++++
xen/common/livepatch.c | 53 +++++++++++++++++++++++++++++++++++--
xen/common/livepatch_elf.c | 10 ++++++-
xen/include/asm-x86/alternative.h | 1 +
xen/include/asm-x86/livepatch.h | 21 +++++++++++++++
xen/include/xen/livepatch.h | 9 +++++++
xen/include/xen/livepatch_payload.h | 49 ++++++++++++++++++++++++++++++++++
10 files changed, 230 insertions(+), 19 deletions(-)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-09-11 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 15:48 Konrad Rzeszutek Wilk [this message]
2016-09-11 15:48 ` [PATCH v5 1/4] livepatch/docs: Document .bss not being cleared, and .data potentially having changed values Konrad Rzeszutek Wilk
2016-09-12 7:49 ` Jan Beulich
2016-09-13 15:59 ` Konrad Rzeszutek Wilk
2016-09-13 16:12 ` Jan Beulich
2016-09-11 15:48 ` [PATCH v5 2/4] livepatch: Add limit of 2MB to payload .bss sections Konrad Rzeszutek Wilk
2016-09-12 7:56 ` Jan Beulich
2016-09-13 16:04 ` Ross Lagerwall
2016-09-11 15:48 ` [PATCH v5 3/4] livepatch: NOP if func->new_addr is zero Konrad Rzeszutek Wilk
2016-09-12 8:04 ` Jan Beulich
2016-09-11 15:48 ` [PATCH v5 4/4] livepach: Add .livepatch.hooks functions and test-case Konrad Rzeszutek Wilk
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=1473608912-5913-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=konrad@kernel.org \
--cc=ross.lagerwall@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).