[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=k5nkUk9LOS=EGHGSq=5Qe8_L-1d3_t9byxMrt@mail.gmail.com>
Date: Mon, 2 Aug 2010 16:53:24 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: Jason Baron <jbaron@...hat.com>
Cc: Greg KH <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, trenn@...e.de
Subject: Re: Boot-time dynamic debugging?
> On Sun, Aug 01, 2010 at 03:10:40PM +0300, Pekka Enberg wrote:
>> Commit 346e15beb5343c2eb8216d820f2ed8f150822b08 ("driver core: basic
>> infrastructure for per-module dynamic debug messages") removed
>> "dynamic_printk" kernel parameter from the dynamic debugging subsystem
>> (and forgot to update Documentation/kernel-parameters.txt). How can I
>> use the new subsystem for enabling boot-time dev_dbg() calls for
>> non-modular kernels?
On Mon, Aug 2, 2010 at 4:47 PM, Jason Baron <jbaron@...hat.com> wrote:
> Right now, you can not enable them dynamically from the boot command
> line (only via the debugfs file). However, Thomas Renninger, has posted
> a series to add back the boot-time functionality, see:
>
> Subject: [patch 0/3] Dynamic Debug providing early boot debug messages via
> boot parameter
> http://marc.info/?l=linux-kernel&m=127970474426120&w=2
>
> So I intend to queue those up for 2.6.36, and also update the
> documentation.
Oh, great!
Acked-by: Pekka Enberg <penberg@...helsinki.fi>
Btw, can you easily enable all dev_dbg() calls with the boot parameter?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists