From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <rth@twiddle.net>
Cc: peter.maydell@linaro.org, cota@braap.org, qemu-devel@nongnu.org,
"open list\:ARM" <qemu-arm@nongnu.org>
Subject: Re: [PATCH v3 4/6] target/arm/translate: ensure gen_goto_tb sets exit flags
Date: Tue, 11 Jul 2017 20:20:31 +0100 [thread overview]
Message-ID: <87fue2aigw.fsf@linaro.org> (raw)
In-Reply-To: <d0d0750b-127e-79e8-4307-57e187cd302f@twiddle.net>
Richard Henderson <rth@twiddle.net> writes:
> On 07/11/2017 07:59 AM, Alex Bennée wrote:
>> if (use_goto_tb(s, dest)) {
>> tcg_gen_goto_tb(n);
>> gen_set_pc_im(s, dest);
>> tcg_gen_exit_tb((uintptr_t)s->tb + n);
>> + s->is_jmp = DISAS_TB_JUMP;
>> } else {
>> gen_set_pc_im(s, dest);
>> gen_goto_ptr();
>> + s->is_jmp = DISAS_JUMP;
>> }
>
> I think DISAS_TB_JUMP is appropriate for both cases. When not using
> goto_tb, the jump is still static and we still chain to the next TB
> via goto_ptr.
OK - I guess we need to nail down what the essential difference is
between the two. I understood DISAS_TB_JUMP as a static known PC which
can be patched in the generated code because we know the two addresses
are in the same page - whereas DISAS_JUMP is a "computed" jump although
in this case the PC is already known.
Does making a distinction between computed and non-computer inter-page
jumps make any sense anyway?
>
> Otherwise,
>
> Reviewed-by: Richard Henderson <rth@twiddle.net>
>
>
> r~
--
Alex Bennée
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <rth@twiddle.net>
Cc: peter.maydell@linaro.org, cota@braap.org, qemu-devel@nongnu.org,
"open list:ARM" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 4/6] target/arm/translate: ensure gen_goto_tb sets exit flags
Date: Tue, 11 Jul 2017 20:20:31 +0100 [thread overview]
Message-ID: <87fue2aigw.fsf@linaro.org> (raw)
In-Reply-To: <d0d0750b-127e-79e8-4307-57e187cd302f@twiddle.net>
Richard Henderson <rth@twiddle.net> writes:
> On 07/11/2017 07:59 AM, Alex Bennée wrote:
>> if (use_goto_tb(s, dest)) {
>> tcg_gen_goto_tb(n);
>> gen_set_pc_im(s, dest);
>> tcg_gen_exit_tb((uintptr_t)s->tb + n);
>> + s->is_jmp = DISAS_TB_JUMP;
>> } else {
>> gen_set_pc_im(s, dest);
>> gen_goto_ptr();
>> + s->is_jmp = DISAS_JUMP;
>> }
>
> I think DISAS_TB_JUMP is appropriate for both cases. When not using
> goto_tb, the jump is still static and we still chain to the next TB
> via goto_ptr.
OK - I guess we need to nail down what the essential difference is
between the two. I understood DISAS_TB_JUMP as a static known PC which
can be patched in the generated code because we know the two addresses
are in the same page - whereas DISAS_JUMP is a "computed" jump although
in this case the PC is already known.
Does making a distinction between computed and non-computer inter-page
jumps make any sense anyway?
>
> Otherwise,
>
> Reviewed-by: Richard Henderson <rth@twiddle.net>
>
>
> r~
--
Alex Bennée
next prev parent reply other threads:[~2017-07-11 19:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 17:59 [Qemu-devel] [PATCH v3 0/6] arm: fixes for eret, isb and DISAS_UPDATE handling Alex Bennée
2017-07-11 17:59 ` [Qemu-devel] [PATCH v3 1/6] include/exec/exec-all: document common exit conditions Alex Bennée
2017-07-11 18:17 ` Richard Henderson
2017-07-18 0:02 ` Emilio G. Cota
2017-07-11 17:59 ` [PATCH v3 2/6] target/arm/translate: make DISAS_UPDATE match declared semantics Alex Bennée
2017-07-11 17:59 ` [Qemu-devel] " Alex Bennée
2017-07-18 0:07 ` Emilio G. Cota
2017-07-18 0:07 ` [Qemu-devel] " Emilio G. Cota
2017-07-11 17:59 ` [PATCH v3 3/6] target/arm/translate.h: expand comment on DISAS_EXIT Alex Bennée
2017-07-11 17:59 ` [Qemu-devel] " Alex Bennée
2017-07-18 0:08 ` Emilio G. Cota
2017-07-18 0:08 ` [Qemu-devel] " Emilio G. Cota
2017-07-11 17:59 ` [PATCH v3 4/6] target/arm/translate: ensure gen_goto_tb sets exit flags Alex Bennée
2017-07-11 17:59 ` [Qemu-devel] " Alex Bennée
2017-07-11 18:16 ` Richard Henderson
2017-07-11 18:16 ` [Qemu-devel] " Richard Henderson
2017-07-11 19:20 ` Alex Bennée [this message]
2017-07-11 19:20 ` Alex Bennée
2017-07-11 21:08 ` Richard Henderson
2017-07-11 21:08 ` [Qemu-devel] " Richard Henderson
2017-07-11 17:59 ` [PATCH v3 5/6] target/arm: use gen_goto_tb for ISB handling Alex Bennée
2017-07-11 17:59 ` [Qemu-devel] " Alex Bennée
2017-07-11 18:17 ` Richard Henderson
2017-07-11 18:17 ` [Qemu-devel] " Richard Henderson
2017-07-18 0:11 ` Emilio G. Cota
2017-07-18 0:11 ` [Qemu-devel] " Emilio G. Cota
2017-07-11 17:59 ` [PATCH v3 6/6] target/arm: use DISAS_EXIT for eret handling Alex Bennée
2017-07-11 17:59 ` [Qemu-devel] " Alex Bennée
2017-07-18 0:14 ` Emilio G. Cota
2017-07-18 0:14 ` [Qemu-devel] " Emilio G. Cota
2017-07-11 18:18 ` [Qemu-devel] [PATCH v3 0/6] arm: fixes for eret, isb and DISAS_UPDATE handling Richard Henderson
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=87fue2aigw.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.