From: Kees Cook <keescook@chromium.org>
To: Joel Fernandes <joelaf@google.com>
Cc: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/8] pstore: Improve performance of ftrace backend with ramoops
Date: Fri, 11 Nov 2016 14:21:45 -0800 [thread overview]
Message-ID: <1478902913-143778-1-git-send-email-keescook@chromium.org> (raw)
Hi Joel,
I've reorganized a bunch of the logic here. Since pstore is going to need
the init_przs() logic for multiple pmsg przs, I wanted to get this in and
make sure I was happy with how it looks. I figured this would reduce our
round-trip time on reviews. :)
Can you test this series and verify that it works as you're expecting? I've
validated some basic behavior already, but don't have a good test-case for
ftrace. What commands do you actually use for testing ftrace? I'd like to
add something to my local tests.
Thanks!
-Kees
next reply other threads:[~2016-11-11 22:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 22:21 Kees Cook [this message]
2016-11-11 22:21 ` [PATCH v3 1/8] pstore: Make spinlock per zone instead of global Kees Cook
2016-11-11 22:21 ` [PATCH v3 2/8] pstore: Warn on PSTORE_TYPE_PMSG using deprecated function Kees Cook
2016-11-11 22:21 ` [PATCH v3 3/8] pstore: Allow prz to control need for locking Kees Cook
2016-11-11 22:21 ` [PATCH v3 4/8] pstore: Make ramoops_init_przs generic for other prz arrays Kees Cook
2016-11-11 22:21 ` [PATCH v3 5/8] ramoops: Split ftrace buffer space into per-CPU zones Kees Cook
2016-11-11 22:21 ` [PATCH v3 6/8] pstore: Add ftrace timestamp counter Kees Cook
2016-11-11 22:21 ` [PATCH v3 7/8] pstore: Merge per-CPU ftrace records into one Kees Cook
2016-11-11 22:21 ` [PATCH v3 8/8] pstore: improve error report for failed setup Kees Cook
2016-11-15 19:55 ` [PATCH v3 0/8] pstore: Improve performance of ftrace backend with ramoops Joel Fernandes
2016-11-15 21:36 ` Kees Cook
2016-11-15 22:06 ` Joel Fernandes
2016-11-15 22:14 ` Kees Cook
2016-11-16 6:38 ` Joel Fernandes
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=1478902913-143778-1-git-send-email-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).