qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
	qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Shifts, ppc[64], xtensa
Date: Wed, 19 Sep 2012 11:35:25 -0700	[thread overview]
Message-ID: <505A106D.8020009@twiddle.net> (raw)
In-Reply-To: <CAFEAcA-Bg+yv5sH1TTm9opHBtVYPJ7Vpn1t9nbwMT8yjEr7ELg@mail.gmail.com>

On 09/19/2012 11:30 AM, Peter Maydell wrote:
> On 19 September 2012 19:01, Richard Henderson <rth@twiddle.net> wrote:
>> On 09/19/2012 10:51 AM, Aurelien Jarno wrote:
>>> That said it is not a valid reason to not keep the value during
>>> re-translation, as it means the TB will exit instead of linking to
>>> the next one. The consequences are only the performance.
>>
>> We still have the problem of when is the goto_tb link initialized the *first* time?
>> Where we expect the goto_tb to fall through to stuff+exit_tb?
>>
>> For i386 it's during translation, with no care for re-translation.
>>
>> For ARM?  I can't see that it is.
> 
> I think the answer to this is that the only caller of cpu_gen_code()
> is tb_gen_code(), which always then calls tb_link_page()
> which calls tb_reset_jump() which calls tb_set_jmp_target().

That looks correct.  If convoluted.  ;-)

>> For PPC, malc has already verified that it *never* happens.  If he
>> puts "trap" insns there instead of "nop" insns, he'll see the trap.
> 
> ...but on the other hand that ought to work for PPC too, so
> presumably my analysis is wrong somewhere.

malc?  Breakpoint on ppc_tb_set_jmp_target?


r~

  reply	other threads:[~2012-09-19 18:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 19:52 [Qemu-devel] Shifts, ppc[64], xtensa malc
2012-09-18 23:20 ` Max Filippov
2012-09-19 12:49   ` malc
2012-09-19 15:00     ` Max Filippov
2012-09-19  0:10 ` Richard Henderson
2012-09-19 12:46   ` malc
2012-09-19 12:57 ` Peter Maydell
2012-09-19 17:00   ` Richard Henderson
2012-09-19 17:02     ` Richard Henderson
2012-09-19 17:11     ` Peter Maydell
2012-09-19 17:30       ` Richard Henderson
2012-09-19 17:51         ` Aurelien Jarno
2012-09-19 18:01           ` Richard Henderson
2012-09-19 18:30             ` Peter Maydell
2012-09-19 18:35               ` Richard Henderson [this message]
2012-09-19 19:53               ` Richard Henderson
2012-09-19 20:05                 ` Peter Maydell
2012-09-19 21:21                   ` Richard Henderson
2012-09-20  0:29                 ` Max Filippov
2012-09-20 14:03                   ` Richard Henderson
2012-09-20 14:22                     ` Max Filippov
2012-09-20 22:53                   ` malc

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=505A106D.8020009@twiddle.net \
    --to=rth@twiddle.net \
    --cc=aurelien@aurel32.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=peter.maydell@linaro.org \
    --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).