From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51974)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VGQFM-0003rY-FA
	for qemu-devel@nongnu.org; Mon, 02 Sep 2013 05:16:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VGQFA-0005Hp-QU
	for qemu-devel@nongnu.org; Mon, 02 Sep 2013 05:16:32 -0400
Received: from mail-ee0-x22d.google.com ([2a00:1450:4013:c00::22d]:36064)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VGQFA-0005Hh-Jg
	for qemu-devel@nongnu.org; Mon, 02 Sep 2013 05:16:20 -0400
Received: by mail-ee0-f45.google.com with SMTP id c50so2205725eek.4
	for <qemu-devel@nongnu.org>; Mon, 02 Sep 2013 02:16:19 -0700 (PDT)
Date: Mon, 2 Sep 2013 11:16:17 +0200
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20130902091617.GC947@stefanha-thinkpad.redhat.com>
References: <CABhLV00FYY2d=n8LkKi2Y8YKzXZbH+MbRT905K6TY0deJ6e9_g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABhLV00FYY2d=n8LkKi2Y8YKzXZbH+MbRT905K6TY0deJ6e9_g@mail.gmail.com>
Subject: Re: [Qemu-devel] Capture SIGSEGV to track pc.ram page access
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Thomas Knauth <thomas.knauth@gmx.de>
Cc: qemu-devel@nongnu.org

On Sun, Sep 01, 2013 at 11:38:34AM +0200, Thomas Knauth wrote:
> My question is where do I have to touch qemu to call my code for
> handling SIGSEGVs? Is this possible at all? Can anyone suggest
> alternative ways of tracking which pages of pc.ram are accessed?

Maybe you can use the dirty page tracking infrastructure?
memory_global_dirty_log_start()

Stefan