 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] systemtap probe points for Xen hypervisor
| To: | systemtap@xxxxxxxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] systemtap probe points for Xen hypervisor |
| From: | "Peter Teoh" <htmldeveloper@xxxxxxxxx> |
| Date: | Tue, 22 Apr 2008 09:04:45 +0800 |
| Delivery-date: | Mon, 21 Apr 2008 18:05:13 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=YfXylHGLDLWX2wb9GUslNZ2Kj3hvBgK/rrzJPzOjq+M=; b=wK5ASNTW6ayk0aO1lIB7oQ9puSkfUxvPfjnlt49s8nWja214eLXJ22XbMluKy6/r2lYYggPdAbfwY8looX410BdnDvdaB93CJA57x2Qdx15XWPwObrkTpZE6hAwoz260CDaECHGM+VBejMeRVKE/WD6TT0ndzSFbPrz5LHTDdf0= |
| 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= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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. -- Regards, Peter Teoh _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-ia64-devel] [IA64] Weekly benchmark results [ww15], KUWAMURA Shin'ya |
|---|---|
| Next by Date: | [Xen-devel] VMX status report. Xen: #17461 & Xen0: #522 -- no new issue, Li, Haicheng |
| Previous by Thread: | [Xen-ia64-devel] [IA64] Weekly benchmark results [ww15], KUWAMURA Shin'ya |
| Next by Thread: | [Xen-devel] Re: systemtap probe points for Xen hypervisor, Peter Teoh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
