From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Deegan Subject: Re: Mem_event API and MEM_EVENT_REASON_SINGLESTEP Date: Fri, 30 Nov 2012 21:07:08 +0000 Message-ID: <20121130210708.GA2013@ocelot.phlegethon.org> References: <50B77375.9070904@gmail.com> <50B77CB8.1040606@gmail.com> <50B91273.6050606@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <50B91273.6050606@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Razvan Cojocaru Cc: jepstein98@gmail.com, "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org At 22:09 +0200 on 30 Nov (1354313363), Razvan Cojocaru wrote: > > After you set single stepping on for a VCPU and resume, you should see > > a single step mem_event soon after. What is the behavior that you are > > observing? Are you trying this on an UP or SMP guest? > > I do see single step mem_events after. I've tried it on a SMP HVM > Slackware guest. What behaviour am I observing? The gla and gfn values > are being printed out - but I don't know how to detect a write operation > based on them. What more do you want to know? The gla tells you what the address is that's being written to. If you want the rest of the register state &c, then have a look at either tools/debugger/gdbsx (a full debugger stub for guests; its maintainer is Mukesh Rathor ) or tools/xentrace/xenctx.c (which has some code to print registers, read memory addresses, &c) Cheers, Tim.