From: "Alex Bennée" <alex.bennee@linaro.org>
To: oussema ben khedher <oussemakeder@yahoo.fr>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] adress of translation block
Date: Wed, 01 Mar 2017 11:43:28 +0000 [thread overview]
Message-ID: <8760jt2pen.fsf@linaro.org> (raw)
In-Reply-To: <1174847004.5500748.1488361912027@mail.yahoo.com>
oussema ben khedher <oussemakeder@yahoo.fr> writes:
> hi
> i need help because im really blocked in my educational project
> my problem is i how can i find the adress of the instruction of the end of translation block in qemu (usually it's branch instruction) or the adress of the translation block
> your advice will be very helpful for me .thanks
Rather than continuously spamming the list with the same question you
might find it better to ask on the IRC channel (OFTC/#qemu). While we do
want to help people you can't expect immediate feedback on list
questions, especially when its not clear what you are after.
As to the address of the instruction at the end of the block why do you
need it?
The blocks usually end with a branch taken/not taken so most have 2 exit
points. If you enable -d nochain then the TBs will return to the
run-loop after every basic block executed. With TB chaining in effect
these jumps are directly patched to jump to the next translated block.
Have you read:
http://wiki.qemu-project.org/Documentation/TCG
? These describe how the TCG works and the general code flow.
--
Alex Bennée
prev parent reply other threads:[~2017-03-01 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1174847004.5500748.1488361912027.ref@mail.yahoo.com>
2017-03-01 9:51 ` [Qemu-devel] adress of translation block oussema ben khedher
2017-03-01 11:43 ` Alex Bennée [this message]
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=8760jt2pen.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=oussemakeder@yahoo.fr \
--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).