Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1537600 > unrolled thread

Enabling trace points during module load/init

Started byChristian König <deathsimple@vodafone.de>
First post2016-12-07 09:30 +0100
Last post2016-12-07 09:30 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  Enabling trace points during module load/init Christian König <deathsimple@vodafone.de> - 2016-12-07 09:30 +0100

#1537600 — Enabling trace points during module load/init

FromChristian König <deathsimple@vodafone.de>
Date2016-12-07 09:30 +0100
SubjectEnabling trace points during module load/init
Message-ID<sLFLX-65b-1@gated-at.bofh.it>
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.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web