I added a special opcode, which is not used by existing x86. When the process in the guest issues this opcode, the qemu starts to log its mmu access.
On Mon, Aug 27, 2012 at 11:14 PM, 陳韋任 (Wei-Ren Chen) <che...@iis.sinica.edu.tw> wrote: >> My final goal is to obtain the memory access trace for a particular >> process in the guest, so your patch really helps, except for too many >> kernel _mmu events. > > How do you know guest is running which process, and log it's memory > access trace? > > Regards, > chenwj > > -- > Wei-Ren Chen (陳韋任) > Computer Systems Lab, Institute of Information Science, > Academia Sinica, Taiwan (R.O.C.) > Tel:886-2-2788-3799 #1667 > Homepage: http://people.cs.nctu.edu.tw/~chenwj
