From: Sergey Smolov <smolov@ispras.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MIPS 'move' insn emulation
Date: Wed, 13 Sep 2017 10:29:30 +0300 [thread overview]
Message-ID: <59B8DE5A.9000301@ispras.ru> (raw)
In-Reply-To: <CAFEAcA97i97_aoq8xNKtP8Z+i-u5Hq+_e6N80=T=WspSEW+A7A@mail.gmail.com>
On 12.09.2017 18:06, Peter Maydell wrote:
> On 12 September 2017 at 15:53, Sergey Smolov <smolov@ispras.ru> wrote:
>> Generally speaking, is it possible at "run time" to detect write accesses to
>> MIPS GPR registers?
>> If true, which parts of code should I look in?
> We don't currently support tracing at that level, I'm afraid.
> (There are some patches on list starting to explore providing
> an API for doing this kind of instrumentation, but they're
> still at the "working out a design" stage.)
> You might want to look at the -d options, which can give
> you register dumps before every executed instruction if
> you pick the right set of options (-d exec,cpu,nochain
> -singlestep is probably a start.)
>
> thanks
> -- PMM
-d options are a bit high-level for me, because I just see the execution
result for every instruction. So it will be a mistake to think that
every change of some register's value is just a new value writing.
As I understand, at "translate time" QEMU creates a TCG model that can
be run as x86 code on the host machine. May be it is possible to find
some mapping in this model between x86 and MIPS registers? Having such a
mapping, one can detect that some value has been written in a x86
register that conforms to some GPR MIPS register. Am I right?
--
Sincerely yours,
Sergey Smolov
next prev parent reply other threads:[~2017-09-13 7:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 14:14 [Qemu-devel] MIPS 'move' insn emulation Sergey Smolov
2017-09-12 14:32 ` Peter Maydell
2017-09-12 14:53 ` Sergey Smolov
2017-09-12 15:06 ` Peter Maydell
2017-09-13 7:29 ` Sergey Smolov [this message]
2017-09-13 11:01 ` Peter Maydell
2017-09-13 14:20 ` Yongbok Kim
2017-09-14 13:49 ` Sergey Smolov
2017-09-14 13:58 ` Peter Maydell
2017-09-14 14:16 ` Sergey Smolov
2017-09-14 14:23 ` Yongbok Kim
2017-09-14 14:29 ` Peter Maydell
2017-09-14 16:32 ` Sergey Smolov
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=59B8DE5A.9000301@ispras.ru \
--to=smolov@ispras.ru \
--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 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.