This is an archive of the discontinued LLVM Phabricator instance.

[XRay] Create an Index of sleds per function
ClosedPublic

Authored by dberris on May 1 2017, 12:05 AM.

Details

Summary

This change adds a new section to the xray-instrumented binary that
stores an index into ranges of the instrumentation map, where sleds
associated with the same function can be accessed as an array. At
runtime, we can get access to this index by function ID offset allowing
for selective patching and unpatching by function ID.

Each entry in this new section (xray_fn_idx) will include two pointers
indicating the start and one past the end of the sleds associated with
the same function. These entries will be 16 bytes long on x86 and
aarch64. On arm, we align to 16 bytes anyway so the runtime has to take
that into consideration.

__{start,stop}_xray_fn_idx will be the symbols that the runtime will
look for when we implement the selective patching/unpatching by function
id APIs. Because XRay synthesizes the function id's in a monotonically
increasing manner at runtime now, implementations (and users) can use
this table to look up the sleds associated with a specific function.
This is useful in implementations that want to do things like:

  • Implement coverage mode for functions by patching everything pre-main, then as functions are encountered, the installed handler can unpatch the function that's been encountered after recording that it's been called.
  • Do "learning mode", so that the implementation can figure out some statistical information about function calls by function id for a time being, and then determine which functions are worth uninstrumenting at runtime.
  • Do "selective instrumentation" where an implementation can specifically instrument only certain function id's at runtime (either based on some external data, or through some other heuristics) instead of patching all the instrumented functions at runtime.

Event Timeline

dberris created this revision.May 1 2017, 12:05 AM
dblaikie accepted this revision.May 3 2017, 11:09 AM

Looks reasonable to me. (others can speak up if they want to hold off on committing this until they've had a chance to look)

This revision is now accepted and ready to land.May 3 2017, 11:09 AM

Thanks @dblaikie -- I'll land and deal with follow-ups as required in the meantime.

Cheers

This revision was automatically updated to reflect the committed changes.