From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] perf inject: Minor improvements
Date: Fri, 20 May 2022 16:23:59 +0300 [thread overview]
Message-ID: <20220520132404.25853-1-adrian.hunter@intel.com> (raw)
Hi
Here are patches for 2 minor improvements for perf inject:
1. Keep some features sections from input file
2. Keep a copy of kcore_dir
Adrian Hunter (5):
perf header: Add ability to keep feature sections
libperf: Add preadn()
perf inject: Keep some features sections from input file
perf data: Add has_kcore_dir()
perf inject: Keep a copy of kcore_dir
tools/lib/perf/include/internal/lib.h | 2 +
tools/lib/perf/lib.c | 20 +++++
tools/perf/builtin-inject.c | 162 +++++++++++++++++++++++++++++++++-
tools/perf/util/data.c | 14 +++
tools/perf/util/data.h | 1 +
tools/perf/util/header.c | 62 +++++++++++--
tools/perf/util/header.h | 15 ++++
7 files changed, 264 insertions(+), 12 deletions(-)
Regards
Adrian
next reply other threads:[~2022-05-20 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 13:23 Adrian Hunter [this message]
2022-05-20 13:24 ` [PATCH 1/5] perf header: Add ability to keep feature sections Adrian Hunter
2022-05-20 13:24 ` [PATCH 2/5] libperf: Add preadn() Adrian Hunter
2022-05-20 13:55 ` David Laight
2022-05-20 15:56 ` [PATCH V2 " Adrian Hunter
2022-05-20 13:24 ` [PATCH 3/5] perf inject: Keep some features sections from input file Adrian Hunter
2022-05-23 8:14 ` Jiri Olsa
2022-05-23 9:23 ` Adrian Hunter
2022-05-20 13:24 ` [PATCH 4/5] perf data: Add has_kcore_dir() Adrian Hunter
2022-05-20 13:24 ` [PATCH 5/5] perf inject: Keep a copy of kcore_dir Adrian Hunter
2022-05-23 8:16 ` [PATCH 0/5] perf inject: Minor improvements Jiri Olsa
2022-05-23 13:12 ` 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=20220520132404.25853-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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.