From: "Sorav Bansal" <sbansal@cs.stanford.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] micro-instruction size
Date: Mon, 14 May 2007 09:57:51 -0700 [thread overview]
Message-ID: <21dbb7da0705140957m5ed4ce55r1dd77cbbdf033fb0@mail.gmail.com> (raw)
In-Reply-To: <716704.3494.qm@web32507.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
> I want to instrument call instruction so that my
> tracking function is called on each call instruction.
> >From what I understand, I should
> a) change target-i386/translate.c case 0xe8 to
> generate my own microinstruction, say gen_op_mycall()
> b) Add functionality of op_mycall() to
> target-i386/op.c
> c) Add this new micro-instruction in
> i386-softmmu/opc.h.
>
> Is the above correct?
You only need to perform steps A and B.
Step C is automatically taken care of by dyngen.c.
Similarly, the copy_size in DEF(s,n,copy_size) is automatically computed.
Sorav
[-- Attachment #2: Type: text/html, Size: 790 bytes --]
prev parent reply other threads:[~2007-05-14 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 16:46 [Qemu-devel] micro-instruction size divya arora
2007-05-14 16:57 ` Sorav Bansal [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=21dbb7da0705140957m5ed4ce55r1dd77cbbdf033fb0@mail.gmail.com \
--to=sbansal@cs.stanford.edu \
--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).