Re: [RESEND RFC PATCH 2/5] printk: add message hash values in /dev/kmsg output

2013-07-26 Thread Hidehiro Kawai
Hello, (2013/07/26 0:01), Kazuo Ito wrote:> Hello, again. > > On Thu, Jul 25, 2013 at 5:37 PM, Hidehiro Kawai < > hidehiro.kawai...@hitachi.com> wrote: > >> diff --git a/drivers/base/core.c b/drivers/base/core.c >> index 8856d74..e2bf2af 100644 >> --- a/drivers/base/core.c >> +++ b/drivers/base/co

[RESEND RFC PATCH 2/5] printk: add message hash values in /dev/kmsg output

2013-07-25 Thread Hidehiro Kawai
This patch adds the hash value for each printk line when reading /dev/kmsg as bellow: 6,154,325061,-,b7db707c@kernel/smp.c:554;Brought up 4 CPUs Here, the 5th field is the 32-bit hash value followed by @:. If this feature is disabled, i.e. CONFIG_KMSG_HASH=n, or the hash value hasn't be

[RFC PATCH 2/5] printk: add message hash values in /dev/kmsg output

2013-07-02 Thread Hidehiro Kawai
This patch adds the hash value for each printk line when reading /dev/kmsg as bellow: 6,154,325061,-,b7db707c@kernel/smp.c:554;Brought up 4 CPUs Here, the 5th field is the 32-bit hash value followed by @:. If this feature is disabled, i.e. CONFIG_KMSG_HASH=n, or the hash value hasn't be