public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Shuai Ruan <shuai.ruan@linux.intel.com>,
	kvm@vger.kernel.org, allen.m.kay@intel.com
Subject: Re: [PATCH] KVM: x86: Add three MSRs to the list of ignored MSRs
Date: Thu, 14 Apr 2016 18:29:08 +0200	[thread overview]
Message-ID: <20160414162907.GB3350@potion.brq.redhat.com> (raw)
In-Reply-To: <570FAC6F.10704@redhat.com>

2016-04-14 16:42+0200, Paolo Bonzini:
> On 14/04/2016 15:33, Radim Krčmář wrote:
>> The main bug in KVM is that it allows the guest to think that it runs on
>> CPU that isn't emulated:  any CPU that has MSR_PLATFORM_INFO shouldn't
>> be exposed in KVM.
> 
> That's all of them.  f/m/s values and the model name are a useful
> debugging tool.  Considering that MSR_PLATFORM_INFO is hardly ever used,
> it doesn't seem to be a great compromise.

I don't see that as a compromise.  igd would fail even if we fixed the
host side, so we'll have problems regardless of what we do.

We have a bug, because certain v/f/m/s implies some features (MSRs,
constant_tsc, ...) and those aren't emulated.

I do agree that we don't want to fix the bug, either by whitelisting and
emulating features that makes little sense in virt or by forcing guests
to adopt new v/f/m/s (the latter option is more reasonable), because
rare occurences of the bug take *much* less work to fix on the guest
side.  (The only part I'm concerned about is that we don't have a good
excuse for some guest errors ...)

  reply	other threads:[~2016-04-14 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  9:28 [PATCH] KVM: x86: Add three MSRs to the list of ignored MSRs Shuai Ruan
2016-04-14 13:33 ` Radim Krčmář
2016-04-14 14:42   ` Paolo Bonzini
2016-04-14 16:29     ` Radim Krčmář [this message]
2016-04-15 10:48       ` Paolo Bonzini
2016-04-15 14:12         ` Radim Krčmář
     [not found]           ` <20160419092025.GA2651@shuai.ruan@linux.intel.com>
2016-04-19 16:10             ` Kay, Allen M

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=20160414162907.GB3350@potion.brq.redhat.com \
    --to=rkrcmar@redhat.com \
    --cc=allen.m.kay@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=shuai.ruan@linux.intel.com \
    /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