All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Enabling trace points during module load/init
Date: Wed, 7 Dec 2016 09:27:21 +0100	[thread overview]
Message-ID: <ad6fb376-4fa8-3001-8cc9-7e0a41393616@vodafone.de> (raw)

Hi everone,

I'm the co-maintainer of the AMD GFX drivers in the upstream kernel and 
yesterday I ran into the problem that I need to enable some trace points 
during module load/init.

We had that issue quite a bunch of times before, but so far never had 
the time or patience to figure out how to enable this properly. So we 
always ended up adding printk() into our code additionally to the 
existing trace points to figure out what the driver does during startup.

But this time I started to Google a bit and figured out that Steven 
Rostedt already had that issue solved years ago, but never pushed it 
upstream. Asking Steven why the absolutely surprising answer was that it 
was dropped because nobody spoke up and said that this was an useful 
feature.

So here I'm absolutely confirming that this is an useful feature and we 
could really make good use of it. Also feel free to CC me for reviews 
and/or testing.

Best regards,
Christian.

             reply	other threads:[~2016-12-07  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  8:27 Christian König [this message]
2016-12-15 17:37 ` Enabling trace points during module load/init David Howells
2016-12-16 11:55 ` Allow tracepoints to use direct indexing for number->string translation David Howells
2016-12-16 15:02   ` Steven Rostedt
2016-12-16 16:22   ` David Howells
2016-12-16 16:37     ` Steven Rostedt
2016-12-16 16:52     ` David Howells

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=ad6fb376-4fa8-3001-8cc9-7e0a41393616@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=alexander.deucher@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.