From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: [PATCH 1/5] Skip timer works.patch Date: Mon, 30 Oct 2006 15:09:20 -0800 Message-ID: <45468620.5060805@vmware.com> References: <200610200009.k9K09MrS027558@zach-dev.vmware.com> <20061027145650.GA37582@muc.de> <45425976.3090508@vmware.com> <200610271416.12548.ak@suse.de> <4546669F.8020706@vmware.com> <20061030225016.GA95732@muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20061030225016.GA95732@muc.de> Sender: linux-kernel-owner@vger.kernel.org To: Andi Kleen Cc: Andi Kleen , virtualization@lists.osdl.org, Andrew Morton , Chris Wright , Linux Kernel Mailing List List-Id: virtualization@lists.linuxfoundation.org Andi Kleen wrote: > On Mon, Oct 30, 2006 at 12:54:55PM -0800, Zachary Amsden wrote: > >> Andi Kleen wrote: >> >>> no_timer_check. But it's only there on x86-64 in mainline - although there >>> were some patches to add it to i386 too. >>> >>> >> I can rename to match the x86-64 name. >> > > I will do that in my tree. > > >>>> That is what this patch is building towards, but the boot option is >>>> "free", so why not? In the meantime, it helps non-paravirt kernels >>>> booted in a VM. >>>> >>>> >>> Hmm, you meant they paniced before? If they just fail a few tests >>> that is not particularly worrying (real hardware does that often too) >>> >>> >> Yes, they sometimes fail to boot, and the failure message used to ask us >> to pester mingo. >> > > I still think we should figure that out automatically. Letting > the Hypervisor pass magic boot options seems somehow unclean. > > But i suppose it will only work for the paravirtualized case, > not for the case of kernel running "native" under a hypervisor > I suppose? Or does that one not panic? > That is the one that can panic, for now. Fixing the paravirtualized case is easy, but we can't assume paravirtualization just yet. Zach