[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A KernelShark plugin for Xen traces analysis
- To: Dario Faggioli <dfaggioli@xxxxxxxx>, Giuseppe Eletto <giuseppe.eletto@xxxxxxxxxxxx>, <linux-trace-devel@xxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
- Date: Wed, 14 Apr 2021 19:11:19 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vcZrNqJ9VmDj+8l2zxe5KkNojdJrNbMiA4zbm83u8lo=; b=CMCSjx4NGw3+4NOsQ/c4t6SMvh0ELhx9/4eegHP8Z+lg3yJKlFbHR1XiIUiUvgZv2w9EhiLGsoVf2u9fJUeVQONMdp6fZTrfPUeSSw5Jy9XePwj+p25yWUA3mjgHVdxoMCgZZEs/kVaCwoXzstPsqpwD06E9+jasXge7p2sC+z2sCUa++uVaZLPPGcLEp4N77wRhk2r0IyHpLNfy1uNL7R8BbwIcwWrfk6dcVL4xe7hxk5vxlpIrhQguRtEw94ijWUvBXWZ7JddzpYYerWB4HksLohwfBrxbgVe4AojOCuyjOX76ss9mSt6PaGQqQoVEk9BVQ9I81dP4pwcBPpMjQA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FZEStFxAinZbUmLcL0MSdpoeb0pNmKWLihrDGmV4BUacFyJBkVcQlxdhipUkETLdzRWZ5AREV3MuMe6qq1xzk7Hx0Go7z94aSTjnke9EaQM+QLwXwPHEpGQU/lcDs7FgXXkyTwlkd64CPAG01ZtZ0gCquSt+HpTBnrbhq4BumRb5Bs3GZAo3c3HHNPc9xhUSqJ39IhqmcaZ+18B1WF4tk3jxWAUFGLVEhDTKH6k5AZp6SJO2tJGNbkgU+mcuEGrF/fbo6TOlIXyzmnJPMbN6v7xYAtsSDuS3wpE+JUKLVhP6doGru58Ohd+roo65PBnc+12bT2WtAIYRbquRitey1w==
- Authentication-results: esa1.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
- Cc: Enrico Bini <enrico.bini@xxxxxxxx>
- Delivery-date: Wed, 14 Apr 2021 18:11:38 +0000
- Ironport-hdrordr: A9a23:Ik6NZ6G80ayqPVPkpLqFOpHXdLJzesId70hD6mlYVQFVfsuEl8 qngfQc0lvOhCwMXWw78OrsBICrSxrnlaJdy48XILukQU3aqHKlRbsSibfK7h/BP2nF9uBb3b p9aKQWMrfNJHVzkMqS2maFOvk6xt3vys6VrMP/61socg1wcaFn6G5Ce2OmO2l7XhNPC5Z8NL f03LslmxOadX4abtu2CxA+NoCum/TxmI/7ehlDPhY76WC15g+A0qLwEBSTw34lIlFy6IolmF KlryXJop+Nntv+4R/a2m/V4f1t6abc4+oGPuOgoIw4Lj3tjyyheYhuXaaT1QpF3N2H2RIRv/ Tn5zsmIsRv+1PdF1vF3ifF6k3b/xsFr1/k1FOCjnPoraXCNUwHIvsEv611WF/9ySMbzbZB+Z MO5U21nd5rKCmFuyLH693BR3hR5zGJiEtnq8E/pThiS4cEAYUhy7A3zQduP7orOjn104wjGP kGNrCn2N9mNWmXaH3UpQBUsaWRd0V2Gh+HR34LsdCO3w5Xm2hkz1AZyNZ3pAZ5yK4A
- Ironport-sdr: oUHz8YqNVH+nx6KaOu9U5VhmLgxVuvLZhQ/xAikp8igz/lN3vRNi4wMxyp1FNpjXRuaGV58NQ9 32wQG18t16+zKV/scKftpHcpSneXtdLzk9o41ptIt63lZWkx+15h4AJRNDDbIZ5fsTmDXOrhHM MMN9fDU5Jll7DBO8JrlMbL6vMrlZClRRH88t+bhoj5GeeqGZD/romsT5z9byZ0RFe7ubI+Q8Jb T3Z3wJtXPX2rdUIj/LZipTp3bkc615UfDGbJ1HjlTw4ZBOtAjVon/Mq3K4oVCHPxrSQiDrSkvR Wag=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 14/04/2021 18:31, Dario Faggioli wrote:
> On Tue, 2021-04-13 at 16:33 +0100, Andrew Cooper wrote:
>> On 13/04/2021 15:28, Giuseppe Eletto wrote:
>>> You will need the development version of KernelShark, available
>>> here:
>>> https://git.kernel.org/pub/scm/utils/trace-cmd/kernel-shark.git
>>>
>>> A screenshot of the plugin in action is available here:
>>> https://github.com/giuseppe998e/kernelshark-xentrace-plugin/raw/master/.github/img/ks-xentrace.png
>>>
>>> I'm happy to receive whatever feedback you may have about it,
>>> and to answer any question.
>> Very nice.
>>
>> 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.
>> For the screenshot, there are a lot of examples where you have a
>> dom:vcpu pair, and a number rendered in hex. Throughout the
>> hypervisor,
>> we're standardising on d$v$ as a format, and e.g. d[IDLE]v$ for some
>> of
>> the magic domid's (0x7ff0 ... 0x7fff).
>>
> Yes, the content of the "info" column is currently a bit "raw". I
> believe it should be made more similar to what `xenalyze --dump-all`
> looks like, rather than to what xentrace_format` does (just to make and
> example that people that have used these two tools can understand).
>
> This is just due to the fact that we wanted to let the Xen and
> KernelShark communities know about this work as soon as Giuseppe got it
> working properly and reliably, to gather any kind of feedback, decide
> where this should live, in the long run, (in Xen? In KS? In its own
> project?), etc. :-)
Where the plugin (ought to) live depends heavily on whether we consider
the trace format a stable ABI or not.
~Andrew
|
