qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Lieven <pl@dlhnet.de>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
Date: Mon, 10 Sep 2012 15:12:58 +0300	[thread overview]
Message-ID: <504DD94A.2030703@redhat.com> (raw)
In-Reply-To: <504DCF1A.1@redhat.com>

On 09/10/2012 02:29 PM, Paolo Bonzini wrote:
> Il 10/09/2012 13:06, Peter Lieven ha scritto:
>> 
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason MSR_READ rip
>> 0x11478 info 0 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_msr: msr_read 194 = 0x0 (#GP)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_inj_exception: #GP (0x0)
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_entry: vcpu 0
>> qemu-kvm-1.0.1-5107 [007] 410771.148000: kvm_exit: reason TRIPLE_FAULT
>> rip 0x11478 info 0 0
> 
> Memory controller MSR:
> 
> static float getNHMmultiplier(void)
> {
>         unsigned int msr_lo, msr_hi;
>         float coef;
> 
>         /* Find multiplier (by MSR) */
>         /* First, check if Flexible Ratio is Enabled */
>         rdmsr(0x194, msr_lo, msr_hi);
>         if((msr_lo >> 16) & 1){
>                 coef = (msr_lo >> 8) & 0xFF;
>          } else {
>                 rdmsr(0xCE, msr_lo, msr_hi);
>                 coef = (msr_lo >> 8) & 0xFF;
>          }
> 
>         return coef;
> }
> 

The SDM only mentions 0x194 as a machine check exception register
(recorded R12).

In the Architectural MSRs (how I love that name) section 18AH-197H are
listed as reserved.

In the Nehalem section they're not there at all.



-- 
error compiling committee.c: too many arguments to function

      parent reply	other threads:[~2012-09-10 12:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 15:06 [Qemu-devel] memtest 4.20+ does not work with -cpu host Peter Lieven
2012-09-06 14:58 ` Avi Kivity
2012-09-10 11:06   ` Peter Lieven
2012-09-10 11:29     ` Paolo Bonzini
2012-09-10 11:47       ` Peter Lieven
2012-09-10 11:52       ` Peter Lieven
2012-09-10 12:15         ` Paolo Bonzini
2012-09-10 12:21           ` Gleb Natapov
2012-09-10 12:29             ` Peter Lieven
2012-09-10 12:32               ` Avi Kivity
2012-09-10 12:38                 ` Peter Lieven
2012-09-13  7:53                 ` Peter Lieven
2012-09-13  7:55                   ` Paolo Bonzini
2012-09-13  7:57                     ` Gleb Natapov
2012-09-13  8:00                       ` Paolo Bonzini
2012-09-13  8:05                         ` Gleb Natapov
2012-09-13 12:05                           ` Peter Lieven
2012-09-13 12:42                             ` Gleb Natapov
2012-09-13 12:56                               ` Peter Lieven
2012-09-13 13:43                                 ` Gleb Natapov
2012-09-10 12:12       ` Avi Kivity [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=504DD94A.2030703@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pl@dlhnet.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).