From: Avi Kivity <avi@redhat.com>
To: Nicolae Mogoreanu <mogo@google.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Joerg Roedel <joerg.roedel@amd.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Ignore the writes to MSR_K7_HWCR(3)
Date: Wed, 07 Mar 2012 13:00:33 +0200 [thread overview]
Message-ID: <4F573FD1.9080708@redhat.com> (raw)
In-Reply-To: <CAA3wOXps5yg4NbdC0Cud+2px487zEV34v-dEfAom4o-24JPvbQ@mail.gmail.com>
On 02/21/2012 11:44 PM, Nicolae Mogoreanu wrote:
> From: Nicolae Mogoreanu <mogoreanu@gmail.com>
> KVM: Ignore the writes to MSR_K7_HWCR(3)
>
> When CPUID Fn8000_0001_EAX reports 0x00100f22 Windows 7 x64 guest
> tries to set bit 3 in MSRC001_0015 in nt!KiDisableCacheErrataSource
> and fails. This patch will ignore this step and allow things to move
> on without having to fake CPUID value.
>
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-03-07 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 21:44 [PATCH] KVM: Ignore the writes to MSR_K7_HWCR(3) Nicolae Mogoreanu
2012-03-07 11:00 ` 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=4F573FD1.9080708@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mogo@google.com \
--cc=mtosatti@redhat.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