tree b85f04e6c7c2e6898abdc151015e64b3c8f2c190
parent 6bf9e131d05a3f41f524f661680fd15b2aa578dd
author Ryan Savitski <rsavitski@google.com> 1608141882 +0000
committer Ryan Savitski <rsavitski@google.com> 1608141882 +0000

traced_perf: memory guardrail proto changes

I went with a "reason for the abrupt stop" proto enum as I foresee
adding one more case - where the StopDataSource is taking too long,
and we should straight up abandon the rest of the work (even if we're
still working through a backlog of events that were recorded before
the Stop IPC).

Change-Id: I1b4a44e75571e5ac8041c3eb014ef35d3f938825