From: Tim Deegan <tim@xen.org>
To: Razvan Cojocaru <rzvncj@gmail.com>
Cc: jepstein98@gmail.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Mem_event API and MEM_EVENT_REASON_SINGLESTEP
Date: Fri, 30 Nov 2012 21:07:08 +0000 [thread overview]
Message-ID: <20121130210708.GA2013@ocelot.phlegethon.org> (raw)
In-Reply-To: <50B91273.6050606@gmail.com>
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 <mukesh.rathor@oracle.com>)
or tools/xentrace/xenctx.c (which has some code to print registers, read
memory addresses, &c)
Cheers,
Tim.
next prev parent reply other threads:[~2012-11-30 21:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 14:38 Mem_event API and MEM_EVENT_REASON_SINGLESTEP Razvan Cojocaru
2012-11-29 15:18 ` Razvan Cojocaru
2012-11-30 19:50 ` AP
2012-11-30 20:09 ` Razvan Cojocaru
2012-11-30 20:24 ` AP
2012-11-30 20:45 ` Razvan Cojocaru
2012-11-30 20:56 ` AP
2012-11-30 21:04 ` Razvan Cojocaru
2012-11-30 21:17 ` AP
2012-12-04 7:23 ` Razvan Cojocaru
2012-11-30 21:07 ` Tim Deegan [this message]
2012-11-30 21:14 ` Razvan Cojocaru
2012-11-29 15:58 ` Tim Deegan
2012-11-29 16:20 ` Razvan Cojocaru
2012-11-29 18:05 ` Tim Deegan
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=20121130210708.GA2013@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=jepstein98@gmail.com \
--cc=rzvncj@gmail.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.