VAVDA: Use the new, generic video decoder and accelerator infrastructure.

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 87f4b7b235fae97080c8cf90cb881c4a90aea48e..60ab29dd6a3fc8c75e6c64c4c7145bb799a29f92 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -14038,7 +14038,17 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   </summary>
 </histogram>
 
+<histogram name="Media.VAVDA.DecoderFailure" enum="VAVDADecoderFailure">
+  <owner>posciak@chromium.org</owner>
+  <summary>
+    Error codes reported by video decode using VA-API hardware video decoder.
+  </summary>
+</histogram>
+
 <histogram name="Media.VAVDAH264.DecoderFailure" enum="VAVDAH264DecoderFailure">
+  <obsolete>
+    Deprecated as of 4/2015, partially replaced by Media.VAVDA.DecoderFailure.
+  </obsolete>
   <owner>posciak@chromium.org</owner>
   <summary>
     Error codes reported by video decode using VA-API hardware video decoder.
@@ -61613,6 +61623,10 @@ To add a new entry, add it with any value and run test to compute valid value.
   <int value="2" label="Other"/>
 </enum>
 
+<enum name="VAVDADecoderFailure" type="int">
+  <int value="0" label="VAAPI_ERROR"/>
+</enum>

[Ilya Sherman, 2015/03/30 05:11:47]

Hmm, is it really useful to have this histogram that has only a single bucket in
it?  How do you anticipate interpreting the data?  It's typically best to
compare quantities against each other, i.e. to identify a baseline.

+
 <enum name="VAVDAH264DecoderFailure" type="int">
   <int value="0" label="FRAME_MBS_ONLY_FLAG_NOT_ONE"/>
   <int value="1" label="GAPS_IN_FRAME_NUM"/>