Re: A KernelShark plugin for Xen traces analysis

From: Dario Faggioli <dfaggioli@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Giuseppe Eletto <giuseppe.eletto@edu.unito.it>,
	linux-trace-devel@vger.kernel.org,
	xen-devel@lists.xenproject.org
Cc: Enrico Bini <enrico.bini@unito.it>
Subject: Re: A KernelShark plugin for Xen traces analysis 
Date: Wed, 14 Apr 2021 23:51:31 +0200	[thread overview]
Message-ID: <f99d5176df0298e8057e21f24a627832121b7aa8.camel@suse.com> (raw)
In-Reply-To: <7184a7d7-6bca-4106-d70e-8cf9d5b227fb@citrix.com>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

On Wed, 2021-04-14 at 19:11 +0100, Andrew Cooper wrote:
> On 14/04/2021 18:31, Dario Faggioli wrote:
> > > A couple of questions.  Which Xen libraries do you currently use
> > > map
> > > the
> > > frames?
> > > 
> > Err... If I understood the question none, as the plugin loads and
> > parses a file, as it is produced by `xentrace`. :-)
> > 
> > But maybe I didn't understand the question?
> 
> Ah no - that answer's my question.  I'd blindly assumed that the
> plugin
> was talking directly to Xen to obtain the tracebuffer.
> 
Right. No, KernelShark, for Linux, "just" reads trace-data file
produced by trace-cmd. So we adopted the same model and made it "just"
read a trace-data file, in our case produced by xentrace.

Regards
-- 
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]