On Fri, Sep 27, 2013 at 12:50 PM, Stefan Hajnoczi wrote:
> If you want to continue with the original SIGSEGV handler approach,
> check signals masks for the vcpu threads. Make sure the signal actually
> gets delivered to a thread that has the signal unblocked and a signal
> handler installed.
I'
On Thu, Sep 26, 2013 at 02:53:54PM +0200, Thomas Knauth wrote:
> As far as I understand the dirty logging infrastructure will only
> record writes. I want to track reads as well.
>
> A better way to express what I would like to do is trace all guest
> physical addresses that are accessed. Again, I
As far as I understand the dirty logging infrastructure will only
record writes. I want to track reads as well.
A better way to express what I would like to do is trace all guest
physical addresses that are accessed. Again, I am unsure whether qemu
supports this out-of-the box and where I would ha
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 tra
