[System Monitor] dockyard_host: report total system memory on connection
To improve testing of the full path of the data, this CL adds a query for the device memory to the dockyard_host. It does so by setting up proper callbacks and waiting for the device connection prior to making the request. Bug: 9 Test: dockyard_host_test Change-Id: I334a99a2190ce7eab849b9742cce5d92b205ad5a
Showing
- garnet/bin/system_monitor/dockyard_host/BUILD.gn 14 additions, 1 deletiongarnet/bin/system_monitor/dockyard_host/BUILD.gn
- garnet/bin/system_monitor/dockyard_host/dockyard_host.cc 56 additions, 16 deletionsgarnet/bin/system_monitor/dockyard_host/dockyard_host.cc
- garnet/bin/system_monitor/dockyard_host/dockyard_host.h 43 additions, 0 deletionsgarnet/bin/system_monitor/dockyard_host/dockyard_host.h
- garnet/bin/system_monitor/dockyard_host/dockyard_main.cc 28 additions, 0 deletionsgarnet/bin/system_monitor/dockyard_host/dockyard_main.cc
- garnet/bin/system_monitor/dockyard_host/tests/BUILD.gn 22 additions, 0 deletionsgarnet/bin/system_monitor/dockyard_host/tests/BUILD.gn
- garnet/bin/system_monitor/dockyard_host/tests/dockyard_fake.cc 67 additions, 0 deletions...t/bin/system_monitor/dockyard_host/tests/dockyard_fake.cc
- garnet/bin/system_monitor/dockyard_host/tests/dockyard_host_test.cc 40 additions, 0 deletions.../system_monitor/dockyard_host/tests/dockyard_host_test.cc
- garnet/bin/system_monitor/harvester/harvester.cc 2 additions, 1 deletiongarnet/bin/system_monitor/harvester/harvester.cc
- garnet/lib/system_monitor/dockyard/BUILD.gn 7 additions, 0 deletionsgarnet/lib/system_monitor/dockyard/BUILD.gn
- garnet/lib/system_monitor/dockyard/dockyard.cc 35 additions, 11 deletionsgarnet/lib/system_monitor/dockyard/dockyard.cc
- garnet/lib/system_monitor/dockyard/dockyard.h 21 additions, 6 deletionsgarnet/lib/system_monitor/dockyard/dockyard.h
- garnet/packages/tests/BUILD.gn 2 additions, 1 deletiongarnet/packages/tests/BUILD.gn
Loading
Please register or sign in to comment