qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chen Yufei <cyfdecyf@gmail.com>
To: Yue Chen <ycyc321@gmail.com>,
	Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to trace all the guest OS instructions and the micro-ops
Date: Mon, 12 Mar 2012 14:20:51 +0800	[thread overview]
Message-ID: <CAAoCq2sjFL7v8oivd9_onxBHS9guH+yirt9QunqveS5bvQSbpQ@mail.gmail.com> (raw)
In-Reply-To: <CAGdaadbceNALzxLw6SR1Cv5GhokSr1RkQUacBzX7arXUSccEoA@mail.gmail.com>

On Mon, Mar 12, 2012 at 5:43 AM, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> Hi....
>
> On Sun, Mar 11, 2012 at 10:12, Yue Chen <ycyc321@gmail.com> wrote:
>> I am doing some research based on the QEMU. Does anyone know how to get
>> (trace) all the instructions of the guest OS, and get all the intermediate
>> micro-ops ?  (Not in the 0.9.1 version)

QEMU has release version 1.0.1. Why are you still using 0.9.1?

>
> I believe it's "-d" option you're looking for. Please read qemu manual
> for further clarification and info.

"-d" can only give a static view of what instruction is translated,
but can't get a dynamic instruction execution trace.

>
>> Additionally, how to get the whole memory or each process' memory data of
>> the guest OS?
>
> you wanna do that simply from Qemu's monitor? I don't think that's
> doable...or at least easily. Qemu sees guest RAM like your physical
> RAM. It doesn't differentiate which pages belongs to which process.
> You need to hook or go straight inside the guest OS, maybe using gdb
> or other tool to get the core dump of those processes.
>
>> I really appreciate your help.
>
> Hope it helps...
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>



-- 
Best regards,
Chen Yufei

  reply	other threads:[~2012-03-12  6:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11  3:12 [Qemu-devel] How to trace all the guest OS instructions and the micro-ops Yue Chen
2012-03-11 21:43 ` Mulyadi Santosa
2012-03-12  6:20   ` Chen Yufei [this message]
2012-03-12  6:33     ` Yue Chen
2012-03-12 16:42       ` Lluís Vilanova

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=CAAoCq2sjFL7v8oivd9_onxBHS9guH+yirt9QunqveS5bvQSbpQ@mail.gmail.com \
    --to=cyfdecyf@gmail.com \
    --cc=mulyadi.santosa@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ycyc321@gmail.com \
    /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).