| 6b3dd70b1f92b6728396dc36bb263b68eeaebae5 |
|
26-Jan-2018 |
Android Build Merger (Role) <noreply-android-build-merger@google.com> |
Merge "Merge "ActivityManager: Add support for agents on startup" am: d5cba89b98 am: ebc0afd811" into oc-mr1-dev-plus-aosp
am: 954ba2c6a1
Change-Id: I218eb054ef0da896c72674c597249c6a5120500d
|
| 5b495d54d3831bd1a72309643f724958e814c90c |
|
23-Jan-2018 |
Andreas Gampe <agampe@google.com> |
ActivityManager: Add support for agents on startup
Add setAgentApp similar to setDebugApp. If given, attempt to attach the given
agent during handleBindApplication.
The flow needed a slight refactor. It is not possible to do a debuggability
check at setAgentApp time (without checking all installed apps). Instead,
when a ProfilerInfo contains an agent, perform a debuggability check then.
This is consistent with how setDebugApp works.
Expose through the shell command:
cmd activity set-agent-app process agent
Add CTS coverage.
Bug: 69929492
Test: m
Test: m cts
Test: cts-tradefed run commandAndExit cts-dev -m CtsJvmtiAttachingHostTestCases
Change-Id: I65e869debd45e6073f9ab21cb9de9c9deb828a2e
/frameworks/base/core/java/android/app/ProfilerInfo.java
|
| 148d7f4291d675fc17852d530be32b7dba06fc93 |
|
28-Nov-2017 |
Yi Jin <jinyithu@google.com> |
Implement activity --proto --processes
Bug: 66729158
Test: out/host/linux-x86/bin/incident_report -w amprocesses
Change-Id: Iae043203bca954bfc4aadad0460cc56621e9ba05
/frameworks/base/core/java/android/app/ProfilerInfo.java
|
| e8e016838a9088606bd1a6de565162544ebad3fc |
|
16-Jan-2018 |
Andreas Gampe <agampe@google.com> |
Merge "ActivityThread: Attempt to attach agent with app's classloader" am: f779d7e3be am: 9f1f950c31
am: 9853a65386
Change-Id: I064033ab86013dd80efa3cb4eb22b89ac143e7b6
|
| ab8a63be6afc428a752828f9ea6423047cd27e42 |
|
05-Jan-2018 |
Andreas Gampe <agampe@google.com> |
ActivityThread: Attempt to attach agent with app's classloader
Try to use the app's (main) classloader when an attach-agent request
is handled. If that fails, retry without a classloader.
Add bind-application-time flag to ProfilerInfo. Use the flag to have
a second attach-agent point on app startup. Add --attach-agent-bind
to cmd activity start to expose the difference between pre-bind and
bind-time attaching.
Bug: 70901841
Test: m
Test: cts-tradefed run commandAndExit cts-dev -m CtsJvmtiAttachingHostTestCases
Change-Id: I21698ec3be43a6d095d577100b2adfb22daca7d5
/frameworks/base/core/java/android/app/ProfilerInfo.java
|
| 6b9d3a1400fea76f7c6be535b332a27cb21522b3 |
|
16-Nov-2017 |
Andrii Kulian <akulian@google.com> |
Add transaction unit tests
Bug: 64797980
Test: android.app.servertransaction.ClientTransactionTests
Test: android.app.servertransaction.TransactionParcelTests
Change-Id: I108bacc819e9d43d0a2f5a30338ae88674a53239
/frameworks/base/core/java/android/app/ProfilerInfo.java
|
| 83085bb3dde17264025bb1ef8427de2184009fef |
|
27-Jun-2017 |
Andreas Gampe <agampe@google.com> |
Frameworks: Add agent to ProfilerInfo
Add an agent option to ProfilerInfo. If set, on bindApplication
attempt to attach the given agent to the app before loading the
app itself.
Bug: 62445317
Test: m
Test: Device boots
Test: Manual profiling tests
Test: cts/hostsidetests/services/activityandwindowmanager/util/run-test CtsServicesHostTestCases android.server.cts.ActivityManagerAmProfileTests
Test: Manual agent test
Test: cts-tradefed run commandAndExit cts-dev --module CtsJvmtiAttachingHostTestCases
Change-Id: I1f0c4121e22351fd3a964dd0a915100a620d4f84
/frameworks/base/core/java/android/app/ProfilerInfo.java
|
| 2b073a0e897a7f48be6fc4e915e4171b7bdfb2b9 |
|
23-Jun-2017 |
Andreas Gampe <agampe@google.com> |
Frameworks: Clean up ProfilerInfo
Use a ProfilerInfo object in ActivityManagerService to reduce the
number of exposed fields. In preparation for adding an agent during
startup.
Bug: 62445317
Test: m
Test: Device boots
Test: Manual test for profiling
Test: cts/hostsidetests/services/activityandwindowmanager/util/run-test CtsServicesHostTestCases android.server.cts.ActivityManagerAmProfileTests
Change-Id: I5fa347ded760c263a8ce3754bb2631205ea7b4b8
/frameworks/base/core/java/android/app/ProfilerInfo.java
|
| 6ffd4f9bab6b4c83f40caa6455664c6e6aadc6df |
|
26-Jan-2017 |
Shukang Zhou <shukang@google.com> |
[Frameworks] Add an 'am' cmd option to enable streaming in profiling.
Add option '--streaming' to 'am start' and 'am profile' commands.
If the option is given, the output of method trace profiling
will be streamed into the specified file, so the output is no
longer limited by the buffer size.
Test: m -j48 test-art-host;
m -j48 ART_TEST_TRACE=true ART_TEST_TRACE_STREAM=true test-art-host;
I also tested manually. Tried all 8 combinations of
sampling/instrumention
streaming/non-streaming
'am start --start-profiler' / 'am profile start'
The output files are all in expected shape.
Bug: 33300765
Change-Id: I8a5136a1c7330c8260b7c6c8da63f42a73aee275
/frameworks/base/core/java/android/app/ProfilerInfo.java
|
| 1b012d302b56b4adf950035136d1d191a1936d5a |
|
20-Aug-2014 |
Jeff Hao <jeffhao@google.com> |
Add sample profiling option to am.
Also bundles all profiling options into a class.
Bug: 17040932
Change-Id: I85d675ee1494bdc7308caffdf94145d27c996e9d
/frameworks/base/core/java/android/app/ProfilerInfo.java
|