From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] target-s390x: fix LOAD MULTIPLE instruction on page boundary
Date: Sat, 23 May 2015 12:33:27 -0700 [thread overview]
Message-ID: <5560D607.7080101@twiddle.net> (raw)
In-Reply-To: <20150523075906.GA25414@aurel32.net>
On 05/23/2015 12:59 AM, Aurelien Jarno wrote:
> On 2015-05-21 14:42, Richard Henderson wrote:
>> Hmm. Seems to be un/under-specified in the PoO. That said,
>
> There is a small sentence in the PoO, in chapter "Program Execution",
> section "Sequence of Storage Reference":
>
> It can normally be assumed that the execution of
> each instruction occurs as an indivisible event.
Ah, I didn't think to look in a different chapter. ;-)
>> It would be nice to know if there ought to be similar up-front access checking
>> for STM, to avoid errant partial stores.
>
> I have just checked, the same is also true for STM instructions, though
> it's probably more difficult to fix that in QEMU. Maybe we need a way to
> check if a load/store will succeed, preferably without using a helper.
I did just suggest a new helper in the "unaligned stores for mips r6" thread.
Therein we provide a probe_write helper that does assert that the given page is
writable, or raise the usual exception. It leaves the TLB updated, so a
subsequent write should take the fast path.
It should be easy enough to extend that with an opcode so that we can implement
this for s390 as
probe_write addr + n * size - 1
qemu_st r0, addr
qemu_st r1, addr + 1*size
...
Hopefully for the edge case where both pages are unmapped, producing an
exception pointing to the last byte, rather than the first byte, is acceptable.
r~
next prev parent reply other threads:[~2015-05-23 19:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 21:32 [Qemu-devel] [PATCH] target-s390x: fix LOAD MULTIPLE instruction on page boundary Aurelien Jarno
2015-05-21 21:42 ` Richard Henderson
2015-05-23 7:59 ` Aurelien Jarno
2015-05-23 19:33 ` Richard Henderson [this message]
2015-05-25 20:47 ` Alexander Graf
2015-05-25 21:04 ` Aurelien Jarno
2015-05-25 21:05 ` Aurelien Jarno
2015-05-25 21:55 ` Alexander Graf
2015-05-26 7:09 ` Peter Maydell
2015-05-26 16:23 ` Richard Henderson
2015-05-21 22:00 ` Alexander Graf
2015-05-23 8:22 ` Aurelien Jarno
2015-05-23 9:26 ` Peter Maydell
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=5560D607.7080101@twiddle.net \
--to=rth@twiddle.net \
--cc=agraf@suse.de \
--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).