Skip to main content

A bundle of auxiliary scripts for the Anycore project

Project description

Pre-Simulation readiness checking

  • Checkpointing/SyscallAnalysis/prerun_check.py - Perform a prerun check based on the info in manifest DB.
  • Checkpointing/SyscallAnalysis/generate_manifest.py - Analyze the System Call trace for an entire SPEC simulation (dumped by a special version of spike). Then produce the manifest for it. Finally save the manifest into DB.

Misc.

  • SpecResultVerification/spike_trim.py - Trim out the extra header/tail message produced by spike or pk during the simulation. Useful if you want to automatically verify the STDOUT output of a SPEC simulation.
  • Checkpointing/ChkptDescFileGen/smpt2ckptdesc.py - Convert the Simpoint output file to the checkpoint job description file accepted by Spike.
  • Checkpointing/DumpHTIF/chkpt_htif_dump.py - Show the HTIF syscalls recorded in a checkpoint file. When restoring a checkpoint, those syscalls will be executed in sequence to bring back the state of HTIF FESVR.
  • TetherSim/SimTetheringController.py - Controller for 721sims working in tethering mode.

To work with trace dump

  • CpuTraceAnalysis/trace2google.py - Analyze the trace dumped by spike or 721sim and output the result in Google's Trace Event Format.

  • To visualize the result, use speedscope (recommend) or Chromium's about://tracing .

    • if ignore_symbol.yaml exists in CWD, it will be read to filter out the defined function calls. See CpuTraceAnalysis/ignore_symbol.yaml for an example.
  • CpuTraceAnalysis/trace2tracevis.py - Analyze and visualize the trace dumped by spike or 721sim in a homebrew timeline frontend (using timeline-js).

    • if ignore_symbol.yaml exists in CWD - Will be read to filter out the defined function calls. See CpuTraceAnalysis/ignore_symbol.yaml for an example.
    • It's recommended to use trace2google.py. Because the trace_vis frontend uses timeline-js, which is not intended for visualizing tracing result, it can be very slow and unresponsive when working with trace with a large amount of event.

image-20201105011703029

Viewing the trace2google.py output with speedscope

image-20201105011839379

Viewing the trace2google.py output with Chrome's about:tracing

image-20200813043919822

Viewing the trace using homebrew TraceVis frontend (use timeline-js)

WIP.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

anycore-dbg-supplement-0.2.0.tar.gz (7.6 MB view details)

Uploaded Source

Built Distribution

anycore_dbg_supplement-0.2.0-py3-none-any.whl (7.7 MB view details)

Uploaded Python 3

File details

Details for the file anycore-dbg-supplement-0.2.0.tar.gz.

File metadata

  • Download URL: anycore-dbg-supplement-0.2.0.tar.gz
  • Upload date:
  • Size: 7.6 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.4 CPython/3.8.6 Linux/5.4.80-1-MANJARO

File hashes

Hashes for anycore-dbg-supplement-0.2.0.tar.gz
Algorithm Hash digest
SHA256 f11164e81c8f472b37c13a70ec003c86cee080951748a8b48ef0c77def5022c8
MD5 ef067736dd11730808f984b5f83cc046
BLAKE2b-256 58ce53b3d052da2341bd70db0fbb50e8c0f2ace45577deee9661746e73e1c02d

See more details on using hashes here.

Provenance

File details

Details for the file anycore_dbg_supplement-0.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for anycore_dbg_supplement-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 62713c7adeccc5be77dc7ca779c0b1459cd721ea1905d8b8b544846a30560346
MD5 494a2959c6048514785a67f825481e55
BLAKE2b-256 bf938330922a4c128e445eb741f1a1020330de38542978b6837e15f30406e833

See more details on using hashes here.

Provenance

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page