Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2007-01-02 Thread Dave Jones
On Tue, Jan 02, 2007 at 01:03:54PM -0500, Theodore Tso wrote: > or perhaps better, making the sysrq-m information > available via either /proc or /sys? or debugfs ? Dave -- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel"

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2007-01-02 Thread Theodore Tso
On Tue, Jan 02, 2007 at 10:33:32AM +, Alan wrote: > On Mon, 1 Jan 2007 23:37:43 -0500 > Theodore Tso <[EMAIL PROTECTED]> wrote: > > > Is this patch a consistency thing? > > > > The goal of the patch was to avoid filling /var/log/messages huge > > amounts of sysrq text. Some of the sysrq comma

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2007-01-02 Thread Dave Jones
On Tue, Jan 02, 2007 at 10:33:32AM +, Alan Cox wrote: > On Mon, 1 Jan 2007 23:37:43 -0500 > Theodore Tso <[EMAIL PROTECTED]> wrote: > > > Is this patch a consistency thing? > > > > The goal of the patch was to avoid filling /var/log/messages huge > > amounts of sysrq text. Some of the s

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2007-01-02 Thread Alan
On Mon, 1 Jan 2007 23:37:43 -0500 Theodore Tso <[EMAIL PROTECTED]> wrote: > > Is this patch a consistency thing? > > The goal of the patch was to avoid filling /var/log/messages huge > amounts of sysrq text. Some of the sysrq commands, especially sysrq-m > and sysrq-t emit a truly vast amount of

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2007-01-01 Thread Theodore Tso
On Fri, Dec 29, 2006 at 08:42:47PM -0800, Andrew Morton wrote: > On Fri, 29 Dec 2006 22:24:53 -0500 > "Theodore Ts'o" <[EMAIL PROTECTED]> wrote: > > > Print messages resulting from sysrq-m with a KERN_INFO instead of the > > default KERN_WARNING priority > > hm, I wonder why. If someone does sys

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2007-01-01 Thread Theodore Tso
On Fri, Dec 29, 2006 at 11:19:49PM -0600, * * wrote: > Was this patch tested? > > > static inline void show_node(struct zone *zone) > > { > >if (NUMA_BUILD) > >- printk("Node %d ", zone_to_nid(zone)); > >+ printk(KERN_INFO, "Node %d ", zone_to_nid(zone)); > > H

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2006-12-29 Thread * *
Was this patch tested? On 12/29/06, Theodore Ts'o <[EMAIL PROTECTED]> wrote: Print messages resulting from sysrq-m with a KERN_INFO instead of the default KERN_WARNING priority Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]> Index: linux-2.6/mm/page_alloc.c =

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2006-12-29 Thread Dave Jones
On Fri, Dec 29, 2006 at 08:42:47PM -0800, Andrew Morton wrote: > On Fri, 29 Dec 2006 22:24:53 -0500 > "Theodore Ts'o" <[EMAIL PROTECTED]> wrote: > > > Print messages resulting from sysrq-m with a KERN_INFO instead of the > > default KERN_WARNING priority > > hm, I wonder why. If someone d

Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

2006-12-29 Thread Andrew Morton
On Fri, 29 Dec 2006 22:24:53 -0500 "Theodore Ts'o" <[EMAIL PROTECTED]> wrote: > Print messages resulting from sysrq-m with a KERN_INFO instead of the > default KERN_WARNING priority hm, I wonder why. If someone does sysrq- then they presumably want to display the result? Tricky. Is this patch

[PATCH] Print sysrq-m messages with KERN_INFO priority

2006-12-29 Thread Theodore Ts'o
Print messages resulting from sysrq-m with a KERN_INFO instead of the default KERN_WARNING priority Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]> Index: linux-2.6/mm/page_alloc.c === --- linux-2.6.orig/mm/page_alloc.c 2006-