commit ded3b84bd08b12cfb3d021150aa2aede7e0179cc
author Ryan Savitski <rsavitski@google.com> Thu Nov 07 17:04:11 2019 +0000
committer Ryan Savitski <rsavitski@google.com> Thu Nov 07 17:04:11 2019 +0000
tree 6dfb01bc5bf56d12974a6e721a201780ffdee4e8
parent 62a814392cf5fa8d4966cf8d5c883e5162635f52

compact sched_waking: cfg/trace protos

Intentional choices:
* kept a single "enabled" cfg bool. We can still have only one of
  the two events enabled, but if both of them are on, I don't
  see much value in having per-event compactness toggles. So keeping
  the config simple.
* We were considering renaming `compact_sched` to just `compact_event`
  or similar in the config. But I think we won't be adding any more
  compact events in the near future, and even if we do, it might be
  more descriptive to use a new config message/field (and keeping this
  one specific to the scheduling events).

Tracing msg: the emitting pid will be inferred from scheduling info in
the trace_processor. We record all other fields (unlike the earlier
revisions of this patch).

The interned comm table will now be shared between switch & waking.

Change-Id: Ie6e96a122e70acd9104d1d7cda7261f5d1838594