From: "Alex Bennée" <alex.bennee@linaro.org>
To: Sergey Smolov <smolov@ispras.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] log every write to Aarch64 regs
Date: Wed, 23 Nov 2016 11:26:11 +0000 [thread overview]
Message-ID: <87r362o2ss.fsf@linaro.org> (raw)
In-Reply-To: <58354B12.1050909@ispras.ru>
Sergey Smolov <smolov@ispras.ru> writes:
> Hello, List!
>
> I have a subset of Aarch64 registers and I need to print something to
> QEMU log every time the emulator writes new data to them.
>
> Is this problem fully or partially solvable in QEMU?
>
> What QEMU components should I look inside to implement this?
For local experimentation you can use plain fprintf's or qemu_log. If
you want something more performance orientated you'll want to look at
the tracing infrastructure. See docs/tracing.txt in the source tree.
>
> Thanks in advance!
--
Alex Bennée
next prev parent reply other threads:[~2016-11-23 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 7:53 [Qemu-devel] log every write to Aarch64 regs Sergey Smolov
2016-11-23 11:26 ` Alex Bennée [this message]
2016-11-23 11:28 ` Alex Bennée
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=87r362o2ss.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=smolov@ispras.ru \
/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.