From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: memtest 4.20+ does not work with -cpu host
Date: Thu, 13 Sep 2012 10:00:26 +0200
Message-ID: <5051929A.2060407@redhat.com>
References: <5048BA0F.3070300@redhat.com> <504DC9BC.1060407@dlhnet.de>
	<504DCF1A.1@redhat.com> <504DD483.6050104@dlhnet.de>
	<504DD9F5.2040300@redhat.com> <20120910122120.GA20907@redhat.com>
	<504DDD37.5000804@dlhnet.de> <504DDDDA.9040001@redhat.com>
	<505190E5.9080008@dlhnet.de> <5051915A.2050405@redhat.com>
	<20120913075734.GX20907@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "H. Peter Anvin" <hpa@zytor.com>, Peter Lieven <pl@dlhnet.de>,
	Avi Kivity <avi@redhat.com>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
To: Gleb Natapov <gleb@redhat.com>
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
In-Reply-To: <20120913075734.GX20907@redhat.com>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
List-Id: kvm.vger.kernel.org

Il 13/09/2012 09:57, Gleb Natapov ha scritto:
>>> > > 
>>> > > #rdmsr -0 0x194
>>> > > 0000000000011100
>>> > > #rdmsr -0 0xce
>>> > > 00000c0004011103
>> > 
>> > Yes, that can help implementing it in KVM.  But without a spec to
>> > understand what the bits actually mean, it's just as risky...
>> > 
>> > Peter, do you have any idea where to get the spec of the memory
>> > controller MSRs in Nehalem and newer processors?  Apparently, memtest is
>> > using them (and in particular 0x194) to find the speed of the FSB, or
>> > something like that.
>> > 
> Why would anyone will want to run memtest in a vm? May be just add those
> MSRs to ignore list and that's it.

>>From the output it looks like it's basically a list of bits.  Returning
something sensible is better, same as for the speed scaling MSRs.

Paolo