media: Update media histograms to support PlayReady key system - Used <KeySystem> variant for any PlayReady in hardware secure mode metrics - Simplified explanation about histogram name in about://media-internals#cdms Test : - Ran the following command: `python3 ./tools/metrics/histograms/print_histogram_names.py --diff origin/main` - Result: ``` 25 histograms added: Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.CloseSession Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.FirstInitialize Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.GenerateRequest Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.GetStatusForPolicy Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.LoadSession Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.RemoveSession Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.SetServerCertificate Media.EME.MediaFoundationCdm.PlayReady.HardwareSecure.UpdateSession Media.EME.PlayReady.CdmCapabilityQueryStatus.CreateDummyMediaFoundationCdmHresult Media.EME.PlayReady.CdmCapabilityQueryStatus.MediaFoundationGetCdmFactoryHresult Media.EME.PlayReady.HardwareSecure.AllowedForSite Media.EME.PlayReady.HardwareSecure.CdmCapabilityQueryStatus Media.EME.PlayReady.HardwareSecure.CdmInfoStatus Media.EME.PlayReady.HardwareSecure.Support Media.EME.PlayReady.HardwareSecure.Support.AV1 Media.EME.PlayReady.HardwareSecure.Support.DolbyVision Media.EME.PlayReady.HardwareSecure.Support.H264 Media.EME.PlayReady.HardwareSecure.Support.HEVC Media.EME.PlayReady.HardwareSecure.Support.MPEG2 Media.EME.PlayReady.HardwareSecure.Support.MPEG4 Media.EME.PlayReady.HardwareSecure.Support.Theora Media.EME.PlayReady.HardwareSecure.Support.Unknown Media.EME.PlayReady.HardwareSecure.Support.VC1 Media.EME.PlayReady.HardwareSecure.Support.VP8 Media.EME.PlayReady.HardwareSecure.Support.VP9 2 histograms removed: Media.EME.MediaFoundationService.ClearKey.HardwareSecure.GetCdmCapability Media.EME.MediaFoundationService.ClearKey.HardwareSecure.IsTypeSupported ``` - Note that 2 removed histograms have 0 report. Bug: 378869813, 391657530 Change-Id: I3c5a9b2f4f2c3f83818c4e68d29fbdb48341cdbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6575785 Reviewed-by: Xiaohan Wang <xhwang@chromium.org> Commit-Queue: Sangbaek Park <sangbaekpark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1464458}
ChromiumChromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.