On 02/17/2011 12:29 PM, Nadav Har'El wrote:
I guess I should be more worried why I got all these PIOs in L2 in the first place - the MSR reads and writes in L1 were just an odd consequence of that. It turns out that the "ping -f" workload I was running in L2 insisted to get accurate timings of each packet, and this, I'm not still sure why, caused a ACPI PM_TIMER PIO for each packet. I guess that normal workloads won't use the timer on every packet, so that shouldn't matter.
Strange, isn't kvmclock exposed to L2? -- error compiling committee.c: too many arguments to function -- 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
