From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: shuox.liu@intel.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Cc: tony.luck@intel.com, keescook@chromium.org, ccross@android.com,
anton@enomsg.org
Subject: Re: [PATCH] pstore: reset ftrace_read_cnt at ramoops_pstore_open
Date: Sun, 02 Mar 2014 17:03:59 +0800 [thread overview]
Message-ID: <5312F3FF.80700@linux.intel.com> (raw)
In-Reply-To: <1393569464-14904-1-git-send-email-shuox.liu@intel.com>
On 2014/2/28 14:37, shuox.liu@intel.com wrote:
> From: Liu ShuoX <shuox.liu@intel.com>
>
> ftrace_read_cnt need to be reset in open to support mutli times
> getting the records.
Andrew,
Would you like to merge it to your testing tree?
pstore is a very important feature for debugging hard issues on
Android mobiles.
Yanmin
>
> Signed-off-by: Liu ShuoX <shuox.liu@intel.com>
> ---
> fs/pstore/ram.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
> index fa8cef2..a5d0cab 100644
> --- a/fs/pstore/ram.c
> +++ b/fs/pstore/ram.c
> @@ -101,6 +101,7 @@ static int ramoops_pstore_open(struct pstore_info *psi)
>
> cxt->dump_read_cnt = 0;
> cxt->console_read_cnt = 0;
> + cxt->ftrace_read_cnt = 0;
> return 0;
> }
>
next prev parent reply other threads:[~2014-03-02 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 6:37 [PATCH] pstore: reset ftrace_read_cnt at ramoops_pstore_open shuox.liu
2014-03-02 9:03 ` Zhang, Yanmin [this message]
2014-03-03 19:45 ` Kees Cook
2014-03-04 1:40 ` Liu ShuoX
2014-03-04 19:11 ` Kees Cook
2014-03-07 2:58 ` Liu ShuoX
2014-03-07 5:43 ` Kees Cook
2014-03-07 21:25 ` Andrew Morton
2014-03-08 0:23 ` Kees Cook
2014-03-08 4:09 ` [PATCH] pstore: clarify clearing of _read_cnt in ramoops_context Liu Shuo
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=5312F3FF.80700@linux.intel.com \
--to=yanmin_zhang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuox.liu@intel.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.