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?