From: Bibo Mao <maobibo@loongson.cn>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [PATCH] include/qemu/bswap.h: using atomic memory load/store for word access
Date: Mon, 17 May 2021 10:53:41 +0800 [thread overview]
Message-ID: <1621220021-17199-1-git-send-email-maobibo@loongson.cn> (raw)
virtio ring buffer has lockless ring buffer scheme. When guest vcpu
reads the memory, qemu io thread may is writing the same address.
It requiires atomic operation in qemu side, __builtin_memcpy may
read byte-by-byte.
This patch uses fix this, however it may bring negative performance
effect on system which does not support hw aligned memory access.
Signed-off-by: Bibo Mao <maobibo@loongson.cn>
---
include/qemu/bswap.h | 34 ++++++++++++----------------------
1 file changed, 12 insertions(+), 22 deletions(-)
diff --git a/include/qemu/bswap.h b/include/qemu/bswap.h
index 2d3bb8b..b914d33 100644
--- a/include/qemu/bswap.h
+++ b/include/qemu/bswap.h
@@ -327,56 +327,46 @@ static inline void stb_p(void *ptr, uint8_t v)
}
/*
- * Any compiler worth its salt will turn these memcpy into native unaligned
- * operations. Thus we don't need to play games with packed attributes, or
- * inline byte-by-byte stores.
- * Some compilation environments (eg some fortify-source implementations)
- * may intercept memcpy() in a way that defeats the compiler optimization,
- * though, so we use __builtin_memcpy() to give ourselves the best chance
- * of good performance.
+ * Some driver using lockless ring buffer like virtio ring requires that
+ * it should be atomic, since guest vcpu thread is reading the memory.
+ * It may bring out negative performance effect for architectures which
+ * do not support hw memory aligned access like mips, if ptr is not word
+ * alignment.
*/
static inline int lduw_he_p(const void *ptr)
{
- uint16_t r;
- __builtin_memcpy(&r, ptr, sizeof(r));
- return r;
+ return *(uint16_t *)ptr;
}
static inline int ldsw_he_p(const void *ptr)
{
- int16_t r;
- __builtin_memcpy(&r, ptr, sizeof(r));
- return r;
+ return *(int16_t *)ptr;
}
static inline void stw_he_p(void *ptr, uint16_t v)
{
- __builtin_memcpy(ptr, &v, sizeof(v));
+ *(uint16_t *)ptr = v;
}
static inline int ldl_he_p(const void *ptr)
{
- int32_t r;
- __builtin_memcpy(&r, ptr, sizeof(r));
- return r;
+ return *(int32_t *)ptr;
}
static inline void stl_he_p(void *ptr, uint32_t v)
{
- __builtin_memcpy(ptr, &v, sizeof(v));
+ *(uint32_t *)ptr = v;
}
static inline uint64_t ldq_he_p(const void *ptr)
{
- uint64_t r;
- __builtin_memcpy(&r, ptr, sizeof(r));
- return r;
+ return *(uint64_t *)ptr;
}
static inline void stq_he_p(void *ptr, uint64_t v)
{
- __builtin_memcpy(ptr, &v, sizeof(v));
+ *(uint64_t *)ptr = v;
}
static inline int lduw_le_p(const void *ptr)
--
1.8.3.1
next reply other threads:[~2021-05-17 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 2:53 Bibo Mao [this message]
2021-05-17 9:23 ` [PATCH] include/qemu/bswap.h: using atomic memory load/store for word access Peter Maydell
2021-05-17 13:40 ` maobibo
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=1621220021-17199-1-git-send-email-maobibo@loongson.cn \
--to=maobibo@loongson.cn \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).