From: Pavel Machek <pavel@ucw.cz>
To: Hui Zhu <zhuhui@xiaomi.com>
Cc: linux-kernel@vger.kernel.org, teawater@gmail.com
Subject: Re: [RFC 0/4] BloodTest: kernel status
Date: Mon, 23 Oct 2017 11:30:00 +0200 [thread overview]
Message-ID: <20171023093000.GE32228@amd> (raw)
In-Reply-To: <1507884965-31476-1-git-send-email-zhuhui@xiaomi.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Hi!
> BloodTest: an interface to call other analysing tools
>
> Linux kernel has a lot of analysing tools, perf, ftrace, systemtap, KGTP
> and so on.
> And kernel also supplies a lot of internal value from procfs and sysfs
> to analyse the performance.
> fs/proc/stat.c | 8
> include/linux/bloodtest.h | 10
> include/linux/kernel_stat.h | 3
> init/Kconfig | 3
> kernel/Makefile | 2
> kernel/bloodtest/Makefile | 3
> kernel/bloodtest/core.c | 132 +++++++++
> kernel/bloodtest/internal.h | 61 ++++
> kernel/bloodtest/kernel_stat.c | 62 ++++
> kernel/bloodtest/pages.c | 266 ++++++++++++++++++
> kernel/bloodtest/perf.c | 576 +++++++++++++++++++++++++++++++++++++++++
> kernel/bloodtest/task.c | 447 +++++++++++++++++++++++++++++++
> kernel/exit.c | 4
> kernel/module.c | 19 +
> 14 files changed, 1592 insertions(+), 4 deletions(-)
No documentation?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-10-23 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 8:56 [RFC 0/4] BloodTest: kernel status Hui Zhu
2017-10-13 8:56 ` [RFC 1/4] " Hui Zhu
2017-10-13 8:56 ` [RFC 2/4] BloodTest: perf Hui Zhu
2017-10-13 8:56 ` [RFC 3/4] module: add /proc/modules_update_version Hui Zhu
2017-10-13 8:56 ` [RFC 4/4] BloodTest: task Hui Zhu
2017-10-23 9:30 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171023093000.GE32228@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=teawater@gmail.com \
--cc=zhuhui@xiaomi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox