From: Super Man <killpy178@gmail.com>
To: qemu-devel@nongnu.org
Subject: Memory callback
Date: Wed, 8 Jul 2020 21:53:59 +0800 [thread overview]
Message-ID: <CAFB2YPkxtLqyf4Mo4Yx1jovSpwyrHz6TPz1tDZd27mazXNQRWA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
Sorry to bother you, I would like to ask a question.I want to use qemu to
monitor the information of the target thread reading and writing memory. I
see that qemu supports the tcg plugin, but I just find the following code
in plugin-gen.c .Do I just need to add a record function in it? How do I
read the current register values such as rip, rsp, how do I know the
current target address and data that the CPU read or written?Is there any
reference example?
/*
> * These helpers are stubs that get dynamically switched out for calls
> * direct to the plugin if they are subscribed to.
> */
> void HELPER(plugin_vcpu_udata_cb)(uint32_t cpu_index, void *udata)
> { }
> void HELPER(plugin_vcpu_mem_cb)(unsigned int vcpu_index,
> qemu_plugin_meminfo_t info, uint64_t vaddr,
> void *userdata)
> { }
[-- Attachment #2: Type: text/html, Size: 9826 bytes --]
reply other threads:[~2020-07-08 16:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFB2YPkxtLqyf4Mo4Yx1jovSpwyrHz6TPz1tDZd27mazXNQRWA@mail.gmail.com \
--to=killpy178@gmail.com \
--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).