[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinBN7QN_c_oyFdpC3vaj9nLEfWCWeeqRCgiEdBW@mail.gmail.com>
Date: Mon, 20 Dec 2010 21:13:33 -0800
From: Tony Luck <tony.luck@...el.com>
To: Huang Ying <ying.huang@...el.com>
Cc: Borislav Petkov <bp@...en8.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...e.hu" <mingo@...e.hu>, "greg@...ah.com" <greg@...ah.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
Kyungmin Park <kmpark@...radead.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [concept & "good taste" review] persistent store
On Mon, Dec 20, 2010 at 4:48 PM, Huang Ying <ying.huang@...el.com> wrote:
> If persistent storage driver (such as ERST) implements kmsg_dumper by
> themselves, that should be easier to use multiple records for one
> message dumping request.
Or I can build it into the fs/pstore layer. If the record size looks too
small[*], loop writing multiple records (starting with the tail of the buffer,
so that if the persistent store fills up, we are sure to have the stack
back trace and register dump).
-Tony
[*] "Too small" may be an architecture dependent value. Archs
with a large number of registers (like ia64) might need more space
than those with fewer registers.
--
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