DynamoRIO / DynamoRIO/dynamorio
expose more runtime options: cache sizing, performance-affecting options, etc.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 629
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
_From [derek.br...@gmail.com](https://code.google.com/u/117968039472581148324/) on August 13, 2009 13:07:15_
we should at least expose -no_finite_{bb,trace}_cache since
instrumentation, or even clean calls esp. on 64-bit, can increase
fragment size enough to really hit a lot of replacement.
may as well also document the thread-shared cache sizing options.
pasting in some notes:
this was PR 225139
things we've considered exposing in the past (some of these should be split
off as separate Issues):
- Probe Mode
- elision
- pcaches: -desktop
has complications of where to store the files
- native_exec
we may be able to avoid some of the negative API impact of turning these
on: e.g., for elision we can try the internal-elision idea (PR 214169).
if we do expose the elision options, would we support eliding client-added
non-meta direct ctis? xref PR 215217
xref PR 214889 on exposing notification and logging options for debugging
support
xref issue #140 on documenting -prof_pcs
at the tutorial someone requested that we expose cache sizing options
_Original issue: http://code.google.com/p/dynamorio/issues/detail?id=198_
Contributor guide
Assessment
This issue has not been assessed yet.