From: pierre-marc.fournier@polymtl.ca (Pierre-Marc Fournier)
Subject: [ltt-dev] sys time
Date: Fri, 17 Oct 2008 11:26:53 -0400 [thread overview]
Message-ID: <48F8AEBD.2030303@polymtl.ca> (raw)
In-Reply-To: <8d94e9280810170606o729767f3p839c1c3a59c9565d@mail.gmail.com>
Gian Lorenzo Meocci wrote:
> I want to know if it is possible to obtain this results using lttng trace.
It is definitely possible.
> Actually I made a sum of all differences from a
> kernel_arch_trap_entry/kernel_arch_trap_exit,
> kernel_arch_syscall_entry/exit, kernel_softirq_entry/exit,
> mm_handle_fault_entry/exit, kernel_irq_entry/exit.
You don't need mm_handle_fault_entry/exit because they are always
enclosed within kernel_arch_trap_entry/exit's.
> But for now, my results isn't very good.
- You need to stop counting time when your process is being scheduled
out. See the kernel_sched_schedule events.
- You need to filter the events based on the pid of the process you're
investigating, but I guess you're already doing that.
- If the process is being created inside the trace, you need to start
counting time only after it is created, of course. You could count
syscall time starting at the kernel_process_fork that creates the
process. Also, you need to stop counting time when it's destroyed of course.
- If the process already exists when the trace is started, only consider
events after the list_statedump_end event. Before that, the pid of each
event might not be reliable.
pmf
next prev parent reply other threads:[~2008-10-17 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8d94e9280810170558j5b9ed8d1q7da37da677c7bf7d@mail.gmail.com>
2008-10-17 13:06 ` Gian Lorenzo Meocci
2008-10-17 15:26 ` Pierre-Marc Fournier [this message]
2008-10-17 16:28 ` Mathieu Desnoyers
2008-10-17 16:40 ` Gian Lorenzo Meocci
2008-10-17 17:33 ` Michel Dagenais
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=48F8AEBD.2030303@polymtl.ca \
--to=pierre-marc.fournier@polymtl.ca \
/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