From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752215AbcLGI2A (ORCPT ); Wed, 7 Dec 2016 03:28:00 -0500 Received: from pegasos-out.vodafone.de ([80.84.1.38]:32786 "EHLO pegasos-out.vodafone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751685AbcLGI17 (ORCPT ); Wed, 7 Dec 2016 03:27:59 -0500 X-Spam-Flag: NO X-Spam-Score: -0.045 Authentication-Results: rohrpostix2.prod.vfnet.de (amavisd-new); dkim=pass header.i=@vodafone.de X-DKIM: OpenDKIM Filter v2.6.8 pegasos-out.vodafone.de 4215C62056F Cc: LKML , Alex Deucher From: =?UTF-8?Q?Christian_K=c3=b6nig?= Subject: Enabling trace points during module load/init To: Steven Rostedt Message-ID: Date: Wed, 7 Dec 2016 09:27:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.