All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Biggs <john.biggs@epfl.ch>
To: Richard Henderson <rth@twiddle.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question about gen_jmp_tb
Date: Mon, 02 Jun 2014 10:16:26 +0200	[thread overview]
Message-ID: <538C32DA.5000809@epfl.ch> (raw)
In-Reply-To: <5388B101.4010809@twiddle.net>

Hi Richard, thanks for your help.

Which instruction, then, I should add my gen_helper to in order for it 
to be called at the end of each basic block, as I've previously stated? 
Is there a way I can generically have this change apply to every target?

Jack

On 05/30/2014 06:25 PM, Richard Henderson wrote:
> On 05/30/2014 01:56 AM, Jack Biggs wrote:
>> Hi all,
>>
>> I'm trying to add some arbitrary code to the end of each translation block, and
>> I wanted to confirm my suspicion that each translation block ends in a jmp
>> instruction, and that each translation block ends (or jumps to another TB) with
>> the call to gen_jmp_tb. My guest is i386, but if this is architecture-specific
>> I'd like to know more about per-target semantics.
> No, not every tb ends with gen_jmp_tb.  Indeed, only those for which we have an
> immediate address end that way.  Plenty of tb's end with indirect branches, or
> for a variety of other reasons.
>
> Certainly gen_jmp_tb is specific to the i386 translator.
>
>
> r~

       reply	other threads:[~2014-06-02  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <538847AC.6040108@epfl.ch>
     [not found] ` <5388B101.4010809@twiddle.net>
2014-06-02  8:16   ` Jack Biggs [this message]
2014-06-02  9:32     ` [Qemu-devel] Question about gen_jmp_tb Alex Bennée
2014-06-02 10:15       ` Jack Biggs
2014-06-02 10:47         ` Peter Maydell
2014-06-02 10:53           ` Jack Biggs
2014-06-02 10:56             ` 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=538C32DA.5000809@epfl.ch \
    --to=john.biggs@epfl.ch \
    --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.