| commit | efb1a76ef9e39b4a5628a27f0f1df74336f8d240 | |
| author | David Hildenbrand <david@redhat.com> | |
| Tue, 3 Sep 2019 11:50:49 +0000 (3 13:50 +0200) | ||
| committer | David Hildenbrand <david@redhat.com> | |
| Mon, 23 Sep 2019 07:28:29 +0000 (23 09:28 +0200) | ||
| tree | 95c5c450fc04ff1fe0439685739672466b802d3a | treesnapshot (tar.gz zip) |
| parent | b6c636f2cd6c50cdc558e3c02fbc7f2d102955b2 | commitdiff |
s390x/tcg: MVCS/MVCP: Use access_memmove()
As we are moving between address spaces, we can use access_memmove()
without checking for destructive overlaps (especially of real storage
locations):
"Each storage operand is processed left to right. The
storage-operand-consistency rules are the same as
for MOVE (MVC), except that when the operands
overlap in real storage, the use of the common real-
storage locations is not necessarily recognized."
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: David Hildenbrand <david@redhat.com>
As we are moving between address spaces, we can use access_memmove()
without checking for destructive overlaps (especially of real storage
locations):
"Each storage operand is processed left to right. The
storage-operand-consistency rules are the same as
for MOVE (MVC), except that when the operands
overlap in real storage, the use of the common real-
storage locations is not necessarily recognized."
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: David Hildenbrand <david@redhat.com>
| target/s390x/mem_helper.c | diffblobblamehistory |