| commit | 8d5d761a7afc59fe9ab870b3c8a3aa4db3ac7bb3 | |
| author | mcgrathr@chromium.org <mcgrathr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 20 Oct 2011 18:23:14 +0000 (20 18:23 +0000) | ||
| committer | mcgrathr@chromium.org <mcgrathr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 20 Oct 2011 18:23:14 +0000 (20 18:23 +0000) | ||
| tree | 818a91df8b32fe639ee942312fecae4c16edf3a2 | treesnapshot (tar.gz zip) |
| parent | 94b623e2ac73138f6f863b153829d5efb7c61a3e | commitdiff |
Add UMA reports for Linux nacl_helper startup status
This extends the Linux Zygote Fork request protocol so the Zygote process
can return a UMA histogram enumeration report to be made, along with the
PID. In the Zygote process, the ZygoteForkDelegate decides what to report.
It gets to choose an initial report to make, which happens on the first
fork request that doesn't have its own report to make (as a generic fork
for a renderer won't). It also gets to choose a report to make with each
individual fork request.
We then use this in the NaClForkDelegate to report status about the attempt
to start up the nacl_helper process. We both make an initial report, so we
can collect this information from every Chrome instance, and make a report
repeating the same information on each NaCl process fork request, so that
we can correlate the nacl_helper startup success/failure rates with
sessions that actually make use of NaCl.
BUG= http://code.google.com/p/nativeclient/issues/detail?id=2361
TEST= looked at about:histograms/NaCl
R=agl@chromium.org,bradchen@google.com,ncbray@google.com
Review URL: http://codereview.chromium.org/8342017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106529 0039d316-1c4b-4281-b951-d872f2087c98
This extends the Linux Zygote Fork request protocol so the Zygote process
can return a UMA histogram enumeration report to be made, along with the
PID. In the Zygote process, the ZygoteForkDelegate decides what to report.
It gets to choose an initial report to make, which happens on the first
fork request that doesn't have its own report to make (as a generic fork
for a renderer won't). It also gets to choose a report to make with each
individual fork request.
We then use this in the NaClForkDelegate to report status about the attempt
to start up the nacl_helper process. We both make an initial report, so we
can collect this information from every Chrome instance, and make a report
repeating the same information on each NaCl process fork request, so that
we can correlate the nacl_helper startup success/failure rates with
sessions that actually make use of NaCl.
BUG= http://code.google.com/p/nativeclient/issues/detail?id=2361
TEST= looked at about:histograms/NaCl
R=agl@chromium.org,bradchen@google.com,ncbray@google.com
Review URL: http://codereview.chromium.org/8342017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106529 0039d316-1c4b-4281-b951-d872f2087c98