From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Erratic gettimeofday() behavior with KVM and newer Linux kernels? Date: Tue, 19 Jun 2007 10:14:26 -0500 Message-ID: <4677F2D2.8060703@codemonkey.ws> References: <4676F587.8030802@codemonkey.ws> <46778917.90803@qumranet.com> <4677E4BF.3060000@codemonkey.ws> <4677E5B8.3070208@qumranet.com> <4677E8D4.6010904@codemonkey.ws> <4677EDF9.3000202@qumranet.com> <4677F04F.7070005@codemonkey.ws> <4677F14C.8000701@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Avi Kivity Return-path: In-Reply-To: <4677F14C.8000701-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Avi Kivity wrote: > Anthony Liguori wrote: >> >> It's less stable then I thought. > > less stable? less unstable? It didn't fix the problem :-) >> You were right btw, the guest is deciding the TSC is too unreliable. >> It happens every once and while (although the taskset/no pm timer >> combination helps a whole lot). >> > > Well, the guest is right too. The tsc is unreliable in a virtualized > environment. There's nothing we can do about it except provide a > paravirtualized timer for the guests that will support it. Yeah, I just moved the paravirt-clock patch higher in the patch series so that I didn't have to worry about it anymore. Regards, Anthony Liguori ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/