Revert "Use RAII for preventing user-code suspensions"

This reverts commit 9c8f34448e0e2b0b0b0094d75dadc3116f5610fa.

Bug: 130150240
Reason for revert: Parent causes lock-level violations in gcstress.

Change-Id: I6c29a0d37a933ac37ab835e171750c2ae5ca0599

1 files changed, 0 insertions, 11 deletions

diff --git a/openjdkjvmti/ti_thread.h b/openjdkjvmti/ti_thread.h
index c5443bfb9f..39f1f0725c 100644
--- a/openjdkjvmti/ti_thread.h
+++ b/openjdkjvmti/ti_thread.h
@@ -52,17 +52,6 @@ namespace openjdkjvmti {
 
 class EventHandler;
 
-// Gains the user_code_suspension_lock_ and ensures that the code will not suspend for user-code.
-class SCOPED_CAPABILITY ScopedNoUserCodeSuspension {
- public:
-  explicit ScopedNoUserCodeSuspension(art::Thread* self)
-      ACQUIRE(art::Locks::user_code_suspension_lock_);
-  ~ScopedNoUserCodeSuspension() RELEASE(art::Locks::user_code_suspension_lock_);
-
- private:
-  art::Thread* self_;
-};
-
 // The struct that we store in the art::Thread::custom_tls_ that maps the jvmtiEnvs to the data
 // stored with that thread. This is needed since different jvmtiEnvs are not supposed to share TLS
 // data but we only have a single slot in Thread objects to store data.