On 03/22/2014 03:15 AM, [email protected] wrote: > I observe that sometimes irq_time only includes "part" of steal_time. > > Like you said, irq_time is in dozens-of-microseconds. In VMs, as all > devices seen are virtual ones, irq_time seems to be not as desired > as it is in physical hosts. > > A quick (but not radical) solution may be: > disable CONFIG_IRQ_TIME_ACCOUNTING if CONFIG_PARAVIRT is selected. > Just adopt tick-based accounting: CONFIG_TICK_CPU_ACCOUNTING > > I am thinking what irq_time really *means* in VMs.
That is not really an option for Linux distributions, which tend to run the same kernel image on the host and in the guest... -- All rights reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
