HomeSort by relevance Sort by last modified time
    Searched refs:attaching (Results 1 - 9 of 9) sorted by null

  /cts/tests/tests/jvmti/attaching/jni/
Android.mk 21 define jvmti-attaching-test-agent
41 $(eval $(call jvmti-attaching-test-agent,1))
42 $(eval $(call jvmti-attaching-test-agent,2))
43 $(eval $(call jvmti-attaching-test-agent,3))
44 $(eval $(call jvmti-attaching-test-agent,4))
  /art/runtime/ti/
agent.cc 62 VLOG(agents) << "Attaching agent: " << name_ << " " << args_;
69 bool attaching,
83 AgentOnLoadFunction callback = attaching ? agent->onattach_ : agent->onload_;
86 (attaching ? "attach" : "load"),
agent.h 73 bool attaching,
  /cts/tests/tests/jvmti/attaching/src/android.jvmti.attaching.cts/
AttachingTest.java 17 package android.jvmti.attaching.cts;
  /external/libunwind/doc/
libunwind-ptrace.tex 71 directly attaching to an already running process (via
  /external/autotest/client/cros/
cros_disks.py 643 None if no loop device is attaching the image file.
700 logging.debug('Attaching image file "%s" to loop device',
  /external/tensorflow/tensorflow/contrib/verbs/
README.md 30 3. Following HKUST research on the use of GPU direct, and their [GDR implementation](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/gdr/README.md), there is a smart way to benefit from the TensorFlow allocation theme which is mostly pool based, i.e allocators pre-allocate a large memory block, and allocate the tensors from there. By attaching a custom Visitor to relevant allocators, we can do a single registration of the entire memory block, which zeros the registration overhead. Once the block is registered, each new tensor allocated will be at a registered address, which will allow us to do direct RDMA writes to it.
  /external/syzkaller/pkg/compiler/
check.go 507 // But that will require attaching dir to individual fields.
  /external/syzkaller/vendor/google.golang.org/api/compute/v0.beta/
compute-gen.go     [all...]

Completed in 551 milliseconds