From: Liang Li <liang.z.li@intel.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, pbonzini@redhat.com,
yang.z.zhang@intel.com, Liang Li <liang.z.li@intel.com>,
quintela@redhat.com
Subject: [Qemu-devel] [PATCH 1/2] cutils: add the AVX2 optimization
Date: Fri, 28 Aug 2015 16:54:12 +0800 [thread overview]
Message-ID: <1440752053-16961-2-git-send-email-liang.z.li@intel.com> (raw)
In-Reply-To: <1440752053-16961-1-git-send-email-liang.z.li@intel.com>
For platform that supports AVX2 instructions, use the AVX2 instructions
instead of SSE2 instructions in buffer_find_nonzero_offset() can help to
improve the performance about 30%. Zero page check during live migration
can be faster with this optimization.
Signed-off-by: Liang Li <liang.z.li@intel.com>
---
include/qemu-common.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/qemu-common.h b/include/qemu-common.h
index bbaffd1..629fcac 100644
--- a/include/qemu-common.h
+++ b/include/qemu-common.h
@@ -468,6 +468,13 @@ void qemu_hexdump(const char *buf, FILE *fp, const char *prefix, size_t size);
/* altivec.h may redefine the bool macro as vector type.
* Reset it to POSIX semantics. */
#define bool _Bool
+#elif defined __AVX2__
+#include <immintrin.h>
+#define VECTYPE __m256i
+#define SPLAT(p) _mm256_set1_epi8(*(p))
+#define ALL_EQ(v1, v2) \
+ (_mm256_movemask_epi8(_mm256_cmpeq_epi8(v1, v2)) == 0xFFFFFFFF)
+#define VEC_OR(v1, v2) (_mm256_or_si256(v1, v2))
#elif defined __SSE2__
#include <emmintrin.h>
#define VECTYPE __m128i
--
1.9.1
next prev parent reply other threads:[~2015-08-28 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 8:54 [Qemu-devel] [PATCH 0/2] Optimization with AVX2 instruction Liang Li
2015-08-28 8:54 ` Liang Li [this message]
2015-08-28 8:54 ` [Qemu-devel] [PATCH 2/2] configure: add --enable-avx2 option Liang Li
2015-09-02 5:40 ` [Qemu-devel] [PATCH 0/2] Optimization with AVX2 instruction Amit Shah
2015-09-06 14:43 ` Paolo Bonzini
2015-09-08 6:16 ` Li, Liang Z
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=1440752053-16961-2-git-send-email-liang.z.li@intel.com \
--to=liang.z.li@intel.com \
--cc=amit.shah@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yang.z.zhang@intel.com \
/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).