From: Adrian Hunter <adrian.hunter@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH V5 15/25] perf tools: Add member to struct dso for an instruction cache
Date: Sat, 7 Mar 2015 23:06:24 +0200 [thread overview]
Message-ID: <1425762394-29799-16-git-send-email-adrian.hunter@intel.com> (raw)
In-Reply-To: <1425762394-29799-1-git-send-email-adrian.hunter@intel.com>
Add a member to struct dso that can be used by Instruction
Trace implementations to hold a cache for decoded instructions.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
tools/perf/util/dso.c | 2 ++
tools/perf/util/dso.h | 3 +++
2 files changed, 5 insertions(+)
diff --git a/tools/perf/util/dso.c b/tools/perf/util/dso.c
index 814554d..4f089c7 100644
--- a/tools/perf/util/dso.c
+++ b/tools/perf/util/dso.c
@@ -4,6 +4,7 @@
#include "symbol.h"
#include "dso.h"
#include "machine.h"
+#include "itrace.h"
#include "util.h"
#include "debug.h"
@@ -910,6 +911,7 @@ void dso__delete(struct dso *dso)
}
dso__data_close(dso);
+ itrace_cache__free(dso->itrace_cache);
dso_cache__free(&dso->data.cache);
dso__free_a2l(dso);
zfree(&dso->symsrc_filename);
diff --git a/tools/perf/util/dso.h b/tools/perf/util/dso.h
index ced9284..55157dd 100644
--- a/tools/perf/util/dso.h
+++ b/tools/perf/util/dso.h
@@ -101,6 +101,8 @@ struct dsos {
struct rb_root root; /* rbtree root sorted by long name */
};
+struct itrace_cache;
+
struct dso {
struct list_head node;
struct rb_node rb_node; /* rbtree node sorted by long name */
@@ -130,6 +132,7 @@ struct dso {
u16 long_name_len;
u16 short_name_len;
void *dwfl; /* DWARF debug info */
+ struct itrace_cache *itrace_cache;
/* dso data file */
struct {
--
1.9.1
next prev parent reply other threads:[~2015-03-07 21:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 21:06 [PATCH V5 00/25] perf tools: Introduce an abstraction for Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 01/25] perf header: Add Instruction Tracing feature Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 02/25] perf evlist: Add initial support for mmapping an Instruction Trace buffer Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 03/25] perf tools: Add user events for Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 04/25] perf tools: Add support for Instruction Trace recording Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 05/25] perf record: Add basic Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 06/25] perf record: Extend -m option for Instruction Tracing mmap pages Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 07/25] perf tools: Add a user event for Instruction Tracing errors Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 08/25] perf session: Add hooks to allow transparent decoding of Instruction Tracing data Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 09/25] perf session: Add Instruction Tracing options Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 10/25] perf itrace: Add helpers for Instruction Tracing errors Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 11/25] perf itrace: Add helpers for queuing Instruction Tracing data Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 12/25] perf itrace: Add a heap for sorting Instruction Tracing queues Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 13/25] perf itrace: Add processing for Instruction Tracing events Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 14/25] perf itrace: Add a hashtable for caching decoded instructions Adrian Hunter
2015-03-07 21:06 ` Adrian Hunter [this message]
2015-03-07 21:06 ` [PATCH V5 16/25] perf script: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 17/25] perf script: Always allow fields 'addr' and 'cpu' for itrace Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 18/25] perf report: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 19/25] perf inject: Re-pipe Instruction Tracing events Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 20/25] perf inject: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 21/25] perf tools: Add Instruction Tracing index Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 22/25] perf tools: Hit all build ids when Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 23/25] perf tools: Add build option NO_ITRACE to exclude " Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 24/25] perf itrace: Add option to synthesize events for transactions Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 25/25] perf script: Add field option 'flags' to print sample flags Adrian Hunter
2015-03-11 15:55 ` [PATCH V5 00/25] perf tools: Introduce an abstraction for Instruction Tracing Adrian Hunter
2015-03-11 19:33 ` Arnaldo Carvalho de Melo
2015-03-12 20:51 ` Adrian Hunter
2015-03-12 20:57 ` Arnaldo Carvalho de Melo
2015-03-13 11:40 ` Adrian Hunter
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=1425762394-29799-16-git-send-email-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome