mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryan Wang <openspace.wang@gmail.com>
To: Neependra Khare <neependra.khare@gmail.com>
Cc: Steven Rostedt <srostedt@redhat.com>,
	linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: When and how to use ftrace?
Date: Wed, 9 Jun 2010 16:14:42 +0800	[thread overview]
Message-ID: <AANLkTimkJjZ32kIl4rjikZqBrFCFPw0zCS7b9uh6gO2V@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik4kdjh1Wmo704_3-jzxmMUd8vGce9Mdojveml1@mail.gmail.com>

2010/6/9 Neependra Khare <neependra.khare@gmail.com>:
>
>
> On Wed, Jun 9, 2010 at 11:02 AM, Ryan Wang <openspace.wang@gmail.com> wrote:
>>
>> I really want to know is the differences between ftrace and other kernel
>> debug
>> tools such as kdump, kdb, etc.
>
> Lets say you want to know what ext2/ext3/ext4 functions are called when you
> run mkdir command on ext2/ext3/ext4 mounted filesystem. Then you can trace
> each kernel function with ftrace.
>
> Articles on ftrace:-
> http://lwn.net/Articles/365835/
> http://lwn.net/Articles/366796/
>
> With kdump you get memory dump of currently running kernel and then you
> debug it.
> kdb will help you to debug the currently running kernel.
>
> I hope this clears some of your doubts.
>
> Regards,
> Neependra
>
>>
>> thanks!
>>
>> --
>> To unsubscribe from this list: send an email with
>> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
>> Please read the FAQ at http://kernelnewbies.org/FAQ
>>
>
>

Seems ftrace is helpful to study the activities inside the kernel to me.
I wonder whether it can be useful to debug kernel bugs. And if so, will
you please give me some examples? Or so far it's mainly used for
observing the running status of kernel?

thanks,

  parent reply	other threads:[~2010-06-09  8:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  1:38 Ryan Wang
2010-06-09  2:42 ` Steven Rostedt
2010-06-09  5:32   ` Ryan Wang
     [not found]     ` <AANLkTik4kdjh1Wmo704_3-jzxmMUd8vGce9Mdojveml1@mail.gmail.com>
2010-06-09  8:14       ` Ryan Wang [this message]
2010-06-09  8:59         ` wu zhangjin
2010-06-09  9:22           ` Ryan Wang

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=AANLkTimkJjZ32kIl4rjikZqBrFCFPw0zCS7b9uh6gO2V@mail.gmail.com \
    --to=openspace.wang@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neependra.khare@gmail.com \
    --cc=srostedt@redhat.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

all inboxes | Powered by JetHome®