lkml.org 
[lkml]   [2008]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/6] loglevel=pci:8,acpi:8,apic=8 support v6

* H. Peter Anvin <hpa@zytor.com> wrote:

> 8) The ability to accessed filtered messages a posteori (via dmesg),
> which is something we currently take for granted.
>
> This *is* the fundamental difference between what Yinghai has now and
> both your stuff and Yinghai's original proposal. Not producing the
> additional messages at all is inherently cheaper, sometimes *much*
> cheaper, but it obviously means the information is not accessible at
> all.

which is what we really want. If a bootup fails, the user has to repeat
the bootup at least once with a verbosity level increased and with
(hopefully) some sort of log capture facility attached.

So the point would be, if the user specified loglevel=all, we would get
really comprehensive, one-stop-shop output.

> At the moment, I would argue that the fact that dmesg is, in effect,
> more verbose than the kernel itself is a good thing; it makes dmesg
> dumps more useful.

yes - but log messages not showing up on the physical console is already
a task that is solved via regular loglevels. printks are being removed
because even printing to the dmesg can be expensive (vsprintf is not the
cheapest of functions, and most of dmesg shows up in the syslog and
people want a clear, default, not too verbose output for that).

so the main feature of these patches is that we can cut out too verbose
information by default, and we can reactivate it with a single central
switch (and a repeated bootup - which has to be done anyway). Everything
else is already solved via either traditional loglevels or pr_debug()
based, build-time facilities.

Ingo


\
 
 \ /
  Last update: 2008-09-18 13:01    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site