From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arjan Koers <0h61vkll2ly8@xutrox.com>
Subject: Re: 2.6.35-rc1 regression with pvclock and smp guests
Date: Sat, 31 Jul 2010 13:50:40 +0200
Message-ID: <4C540E10.6060103@xutrox.com>
References: <4C4D4B8B.80006@amd.com> <4C4DDB00.50203@xutrox.com> <4C4F48D0.8090609@xutrox.com> <4C500872.1020809@redhat.com> <4C536F80.5090205@xutrox.com> <4C537E98.7000704@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>
To: Zachary Amsden <zamsden@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from smtp-out1.tiscali.nl ([195.241.79.176]:43009 "EHLO
	smtp-out1.tiscali.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755541Ab0GaLur (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sat, 31 Jul 2010 07:50:47 -0400
In-Reply-To: <4C537E98.7000704@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 2010-07-31 03:38, Zachary Amsden wrote:
> 
> How are you printing shadow.version?  From a local variable captured
> during the barrier window or directly in a printk afterwards?  If should
> never go backwards like this, and the vcpus come from a zalloc.  This is
> not easily explainable by anything other than a memory ordering or
> compiler issue.

I'm reading shadow.version after the do-while loop and storing it in
an array to print it after the kernel finishes booting. I had to defer
my debug printk's, because they were affecting the results.