On Tue, Feb 05, 2013 at 03:49:41PM -0600, Michael Wolf wrote: > Add a helper routine to scheduler/core.c to allow the kvm module > to retrieve the cpu hardlimit settings. The values will be used > to set up a timer that is used to separate the consigned from the > steal time. 1) Can you please describe, in english, the mechanics of subtracting cpu hardlimit values from steal time reported via run_delay supposed to work? "The period and the quota used to separate the consigned time (expected steal) from the steal time are taken from the cfs bandwidth control settings. Any other steal time accruing during that period will show as the traditional steal time." There is no "expected steal time" over a fixed period of real time. 2) From the description of patch 1: "In the case of where you have a system that is running in a capped or overcommitted environment the user may see steal time being reported in accounting tools such as top or vmstat." This is outdated, right? Because overcommitted environment is exactly what steal time should report. Thanks -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
