IBM/chopstix

Properly organize state extraction scripts

rbertran opened this issue · 1 comments

Create a cohesive interface to ChopStiX

We can implement two behaviors:

  • a) direct dump: everything is handled during 'trace extraction' execution
    • dump register to a file with the right format when starting a execution of region of interest
    • append each page dump with the right format to the previous file on each page fault
    • dump: dump corresponding MPT file when finishing the execution of the region of interest
  • b) dump to the database + offline dumping
    • dump register values and page contents to the database
    • provide post-mortem / offline command line interface to dump mpt/mps for a specific execution of a region of interest.

I'm inclined towards b) , as this will allow to consolidate all the data in a database. Then, it will be more easy to start the research of algorithms/approaches to prune/determine the right states to reproduce.

This is not needed anymore. Contents are dumped to the file system and then post-processed for mpt creation.