From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HeGTz-0002Pq-F9 for qemu-devel@nongnu.org; Wed, 18 Apr 2007 16:10:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HeGTx-0002PS-25 for qemu-devel@nongnu.org; Wed, 18 Apr 2007 16:10:26 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HeGTw-0002PP-TY for qemu-devel@nongnu.org; Wed, 18 Apr 2007 16:10:24 -0400 Received: from wr-out-0506.google.com ([64.233.184.239]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HeGP4-0003qV-Ig for qemu-devel@nongnu.org; Wed, 18 Apr 2007 16:05:22 -0400 Received: by wr-out-0506.google.com with SMTP id i20so486991wra for ; Wed, 18 Apr 2007 13:05:21 -0700 (PDT) Message-ID: Date: Wed, 18 Apr 2007 22:05:21 +0200 From: "andrzej zaborowski" Sender: balrogg@gmail.com Subject: Re: [Qemu-devel] Qemu / KQemu on 64-bit (x86_64) host systems In-Reply-To: <46267504.5080101@t-online.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46231BEB.5070402@t-online.de> <46251321.5050803@t-online.de> <46267504.5080101@t-online.de> Reply-To: balrogg@gmail.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Werner Dittmann Cc: qemu-devel@nongnu.org Hi, On 18/04/07, Werner Dittmann wrote: > Andrzej, > > just another remark: after setting the kernel parameter to "notsc" > the kernel now detects the CPU correctly. Without this setting the > CPU detetion was wrong (displays the wrong CPU type, frequency, etc). > Are there any know side-effects if notsc (no time stamp counter) is > set? I don't know what clocksource is chosen with "notsc", it may be forgettably slower one (but not necessarily). What do you mean by wrong CPU? Apparently this is the same SMP issue I described in http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00652.html so it's not x86_64 related. If you apply the patch from that post, you can skip "notsc". Regards, Andrzej