From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] perf inject: Also re-pipe lost_samples event
Date: Fri, 13 Nov 2015 11:48:32 +0200 [thread overview]
Message-ID: <1447408112-1920-4-git-send-email-adrian.hunter@intel.com> (raw)
In-Reply-To: <1447408112-1920-1-git-send-email-adrian.hunter@intel.com>
perf inject must re-pipe all events otherwise they get dropped
from the output file.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
tools/perf/builtin-inject.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/builtin-inject.c b/tools/perf/builtin-inject.c
index 0a945d2e8ca5..99d127fe9c35 100644
--- a/tools/perf/builtin-inject.c
+++ b/tools/perf/builtin-inject.c
@@ -675,6 +675,7 @@ int cmd_inject(int argc, const char **argv, const char *prefix __maybe_unused)
.fork = perf_event__repipe,
.exit = perf_event__repipe,
.lost = perf_event__repipe,
+ .lost_samples = perf_event__repipe,
.aux = perf_event__repipe,
.itrace_start = perf_event__repipe,
.context_switch = perf_event__repipe,
--
1.9.1
next prev parent reply other threads:[~2015-11-13 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 9:48 [PATCH 0/3] perf tools: 3 fixes Adrian Hunter
2015-11-13 9:48 ` [PATCH 1/3] perf tools: Fix dso lookup by long name and missing buildids Adrian Hunter
2015-11-18 6:18 ` [tip:perf/urgent] perf symbols: " tip-bot for Adrian Hunter
2015-11-13 9:48 ` [PATCH 2/3] perf buildid-list: Requires ordered events Adrian Hunter
2015-11-18 6:19 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2015-11-13 9:48 ` Adrian Hunter [this message]
2015-11-18 6:19 ` [tip:perf/urgent] perf inject: Also re-pipe lost_samples event tip-bot for Adrian Hunter
2015-11-13 15:24 ` [PATCH 0/3] perf tools: 3 fixes Arnaldo Carvalho de Melo
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=1447408112-1920-4-git-send-email-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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.