From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Chris Lalancette <clalance@redhat.com>,
Joerg Roedel <joerg.roedel@amd.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] move performance counter MSR access interception to generic x86 KVM path
Date: Sun, 14 Jun 2009 11:00:31 +0300 [thread overview]
Message-ID: <4A34AE1F.9020606@redhat.com> (raw)
In-Reply-To: <1244836889-1365-1-git-send-email-andre.przywara@amd.com>
Andre Przywara wrote:
> The performance counter MSRs are different for AMD and Intel CPUs and they
> are chosen mainly by the CPUID vendor string. This patch catches writes to
> all addresses (regardless of VMX/SVM path) and handles them in the generic
> MSR handler routine. Writing a 0 into the event select register is something
> we perfectly emulate ;-), so don't print out a warning to dmesg in this
> case.
> This fixes booting a 64bit Windows guest with an AMD CPUID on an Intel host.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-06-14 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 20:01 [PATCH] move performance counter MSR access interception to generic x86 KVM path Andre Przywara
2009-06-14 8: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=4A34AE1F.9020606@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.com \
--cc=clalance@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.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