From: Tamas K Lengyel <tamas@tklengyel.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Tamas K Lengyel <tamas@tklengyel.com>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH v5 3/4] x86/mem_sharing: enable mem_share audit mode only in debug builds
Date: Thu, 16 May 2019 15:37:51 -0600 [thread overview]
Message-ID: <20190516213752.1701-3-tamas@tklengyel.com> (raw)
Message-ID: <20190516213751.u2YQ96z0Oo_pUw1-fft7OzJi9oazj2E54l5EcLvPI8U@z> (raw)
In-Reply-To: <20190516213752.1701-1-tamas@tklengyel.com>
Improves performance for release builds.
Signed-off-by: Tamas K Lengyel <tamas@tklengyel.com>
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>
Cc: Roger Pau Monne <roger.pau@citrix.com>
---
xen/include/asm-x86/mem_sharing.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/xen/include/asm-x86/mem_sharing.h b/xen/include/asm-x86/mem_sharing.h
index 9f9f7e93e3..afd0c17292 100644
--- a/xen/include/asm-x86/mem_sharing.h
+++ b/xen/include/asm-x86/mem_sharing.h
@@ -25,7 +25,11 @@
#include <public/memory.h>
/* Auditing of memory sharing code? */
+#ifndef NDEBUG
#define MEM_SHARING_AUDIT 1
+#else
+#define MEM_SHARING_AUDIT 0
+#endif
typedef uint64_t shr_handle_t;
--
2.20.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-16 21:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 21:37 [PATCH v5 1/4] x86/mem_sharing: reorder when pages are unlocked and released Tamas K Lengyel
2019-05-16 21:37 ` [Xen-devel] " Tamas K Lengyel
2019-05-16 21:37 ` [PATCH v5 2/4] x86/mem_sharing: copy a page_lock version to be internal to memshr Tamas K Lengyel
2019-05-16 21:37 ` [Xen-devel] " Tamas K Lengyel
2019-05-17 7:21 ` Jan Beulich
2019-05-17 7:21 ` [Xen-devel] " Jan Beulich
2019-05-17 20:04 ` Tamas K Lengyel
2019-05-17 20:04 ` [Xen-devel] " Tamas K Lengyel
2019-06-17 12:21 ` Tamas K Lengyel
2019-05-16 21:37 ` Tamas K Lengyel [this message]
2019-05-16 21:37 ` [Xen-devel] [PATCH v5 3/4] x86/mem_sharing: enable mem_share audit mode only in debug builds Tamas K Lengyel
2019-06-17 12:24 ` Tamas K Lengyel
2019-05-16 21:37 ` [PATCH v5 4/4] x86/mem_sharing: compile mem_sharing subsystem only when kconfig is enabled Tamas K Lengyel
2019-05-16 21:37 ` [Xen-devel] " Tamas K Lengyel
2019-05-17 7:23 ` Jan Beulich
2019-05-17 7:23 ` [Xen-devel] " Jan Beulich
2019-06-03 8:26 ` Jan Beulich
2019-06-03 8:26 ` [Xen-devel] " Jan Beulich
2019-06-03 16:38 ` Tamas K Lengyel
2019-06-03 16:38 ` [Xen-devel] " Tamas K Lengyel
2019-06-03 16:40 ` Julien Grall
2019-06-03 16:40 ` [Xen-devel] " Julien Grall
2019-06-03 16:55 ` Tamas K Lengyel
2019-06-03 16:55 ` [Xen-devel] " Tamas K Lengyel
2019-06-04 8:41 ` Razvan Cojocaru
2019-06-04 8:41 ` [Xen-devel] " Razvan Cojocaru
2019-06-04 14:36 ` Daniel De Graaf
2019-06-17 12:17 ` Tamas K Lengyel
2019-06-17 12:23 ` [Xen-devel] [PATCH v5 1/4] x86/mem_sharing: reorder when pages are unlocked and released Tamas K Lengyel
2019-06-17 13:46 ` 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=20190516213752.1701-3-tamas@tklengyel.com \
--to=tamas@tklengyel.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@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).