[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k4knqo91.fsf@basil.nowhere.org>
Date: Tue, 09 Nov 2010 02:28:26 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Mike Waychison <mikew@...gle.com>
Cc: simon.kagstrom@...insight.net, davem@...emloft.net,
nhorman@...driver.com, Matt Mackall <mpm@...enic.com>,
adurbin@...gle.com, linux-kernel@...r.kernel.org,
chavey@...gle.com, Greg KH <greg@...ah.com>,
Américo Wang <xiyou.wangcong@...il.com>,
akpm@...ux-foundation.org, linux-api@...r.kernel.org
Subject: Re: [PATCH v2 00/23] netoops support
Mike Waychison <mikew@...gle.com> writes:
I'm still not fully convinced this needs to be a fully separate
mechanism from netconsole. It seems a lot of work to implement
basically log level.
Maybe netconsole could be patched to support only dumping KERN_EMERG?
But I guess the structured logging has some advantages, although
there have been certainly oops parsers (e.g. kerneloops.org) without it.
> * I am _NOT_ happy with the remaining userland ABIs presented in this
> patchset. Specifically the files "net_dump_now",
> "net_dump_one_shot", "netdump_fw_version", "netdump_board_name"
> and
fw_version and board_name is known by the kernel anyways through the DMI
interface, assuming the BIOS supplies that. We also dump it already
on a standard oops. So why not just use that directly?
As a general user ABI perhaps simply an unstructured string is better
that is included in the packet.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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