diff options
author | David Hildenbrand <david@redhat.com> | 2019-09-03 13:50:49 +0200 |
---|---|---|
committer | David Hildenbrand <david@redhat.com> | 2019-09-23 09:28:29 +0200 |
commit | efb1a76ef9e39b4a5628a27f0f1df74336f8d240 (patch) | |
tree | 95c5c450fc04ff1fe0439685739672466b802d3a /qom | |
parent | b6c636f2cd6c50cdc558e3c02fbc7f2d102955b2 (diff) |
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>
Diffstat (limited to 'qom')
0 files changed, 0 insertions, 0 deletions