From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Nesrine Zouari" <nesrine.zouari@enis.tn>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Lluís Vilanova" <vilanova@ac.upc.edu>
Subject: Re: [Qemu-devel] Qemu Trace
Date: Fri, 2 Feb 2018 15:53:45 +0000 [thread overview]
Message-ID: <CAFEAcA-5PwhJw9epXh+0_oe3E-vsVKkQDX3s1Go-FBzO=FA3zA@mail.gmail.com> (raw)
In-Reply-To: <20180202100843.GD13090@stefanha-x1.localdomain>
On 2 February 2018 at 10:08, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Thu, Feb 01, 2018 at 04:30:10PM +0100, Nesrine Zouari wrote:
>> I am a computer engineering student and I am actually working on my
>> graduation project at Lauterbach company. The project is about Qemu Trace
>> and as a future I would like to contribute this work to the main line.
>>
>> My project is divided into two parts:
>>
>> 1/ Collecting the Guest trace data : The trace solution should be able to
>> provide:
>>
>> a/ Instruction flow Trace
>>
>> b/ Memory read/write access
>>
>> c/ Time Stamps.
>>
>> d/ For tracing rich operating systems that are using MMU, we
>> additionally need to trace the task switches.
>
> Lluìs has done the most instrumentation work in qemu.git and can explain
> the current status.
I think at the moment the status is that we're still discussing
what the trace plugin API should be... there are some mailing
list threads on the subject from I think last year some time.
thanks
-- PMM
next prev parent reply other threads:[~2018-02-02 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 15:30 [Qemu-devel] Qemu Trace Nesrine Zouari
2018-02-01 23:07 ` Dongli Zhang
2018-02-02 10:08 ` Stefan Hajnoczi
2018-02-02 10:45 ` Nesrine Zouari
2018-02-02 15:53 ` Peter Maydell [this message]
2018-02-05 15:51 ` Stefan Hajnoczi
2018-02-05 15:55 ` Peter Maydell
2018-02-06 9:17 ` Stefan Hajnoczi
2018-02-06 10:55 ` Peter Maydell
2018-02-06 15:44 ` Stefan Hajnoczi
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='CAFEAcA-5PwhJw9epXh+0_oe3E-vsVKkQDX3s1Go-FBzO=FA3zA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=nesrine.zouari@enis.tn \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vilanova@ac.upc.edu \
/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).