tree 8a77fac99879f781d3c4eeaa8c79b3d9eb7bbc13
parent 765b2a04576f4e985a88165456f5ee55cdfe56b8
author Alex Light <allight@google.com> 1556843702 -0700
committer Treehugger Robot <treehugger-gerrit@google.com> 1556913387 +0000

Correctly handle thread deopt with thread-specific JVMTI events

We were incorrectly treating some JVMTI events as still requiring
global deopt even though that requirment had been lifted. This meant
that if one sets thread-specific event notification requests on
multiple threads only some of them will actually be deoptimized. This
could cause events to be missed if the relevant methods/threads had
been jitted.

Test: ./test.py --host --jit-on-first-use
Test: ./test.py
Bug: 131865028

Change-Id: Ib196faa635e61262eea7ccc576dc0d700b3e7eff