All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 9/9] perf inject: enable COMPRESSED records decompression
Date: Tue, 26 Feb 2019 09:28:32 +0300	[thread overview]
Message-ID: <019869b7-bb11-6b67-b914-e5d96d85888c@linux.intel.com> (raw)
In-Reply-To: <10824243-040d-4b44-65c0-2c63870e9bb6@linux.intel.com>


Initialized decompression API so COMPRESSED records would be
decompressed into the resulting output data file.

Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
---
 tools/perf/builtin-inject.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tools/perf/builtin-inject.c b/tools/perf/builtin-inject.c
index 9bb1f35d5cb7..5a5bc4207766 100644
--- a/tools/perf/builtin-inject.c
+++ b/tools/perf/builtin-inject.c
@@ -839,6 +839,9 @@ int cmd_inject(int argc, const char **argv)
 	if (inject.session == NULL)
 		return -1;
 
+	if (zstd_init(&(inject.session->zstd_data), 0) < 0)
+		pr_warning("Decompression initialization failed.\n");
+
 	if (inject.build_ids) {
 		/*
 		 * to make sure the mmap records are ordered correctly
@@ -869,6 +872,7 @@ int cmd_inject(int argc, const char **argv)
 	ret = __cmd_inject(&inject);
 
 out_delete:
+	zstd_fini(&(inject.session->zstd_data));
 	perf_session__delete(inject.session);
 	return ret;
 }

  parent reply	other threads:[~2019-02-26  6:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26  5:31 [PATCH v3 0/9] perf: enable compression of record mode trace to save storage space Alexey Budankov
2019-02-26  5:55 ` [PATCH v3 2/9] perf record: implement -f,--mmap-flush=<threshold> option Alexey Budankov
2019-02-26  5:57 ` [PATCH v3 3/9] perf session: define bytes_transferred and bytes_compressed metrics Alexey Budankov
2019-02-26  5:59 ` [PATCH v3 4/9] perf record: implement COMPRESSED event record and its attributes Alexey Budankov
2019-02-26  6:03 ` [PATCH v3 5/9] perf mmap: implement dedicated memory buffer for data compression Alexey Budankov
2019-02-26  6:10 ` [PATCH v3 6/9] perf util: introduce Zstd based streaming compression API Alexey Budankov
2019-02-26  6:20 ` [PATCH v3 7/9] perf record: implement -z,--compression_level=n option and compression Alexey Budankov
2019-02-26  6:26 ` [PATCH v3 8/9] perf report: implement record trace decompression Alexey Budankov
2019-02-26  6:28 ` Alexey Budankov [this message]
2019-02-26  7:01 ` [PATCH v3 1/9] feature: implement libzstd check, LIBZSTD_DIR and NO_LIBZSTD defines Alexey Budankov
2019-02-27 14:27 ` [PATCH v3 0/9] perf: enable compression of record mode trace to save storage space Jiri Olsa
2019-02-27 14:56   ` Alexey Budankov
2019-02-27 14:28 ` Jiri Olsa
2019-02-27 15:40   ` Alexey Budankov

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=019869b7-bb11-6b67-b914-e5d96d85888c@linux.intel.com \
    --to=alexey.budankov@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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.