mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: <acme@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <lizefan@huawei.com>,
	<pi3orama@163.com>, Wang Nan <wangnan0@huawei.com>
Subject: [PATCH v3 0/2] perf tools: Backward ring buffer support
Date: Mon, 9 May 2016 01:47:49 +0000	[thread overview]
Message-ID: <1462758471-89706-1-git-send-email-wangnan0@huawei.com> (raw)

Commit 9ecda41acb97 ("perf/core: Add ::write_backward attribute to
perf event") introduces backward ring buffer. This 2 patches add basic
support for reading from it, and add a new test case for it.

v2 -> v3:
  Improve commit message, add more comments (patch 1/2). patch 1-2/4 in
  v2 have been collected so remove them.

v1 -> v2:
  Patch 1/5 in v1 has been collected by perf/core, so remove it;
  Change function names in patch 2/5 in v1 (1/4 in v2):
      __perf_evlist__mmap_read -> perf_mmap__read

Wang Nan (2):
  perf tools: Support reading from backward ring buffer
  perf tests: Add test to check backward ring buffer

 tools/perf/tests/Build                  |   1 +
 tools/perf/tests/backward-ring-buffer.c | 151 ++++++++++++++++++++++++++++++++
 tools/perf/tests/builtin-test.c         |   4 +
 tools/perf/tests/tests.h                |   1 +
 tools/perf/util/evlist.c                |  50 +++++++++++
 tools/perf/util/evlist.h                |   4 +
 6 files changed, 211 insertions(+)
 create mode 100644 tools/perf/tests/backward-ring-buffer.c

-- 
1.8.3.4

             reply	other threads:[~2016-05-09  1:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  1:47 Wang Nan [this message]
2016-05-09  1:47 ` [PATCH v3 1/2] perf tools: Support reading from backward ring buffer Wang Nan
2016-05-10 20:31   ` [tip:perf/core] " tip-bot for Wang Nan
2016-05-09  1:47 ` [PATCH v3 2/2] perf tests: Add test to check " Wang Nan
2016-05-09 21:12   ` Arnaldo Carvalho de Melo
2016-05-10 20:32   ` [tip:perf/core] " tip-bot for Wang Nan

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=1462758471-89706-1-git-send-email-wangnan0@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=pi3orama@163.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

all inboxes | Powered by JetHome®