Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761537AbYCDGiR (ORCPT ); Tue, 4 Mar 2008 01:38:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750884AbYCDGiE (ORCPT ); Tue, 4 Mar 2008 01:38:04 -0500 Received: from ozlabs.org ([203.10.76.45]:53467 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750771AbYCDGiD (ORCPT ); Tue, 4 Mar 2008 01:38:03 -0500 From: Rusty Russell To: Ingo Molnar Subject: Re: [BUG + PATCH/Bugfix] x86/lguest: fix pgdir pmd index calculation Date: Tue, 4 Mar 2008 17:37:24 +1100 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: "Ahmed S. Darwish" , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , LKML , lguest@ozlabs.org, akpm , Jeremy Fitzhardinge References: <20080224155515.GA24831@ubuntu> <20080229003224.GA18821@ubuntu> <20080229195838.GB21494@elte.hu> In-Reply-To: <20080229195838.GB21494@elte.hu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200803041737.24988.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1208 Lines: 29 On Saturday 01 March 2008 06:58:38 Ingo Molnar wrote: > * Ahmed S. Darwish wrote: > > On the lguest _guest_ side, 'cpu_has_tsc' is _always_ false (due to > > lguest using his own clocksource ?), thus a guest with a pentium+ cpu > > always panics with: > > does the "RDTSC" instruction work in an lguest guest? If not, then the > lguest kernel is correct in not exposing it - and then the solution is > to build a non-TSC guest kernel. Does the patch below help? > > but if the RDTSC instruction does work in an lguest guest, then the > proper approach would be to expose it in the CPU features. > > Ingo It does (assuming host support), but when I tried to use the normal TSC code it poked at other things which a guest couldn't do. Currently I've hit another issue, but revisiting this is on my TODO. The cpu_has_tsc panic is overzealous, since we deal without it, but it'd be nice to use the common TSC clock code. Thanks, Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/