From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Lieven <pl@dlhnet.de>, Avi Kivity <avi@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: memtest 4.20+ does not work with -cpu host
Date: Thu, 13 Sep 2012 11:05:29 +0300 [thread overview]
Message-ID: <20120913080529.GY20907@redhat.com> (raw)
In-Reply-To: <5051929A.2060407@redhat.com>
On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> 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.
>
Everything is list of bits in computers :) At least 0xce is documented in SDM.
It cannot be implemented in a migration safe manner.
--
Gleb.
WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
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>
Subject: Re: [Qemu-devel] memtest 4.20+ does not work with -cpu host
Date: Thu, 13 Sep 2012 11:05:29 +0300 [thread overview]
Message-ID: <20120913080529.GY20907@redhat.com> (raw)
In-Reply-To: <5051929A.2060407@redhat.com>
On Thu, Sep 13, 2012 at 10:00:26AM +0200, Paolo Bonzini wrote:
> 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.
>
Everything is list of bits in computers :) At least 0xce is documented in SDM.
It cannot be implemented in a migration safe manner.
--
Gleb.
next prev parent reply other threads:[~2012-09-13 8:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 15:06 memtest 4.20+ does not work with -cpu host Peter Lieven
2012-08-22 15:06 ` [Qemu-devel] " Peter Lieven
2012-09-06 14:58 ` Avi Kivity
2012-09-06 14:58 ` [Qemu-devel] " Avi Kivity
2012-09-10 11:06 ` Peter Lieven
2012-09-10 11:06 ` [Qemu-devel] " Peter Lieven
2012-09-10 11:29 ` Paolo Bonzini
2012-09-10 11:29 ` [Qemu-devel] " Paolo Bonzini
2012-09-10 11:47 ` Peter Lieven
2012-09-10 11:47 ` [Qemu-devel] " Peter Lieven
2012-09-10 11:52 ` Peter Lieven
2012-09-10 11:52 ` [Qemu-devel] " Peter Lieven
2012-09-10 12:15 ` Paolo Bonzini
2012-09-10 12:15 ` [Qemu-devel] " Paolo Bonzini
2012-09-10 12:21 ` Gleb Natapov
2012-09-10 12:21 ` [Qemu-devel] " Gleb Natapov
2012-09-10 12:29 ` Peter Lieven
2012-09-10 12:29 ` [Qemu-devel] " Peter Lieven
2012-09-10 12:32 ` Avi Kivity
2012-09-10 12:32 ` [Qemu-devel] " Avi Kivity
2012-09-10 12:38 ` Peter Lieven
2012-09-10 12:38 ` [Qemu-devel] " Peter Lieven
2012-09-13 7:53 ` Peter Lieven
2012-09-13 7:53 ` [Qemu-devel] " Peter Lieven
2012-09-13 7:55 ` Paolo Bonzini
2012-09-13 7:55 ` [Qemu-devel] " Paolo Bonzini
2012-09-13 7:57 ` Gleb Natapov
2012-09-13 7:57 ` [Qemu-devel] " Gleb Natapov
2012-09-13 8:00 ` Paolo Bonzini
2012-09-13 8:00 ` [Qemu-devel] " Paolo Bonzini
2012-09-13 8:05 ` Gleb Natapov [this message]
2012-09-13 8:05 ` Gleb Natapov
2012-09-13 12:05 ` Peter Lieven
2012-09-13 12:05 ` [Qemu-devel] " Peter Lieven
2012-09-13 12:42 ` Gleb Natapov
2012-09-13 12:42 ` [Qemu-devel] " Gleb Natapov
2012-09-13 12:56 ` Peter Lieven
2012-09-13 12:56 ` [Qemu-devel] " Peter Lieven
2012-09-13 13:43 ` Gleb Natapov
2012-09-13 13:43 ` [Qemu-devel] " Gleb Natapov
2012-09-10 12:12 ` Avi Kivity
2012-09-10 12:12 ` [Qemu-devel] " Avi Kivity
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=20120913080529.GY20907@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.