[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F1A7854.7010808@gmail.com>
Date: Sat, 21 Jan 2012 09:33:24 +0100
From: Marco Stornelli <marco.stornelli@...il.com>
To: Seiji Aguchi <seiji.aguchi@....com>
CC: Kees Cook <keescook@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Tony Luck <tony.luck@...el.com>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <greg@...ah.com>,
Randy Dunlap <rdunlap@...otime.net>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5] ramoops: use pstore interface
Il 19/01/2012 00:20, Seiji Aguchi ha scritto:
>>> Are there any specific usecases you need to unload ramoops?
>>
>> For me, it would be useful during development. Beyond that, not that I can see.
>
> Thank you for your quick relay. I understood this is useful for you.
>
> But, as Tony said, I think this is a low priority because
> there is a side effect for end users.
> If they unload ramoops by mistake, messages will be lost.
>
> In my opinion, we have to consider whether each feature
> is truly needed for end users (not for developers).
>
> Seiji
>
>
First of all ramoops was born mainly for debug purpose and to help the
maintainability of a product. I used it in systems where the uptime (so
no reboot) was important. So it can be very useful for me load the
module, gather logs and unload it for example. A kernel panic is not
recoverable so the reboot is needed but it's not always true for a
kernel oops.
Marco
--
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