Add UMA stats to get the quality of service of memory pressure handling scheme in ChromeOS.

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 24890235bf659df419fc56dfc6d3ab4c177587ef..a7f3315a276da72dc16962eef2f4d074611c441e 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -2701,6 +2701,16 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   </summary>
 </histogram>
 
+<histogram name="ChromeOS.MemoryPressureLevel"
+    enum="ChromeOSMemoryPressureLevel">
+  <owner>xdai@chromium.org</owner>
+  <summary>
+    The memory pressure level in ChromeOS, which is recorded periodically (once
+    per second). This is used to show the relative frequency of the system being
+    in a critical vs relaxed memory pressure state.
+  </summary>
+</histogram>
+
 <histogram name="ChromeOS.PlatformVerification.Available"
     enum="BooleanAvailable">
   <owner>dkrahn@chromium.org</owner>
@@ -43920,6 +43930,12 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <int value="3" label="Reading"/>
 </enum>
 
+<enum name="ChromeOSMemoryPressureLevel" type="int">
+  <int value="0" label="No memory pressure"/>
+  <int value="1" label="Medium memory pressure"/>
+  <int value="2" label="High memory pressure"/>
+</enum>
+
 <enum name="ChromeOSPlatformVerificationResult" type="int">
   <summary>
     Possible results of a platform verification attempt. See