From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: Florian Weimer <fweimer@redhat.com>,
Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Stefano Brivio <sbrivio@redhat.com>,
qemu-s390x@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH v1 3/4] s390x/tcg: MOVE (MVC): Increment the length once
Date: Wed, 21 Aug 2019 11:22:51 +0200 [thread overview]
Message-ID: <20190821092252.26541-4-david@redhat.com> (raw)
In-Reply-To: <20190821092252.26541-1-david@redhat.com>
Let's increment the length once.
While at it, cleanup the comment. The memset() example is given as a
programming note in the PoP, so drop the description.
Signed-off-by: David Hildenbrand <david@redhat.com>
---
target/s390x/mem_helper.c | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/target/s390x/mem_helper.c b/target/s390x/mem_helper.c
index 4e9d126e2c..bf7dfcdc7a 100644
--- a/target/s390x/mem_helper.c
+++ b/target/s390x/mem_helper.c
@@ -307,16 +307,20 @@ static uint32_t do_helper_mvc(CPUS390XState *env, uint32_t l, uint64_t dest,
HELPER_LOG("%s l %d dest %" PRIx64 " src %" PRIx64 "\n",
__func__, l, dest, src);
- /* mvc and memmove do not behave the same when areas overlap! */
- /* mvc with source pointing to the byte after the destination is the
- same as memset with the first source byte */
+ /* MVC always copies one more byte than specified - maximum is 256 */
+ l++;
+
+ /*
+ * "When the operands overlap, the result is obtained as if the operands
+ * were processed one byte at a time". Only non-overlapping or forward
+ * moves behave like memmove().
+ */
if (dest == src + 1) {
- fast_memset(env, dest, cpu_ldub_data_ra(env, src, ra), l + 1, ra);
- } else if (dest < src || src + l < dest) {
- fast_memmove(env, dest, src, l + 1, ra);
+ fast_memset(env, dest, cpu_ldub_data_ra(env, src, ra), l, ra);
+ } else if (dest < src || src + l <= dest) {
+ fast_memmove(env, dest, src, l, ra);
} else {
- /* slow version with byte accesses which always work */
- for (i = 0; i <= l; i++) {
+ for (i = 0; i < l; i++) {
uint8_t x = cpu_ldub_data_ra(env, src + i, ra);
cpu_stb_data_ra(env, dest + i, x, ra);
}
--
2.21.0
next prev parent reply other threads:[~2019-08-21 9:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 9:22 [Qemu-devel] [PATCH v1 0/4] s390x/tcg: MOVE (MVC): Fault-safe handling David Hildenbrand
2019-08-21 9:22 ` [Qemu-devel] [PATCH v1 1/4] s390x/tcg: Use guest_addr_valid() instead of h2g_valid() in probe_write_access() David Hildenbrand
2019-08-21 9:22 ` [Qemu-devel] [PATCH v1 2/4] s390x/tcg: Introduce probe_read_access() David Hildenbrand
2019-08-21 17:26 ` Richard Henderson
2019-08-21 17:37 ` David Hildenbrand
2019-08-21 19:19 ` Richard Henderson
2019-08-21 19:36 ` David Hildenbrand
2019-08-21 20:38 ` Richard Henderson
2019-08-21 21:33 ` David Hildenbrand
2019-08-21 22:31 ` Richard Henderson
2019-08-21 22:43 ` Richard Henderson
2019-08-22 6:42 ` David Hildenbrand
2019-08-22 7:01 ` David Hildenbrand
2019-08-26 9:31 ` David Hildenbrand
2019-08-21 18:48 ` David Hildenbrand
2019-08-21 9:22 ` David Hildenbrand [this message]
2019-08-21 15:47 ` [Qemu-devel] [PATCH v1 3/4] s390x/tcg: MOVE (MVC): Increment the length once Richard Henderson
2019-08-21 9:22 ` [Qemu-devel] [PATCH v1 4/4] s390x/tcg: MOVE (MVC): Fault-safe handling David Hildenbrand
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=20190821092252.26541-4-david@redhat.com \
--to=david@redhat.com \
--cc=cohuck@redhat.com \
--cc=fweimer@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=sbrivio@redhat.com \
--cc=thuth@redhat.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).