From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32236 invoked by alias); 10 Oct 2011 13:35:58 -0000 Received: (qmail 32195 invoked by uid 22791); 10 Oct 2011 13:35:57 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_QE X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 10 Oct 2011 13:35:40 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9ADZdeh004754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 10 Oct 2011 09:35:39 -0400 Received: from fche.csb (vpn-9-3.rdu.redhat.com [10.11.9.3]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p9ADZcg2007102; Mon, 10 Oct 2011 09:35:39 -0400 Received: by fche.csb (Postfix, from userid 2569) id 38FDA5812E; Mon, 10 Oct 2011 09:35:30 -0400 (EDT) To: "Richard W.M. Jones" Cc: systemtap@sources.redhat.com Subject: Re: Systemtap + tracing processes inside a qemu guest References: <20111010091026.GA15664@amd.home.annexia.org> From: fche@redhat.com (Frank Ch. Eigler) Date: Mon, 10 Oct 2011 13:35:00 -0000 In-Reply-To: <20111010091026.GA15664@amd.home.annexia.org> (Richard W. M. Jones's message of "Mon, 10 Oct 2011 10:10:26 +0100") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q4/txt/msg00031.txt.bz2 "Richard W.M. Jones" writes: > [...] > However to get the complete picture I'd like to > instrument the daemon too. The aim would be to get timing information > across both the host program and the daemon: > > 0.001s program event #1 send message > 0.005s daemon event #1 receive message > 0.010s daemon event #2 send reply > 0.025s program event #2 receive reply > [...] > What's possible at the moment? You're looking for probing two separate systems (the host and the guest) together. The general model does not stretch that far right now (and probably would not be easy to extend it that way). The closest thing would be running separate scripts, one on the host, and one on the guest via --remote, and merging the events together after the fact. - FChE