Date: Fri, 7 Jan 2005 11:26:48 +1100
From: Anton Blanchard <anton@samba.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linas Vepstas <linas@austin.ibm.com>, linux-kernel@vger.kernel.org,
       torvalds@osdl.org
Subject: Re: [PATCH] kernel/printk.c  lockless access
Message-ID: <20050107002648.GD14239@krispykreme.ozlabs.ibm.com>
References: <20050106195812.GL22274@austin.ibm.com> <20050106161241.11a8d07c.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050106161241.11a8d07c.akpm@osdl.org>
User-Agent: Mutt/1.5.6+20040907i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 693
Lines: 16

 
> We faced the same problem in the Digeo kernel.  When the kernel oopses we
> want to grab the last kilobyte or so of the printk buffer and stash it into
> nvram.  We did this via a function which copies the data rather than
> exporting all those variables, which I think is a nicer and more
> maintainable approach:

Actually Id love to do this on ppc64 too. Its always difficult to get a
customer to remember to save away an oops report.

Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/