From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HeYaY-0006RL-7d
	for qemu-devel@nongnu.org; Thu, 19 Apr 2007 11:30:26 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HeYaW-0006PB-Ji
	for qemu-devel@nongnu.org; Thu, 19 Apr 2007 11:30:25 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HeYaW-0006Op-BW
	for qemu-devel@nongnu.org; Thu, 19 Apr 2007 11:30:24 -0400
Received: from mailout03.sul.t-online.com ([194.25.134.81])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <Werner.Dittmann@t-online.de>) id 1HeYVY-0003gi-BH
	for qemu-devel@nongnu.org; Thu, 19 Apr 2007 11:25:16 -0400
Message-ID: <462789D3.9030202@t-online.de>
Date: Thu, 19 Apr 2007 17:25:07 +0200
From: Werner Dittmann <Werner.Dittmann@t-online.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Qemu / KQemu on 64-bit (x86_64) host systems
References: <46231BEB.5070402@t-online.de>	<fb249edb0704162205xa0133a7m5e48cadfbecf065c@mail.gmail.com>	<46251321.5050803@t-online.de>	<fb249edb0704171302p66d26dcwb356b6f1a6fe8d8@mail.gmail.com>	<46267504.5080101@t-online.de>
	<fb249edb0704181305w33527d7ao5cfb0ac837e72fc@mail.gmail.com>
In-Reply-To: <fb249edb0704181305w33527d7ao5cfb0ac837e72fc@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: balrogg@gmail.com, qemu-devel@nongnu.org

Andrzej,

the guest Linux system reported some AMD CPU type (can't remember
which one) which is not in my system. Now when the guest Linux starts
is correctly reports: CPU 0 AMD X2 4200+ ....

Regards,
Werner

andrzej zaborowski wrote:
> Hi,
> 
> On 18/04/07, Werner Dittmann <Werner.Dittmann@t-online.de> 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
> 
> 
>