~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/tools/perf/Documentation/db-export.txt

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 Database Export
  2 ===============
  3 
  4 perf tool's python scripting engine:
  5 
  6         tools/perf/util/scripting-engines/trace-event-python.c
  7 
  8 supports scripts:
  9 
 10         tools/perf/scripts/python/export-to-sqlite.py
 11         tools/perf/scripts/python/export-to-postgresql.py
 12 
 13 which export data to a SQLite3 or PostgreSQL database.
 14 
 15 The export process provides records with unique sequential ids which allows the
 16 data to be imported directly to a database and provides the relationships
 17 between tables.
 18 
 19 Over time it is possible to continue to expand the export while maintaining
 20 backward and forward compatibility, by following some simple rules:
 21 
 22 1. Because of the nature of SQL, existing tables and columns can continue to be
 23 used so long as the names and meanings (and to some extent data types) remain
 24 the same.
 25 
 26 2. New tables and columns can be added, without affecting existing SQL queries,
 27 so long as the new names are unique.
 28 
 29 3. Scripts that use a database (e.g. exported-sql-viewer.py) can maintain
 30 backward compatibility by testing for the presence of new tables and columns
 31 before using them. e.g. function IsSelectable() in exported-sql-viewer.py
 32 
 33 4. The export scripts themselves maintain forward compatibility (i.e. an existing
 34 script will continue to work with new versions of perf) by accepting a variable
 35 number of arguments (e.g. def call_return_table(*x)) i.e. perf can pass more
 36 arguments which old scripts will ignore.
 37 
 38 5. The scripting engine tests for the existence of script handler functions
 39 before calling them.  The scripting engine can also test for the support of new
 40 or optional features by checking for the existence and value of script global
 41 variables.

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php