From: Alexander Graf <agraf@suse.de>
To: Aurelien Jarno <aurelien@aurel32.net>, qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] target-s390x: fix CC computation for EX instruction
Date: Mon, 18 May 2015 15:18:01 +0200 [thread overview]
Message-ID: <5559E689.8070401@suse.de> (raw)
In-Reply-To: <1431818883-14944-1-git-send-email-aurelien@aurel32.net>
On 05/17/2015 01:28 AM, Aurelien Jarno wrote:
> Commit 7a6c7067f optimized CC computation by only saving cc_op before
> calling helpers as they either don't touch the CC or generate a new
> static value. This however doesn't work for the EX instruction as the
> helper changes or not the CC value depending on the actual executed
> instruction (e.g. MVC vs CLC).
>
> This patches force a CC computation before calling the helper. This
> fixes random memory corruption occuring in guests.
>
> Cc: Richard Henderson <rth@twiddle.net>
> Cc: Alexander Graf <agraf@suse.de>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Sounds plausible to me, though I'm surprised I didn't run into this
myself yet.
Richard?
Alex
> ---
> target-s390x/translate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target-s390x/translate.c b/target-s390x/translate.c
> index 80e3a54..10522df 100644
> --- a/target-s390x/translate.c
> +++ b/target-s390x/translate.c
> @@ -2095,7 +2095,7 @@ static ExitStatus op_ex(DisasContext *s, DisasOps *o)
> TCGv_i64 tmp;
>
> update_psw_addr(s);
> - update_cc_op(s);
> + gen_op_calc_cc(s);
>
> tmp = tcg_const_i64(s->next_pc);
> gen_helper_ex(cc_op, cpu_env, cc_op, o->in1, o->in2, tmp);
next prev parent reply other threads:[~2015-05-18 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 23:28 [Qemu-devel] [PATCH] target-s390x: fix CC computation for EX instruction Aurelien Jarno
2015-05-18 13:18 ` Alexander Graf [this message]
2015-05-18 15:35 ` Richard Henderson
2015-05-18 17:07 ` Alexander Graf
2015-05-18 17:32 ` Aurelien Jarno
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=5559E689.8070401@suse.de \
--to=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).