From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Why exit on MSR_STAR and friends? Date: Thu, 17 Feb 2011 12:39:26 +0200 Message-ID: <4D5CFADE.3050108@redhat.com> References: <20110216151706.GA21823@fermat.math.technion.ac.il> <4D5CE8BC.8020306@redhat.com> <20110217102935.GA19369@fermat.math.technion.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, mtosatti@redhat.com To: "Nadav Har'El" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:27156 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752337Ab1BQKje (ORCPT ); Thu, 17 Feb 2011 05:39:34 -0500 In-Reply-To: <20110217102935.GA19369@fermat.math.technion.ac.il> Sender: kvm-owner@vger.kernel.org List-ID: 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