public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] perf script: Add support for exporting to sqlite3
Date: Tue, 15 Aug 2017 16:04:12 -0300	[thread overview]
Message-ID: <20170815190411.GC22988@kernel.org> (raw)
In-Reply-To: <5bce6a00-9140-9dd0-e2ed-1e365f65611b@intel.com>

Em Tue, Aug 15, 2017 at 12:25:24PM +0300, Adrian Hunter escreveu:
> On 03/08/17 11:31, Adrian Hunter wrote:
> > Hi
> > 
> > Here is a script for exporting to SQLite 3 the same data as the PostgreSQL
> > export.  The call-graph script is renamed and amended to work with both
> > PostgreSQL and SQLite.
> > 
> > 
> > Adrian Hunter (5):
> >       perf script: Fix missing call_path_id in export-to-postgresql script
> >       perf script: Fix query in call-graph-from-postgresql.py
> >       perf script: Add support for exporting to sqlite3
> >       perf script: Rename call-graph-from-postgresql.py to call-graph-from-sql.py
> >       perf script: Add support for sqlite3 to call-graph-from-sql.py
> > 
> >  tools/perf/Documentation/intel-pt.txt              |   6 +-
> >  .../scripts/python/bin/export-to-sqlite-record     |   8 +
> >  .../scripts/python/bin/export-to-sqlite-report     |  29 ++
> >  ...h-from-postgresql.py => call-graph-from-sql.py} |  70 ++--
> >  tools/perf/scripts/python/export-to-postgresql.py  |   5 +-
> >  tools/perf/scripts/python/export-to-sqlite.py      | 451 +++++++++++++++++++++
> >  6 files changed, 535 insertions(+), 34 deletions(-)
> >  create mode 100644 tools/perf/scripts/python/bin/export-to-sqlite-record
> >  create mode 100644 tools/perf/scripts/python/bin/export-to-sqlite-report
> >  rename tools/perf/scripts/python/{call-graph-from-postgresql.py => call-graph-from-sql.py} (87%)
> >  create mode 100644 tools/perf/scripts/python/export-to-sqlite.py
> 
> Any problem with these?

Nope, will try and process them soon, sorry for the delay...

- Arnaldo

      reply	other threads:[~2017-08-15 19:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  8:31 [PATCH 0/5] perf script: Add support for exporting to sqlite3 Adrian Hunter
2017-08-03  8:31 ` [PATCH 1/5] perf script: Fix missing call_path_id in export-to-postgresql script Adrian Hunter
2017-08-17  7:50   ` [tip:perf/core] perf scripts python: " tip-bot for Adrian Hunter
2017-08-03  8:31 ` [PATCH 2/5] perf script: Fix query in call-graph-from-postgresql.py Adrian Hunter
2017-08-17  7:50   ` [tip:perf/core] perf scripts python: " tip-bot for Adrian Hunter
2017-08-03  8:31 ` [PATCH 3/5] perf script: Add support for exporting to sqlite3 Adrian Hunter
2017-08-17  7:51   ` [tip:perf/core] perf script python: " tip-bot for Adrian Hunter
2017-08-03  8:31 ` [PATCH 4/5] perf script: Rename call-graph-from-postgresql.py to call-graph-from-sql.py Adrian Hunter
2017-08-17  7:51   ` [tip:perf/core] perf script python: " tip-bot for Adrian Hunter
2017-08-03  8:31 ` [PATCH 5/5] perf script: Add support for sqlite3 " Adrian Hunter
2017-08-17  7:51   ` [tip:perf/core] perf script python: " tip-bot for Adrian Hunter
2017-08-15  9:25 ` [PATCH 0/5] perf script: Add support for exporting to sqlite3 Adrian Hunter
2017-08-15 19:04   ` Arnaldo Carvalho de Melo [this message]

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=20170815190411.GC22988@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox