From: Marco Stornelli <marco.stornelli@gmail.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <greg@kroah.com>,
Randy Dunlap <rdunlap@xenotime.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] ramoops: use pstore interface
Date: Sat, 21 Jan 2012 09:33:24 +0100 [thread overview]
Message-ID: <4F1A7854.7010808@gmail.com> (raw)
In-Reply-To: <5C4C569E8A4B9B42A84A977CF070A35B2DA7A7F237@USINDEVS01.corp.hds.com>
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
next prev parent reply other threads:[~2012-01-21 8:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 23:58 [PATCH v5] ramoops: use pstore interface Kees Cook
2012-01-18 22:06 ` Andrew Morton
2012-01-18 22:16 ` Kees Cook
2012-01-18 22:40 ` Seiji Aguchi
2012-01-18 22:47 ` Kees Cook
2012-01-18 23:20 ` Seiji Aguchi
2012-01-21 8:33 ` Marco Stornelli [this message]
2012-04-02 20:39 ` Shuah Khan
2012-04-02 20:51 ` Kees Cook
2012-04-02 21:09 ` Andrew Morton
2012-04-09 21:33 ` Andrew Morton
2012-04-09 21:42 ` Luck, Tony
2012-04-10 8:34 ` Marco Stornelli
2012-04-10 16:11 ` Kees Cook
2012-04-11 6:33 ` Marco Stornelli
2012-04-11 6:37 ` Andrew Morton
2012-01-18 22:37 ` Luck, Tony
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F1A7854.7010808@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=seiji.aguchi@hds.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.