On Thu, 23 Oct 2014 13:45:13 +0300, Adrian Hunter wrote: > This patch introduces an abstraction for exporting sample > data in a database-friendly way. The abstraction does not > implement the actual output. A subsequent patch takes this > facility into use for extending the script interface. > > The abstraction is needed because static data like symbols, > dsos, comms etc need to be exported only once. That means > allocating them a unique identifier and recording it on each > structure. The member 'db_id' is used for that. 'db_id' > is just a 64-bit sequence number.
Can we do it somewhere in a script not in the core code? I don't feel comfortable to add those bits into the core code. What if we export meta events like task, mmap or some user events to the script optionally and let it process the data? Thanks, Namhyung > > Exporting centres around the db_export__sample() function > which exports the associated data structures if they have > not yet been allocated a db_id. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
