/proc 2.6.24 changes for guest CPU accounting

From: Michael Kerrisk
Date: Mon Jun 23 2008 - 04:03:26 EST


Hi Laurent,

A note and patch from Samuel alerted me to your commits
9ac52315d4cf5f561f36dabaf0720c00d3553162 and
5e84cfde51cf303d368fcb48f22059f37b3872de, which in 2.6.24 changed /proc/stat
and /proc/PID/stat. Would you please CC me on kernel-userspace interface
changes, so that they have a chance of getting documented in man-pages.

(I see that Andrew P tried to get something added to
Documentation/filesystems/proc.txt, but that doesn't seem to have made it in.)

Below is a patch against the proc.5 man page by Samuel and I to document these
changes. Do the changes look okay to you? The first part is the change for
/proc/<pid>/stat, and the other is for /proc/stat.

Cheers,

Michael



===================================================================
--- proc.5 (revision 4046)
+++ proc.5 (working copy)
@@ -753,6 +753,13 @@
.TP
\fIdelayacct_blkio_ticks\fP %llu (since Linux 2.6.18)
Aggregated block I/O delays, measured in clock ticks (centiseconds).
+.TP
+\fIguest_time\fP %lu (since Linux 2.6.24)
+Guest time of the process (time spent running a virtual CPU
+for a guest operating system), in centiseconds.
+.TP
+\fIcguest_time\fP %ld (since Linux 2.6.24)
+Guest time of the process's children, in centiseconds.
.RE
.TP
.I /proc/[number]/statm
@@ -1510,6 +1517,12 @@
.I steal
\- stolen time, which is the time spent in other operating systems when
running in a virtualized environment
+
+Since Linux 2.6.24, there is a ninth column,
+.IR guest ,
+which is the time spent running a virtual CPU for guest
+operating systems under teh control of the Linux kernel.
+.\" See Changelog entry for 5e84cfde51cf303d368fcb48f22059f37b3872de
.TP
\fIpage 5741 1808\fP
The number of pages the system paged in and the number that were paged



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/