[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] systemtap probe points for Xen hypervisor

  • To: systemtap@xxxxxxxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Peter Teoh" <htmldeveloper@xxxxxxxxx>
  • Date: Tue, 22 Apr 2008 09:04:45 +0800
  • Delivery-date: Mon, 21 Apr 2008 18:05:13 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=O6/ORLub6+evSAGyXCaGBjeP8SG5OXS+7BQXxpawsTmbOpcyAtY2KIVMRJACnTv8LtGzdK8tG/cnVQrS0cjnNZl+5lduqAp5goWdx71JS31V7uPMVOw81UzxyNH+NcZklevLoZ0FHw6frThMWtuxMrb8HK0LekuZf00PHYEBQ6Q=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

How do we probe the Xen hypervisor, while running as the dom0 (which
is the GUI frontend for us, and  running as guest)?   Since the entry
to hypervisor is controlled, I supposed it will need a patch before
systemtap can be used to probe the Xen hypervisor, right?   Or is it
not a logical thing  to do?

My target of interest will be to trace/analyze  the behavior of the
Xen hypervisor, and the domX guest as well.

Thank you for your answer.

Peter Teoh

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.