From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/6] KVM: In kernel pit model Date: Fri, 07 Mar 2008 11:57:29 +0200 Message-ID: <47D11189.4030508@qumranet.com> References: <200803041822.44757.sheng.yang@intel.com> <200803071612.12182.sheng.yang@intel.com> <47D10294.5050400@qumranet.com> <200803071714.51252.sheng.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net To: "Yang, Sheng" Return-path: In-Reply-To: <200803071714.51252.sheng.yang@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Yang, Sheng wrote: > On Friday 07 March 2008 16:53:40 Avi Kivity wrote: > >> Yang, Sheng wrote: >> >>> Found more complex for KVM. Xen pulled pm timer down to kernel part, and >>> used the guest TSC as source. So only adjust TSC is OK for it. But we are >>> still using pm timer in QEmu, which using host time as source. So even we >>> pull back TSC, the problem still exists, for 2.6.9 prefer to pm timer by >>> default >>> >> Interesting. I guess we should pull the pm timer into the kernel as >> well. Timing is too tricky for userspace. >> > > ... Should we suggest using "clock=pit" on pae 2.6.9 at first? > > While it is hardly a lovely solution (things should work out of the box) it is reasonable as a temporary measure. Can you repost your patchset? If you're quick I can apply it today, otherwise it will have to wait until next week. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/