public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Arthur Chunqi Li <yzt356@gmail.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: How to trace every memory access
Date: Wed, 20 Nov 2013 11:41:16 +0100	[thread overview]
Message-ID: <528C91CC.5090106@redhat.com> (raw)
In-Reply-To: <CABpY8MJUWdKLwi-0A9290PHU1TSm=XzRWerUMzMdZBjOXk4TOA@mail.gmail.com>

Il 20/11/2013 08:55, Arthur Chunqi Li ha scritto:
> Hi Paolo,
> 
> Currently I can trap every first write/read to a memory page from
> guest VM (add codes in tdp_page_fault). If I want to trace every
> memory access to a page, how can I achieve such goal in KVM?

You don't. :)

If you are looking for something like this, a dynamic recompilation
engine (such as QEMU's TCG) probably ends up being faster.

Paolo

  reply	other threads:[~2013-11-20 10:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20  7:55 How to trace every memory access Arthur Chunqi Li
2013-11-20 10:41 ` Paolo Bonzini [this message]
2013-12-20  9:15   ` Arthur Chunqi Li
2013-12-20 11:58     ` Paolo Bonzini
2013-12-20 14:02       ` Arthur Chunqi Li
2013-12-21  7:25       ` Arthur Chunqi Li

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=528C91CC.5090106@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=yzt356@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