From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: [PATCH v2 0/6] Remove dependency on __LINE__
Date: Wed, 8 Mar 2017 17:46:49 +0000 [thread overview]
Message-ID: <1488995215-7647-1-git-send-email-ross.lagerwall@citrix.com> (raw)
Sorry for the long delay since the first version of this series
(previously called "Make building xSplice patches easier"). Here is a
set of changes that remove the use of __LINE__ when building with NDEBUG
and LivePatch enabled. Tested to boot on x86. Compile-tested on arm.
Changes in v2:
* Renamed xSplice to LivePatch.
* Dropped the patches for the page_alloc.c and the ACPI code as these
only changed __init functions which are not relevant for LivePatch.
* Dropped the patch to rename sections as it is not clear that is is
useful.
* Add a couple of new patches for uses of __LINE__ that have been
introduced since the last version of this series.
See the patches for further changes on each patch.
Ross Lagerwall (6):
lib: Add a generic implementation of current_text_addr()
sched: Remove dependency on __LINE__ for release builds
mm: Use statically defined locking order
iommu: Remove dependency on __LINE__ for release builds
x86_emulate: Remove dependency on __LINE__ for release builds
xen/arm: Remove dependency on __LINE__ for release builds
xen/arch/arm/traps.c | 20 +++++++++++++++++---
xen/arch/x86/mm/mm-locks.h | 28 +++++++++++++++++++---------
xen/arch/x86/x86_emulate/x86_emulate.c | 20 +++++++++++++++++---
xen/common/lib.c | 12 ++++++++++++
xen/drivers/passthrough/vtd/dmar.h | 16 ++++++++++++++--
xen/include/asm-x86/processor.h | 10 ----------
xen/include/xen/lib.h | 2 ++
xen/include/xen/sched.h | 22 +++++++++++++++-------
8 files changed, 96 insertions(+), 34 deletions(-)
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-03-08 17:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 17:46 Ross Lagerwall [this message]
2017-03-08 17:46 ` [PATCH v2 1/6] lib: Add a generic implementation of current_text_addr() Ross Lagerwall
2017-03-09 8:52 ` Dario Faggioli
2017-03-09 10:29 ` Jan Beulich
2017-03-08 17:46 ` [PATCH v2 2/6] sched: Remove dependency on __LINE__ for release builds Ross Lagerwall
2017-03-09 9:03 ` Dario Faggioli
2017-03-08 17:46 ` [PATCH v2 3/6] mm: Use statically defined locking order Ross Lagerwall
2017-03-20 13:52 ` George Dunlap
2017-03-08 17:46 ` [PATCH v2 4/6] iommu: Remove dependency on __LINE__ for release builds Ross Lagerwall
2017-03-09 10:42 ` Jan Beulich
2017-03-15 10:07 ` Tian, Kevin
[not found] ` <5940F13702000000000EA4B6@prv-mh.provo.novell.com>
2017-12-07 11:00 ` Jan Beulich
2017-03-08 17:46 ` [PATCH v2 5/6] x86_emulate: " Ross Lagerwall
2017-03-09 10:45 ` Jan Beulich
2017-03-08 17:46 ` [PATCH v2 6/6] xen/arm: " Ross Lagerwall
2017-03-09 10:34 ` [PATCH v2 0/6] Remove dependency on __LINE__ Jan Beulich
2017-03-10 8:29 ` Ross Lagerwall
2017-03-10 8:50 ` Jan Beulich
2017-03-17 8:57 ` Ross Lagerwall
2017-03-17 9:10 ` 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=1488995215-7647-1-git-send-email-ross.lagerwall@citrix.com \
--to=ross.lagerwall@citrix.com \
--cc=cardoe@cardoe.com \
--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 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).