From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: memtest 4.20+ does not work with -cpu host Date: Thu, 13 Sep 2012 09:55:06 +0200 Message-ID: <5051915A.2050405@redhat.com> References: <5034F587.4000403@dlhnet.de> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Gleb Natapov , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , "H. Peter Anvin" To: Peter Lieven Return-path: Received: from mx1.redhat.com ([209.132.183.28]:10945 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754879Ab2IMHzN (ORCPT ); Thu, 13 Sep 2012 03:55:13 -0400 In-Reply-To: <505190E5.9080008@dlhnet.de> Sender: kvm-owner@vger.kernel.org List-ID: Il 13/09/2012 09:53, Peter Lieven ha scritto: >>>> >>> rdmsr returns it cannot read those MSRs. regardless if I use -cpu host >>> or -cpu qemu64. >> On the host. >> >> > did you get my output? > > #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. Paolo