From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Amit Shah <amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Joerg.Roedel-5C7GfCeVMHo@public.gmane.org,
Markus Rechberger
<markus.rechberger-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH] discard MSR writes
Date: Tue, 20 Nov 2007 12:12:35 +0200 [thread overview]
Message-ID: <4742B313.4080704@qumranet.com> (raw)
In-Reply-To: <200711201539.31712.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Amit Shah wrote:
> On Tuesday 20 November 2007 15:17:54 Avi Kivity wrote:
>
>> Amit Shah wrote:
>>
>>> On Tuesday 20 November 2007 00:38:05 Markus Rechberger wrote:
>>>
>>>> this patch discards MSR writes to the Performance Event-Select
>>>> Registers, this is the first issue why vista seems to fail although now
>>>> vista ends up in an endless loop a bit later.
>>>> Qemu currently also discards those writes.
>>>>
>>> Won't this make the corresponding rdmsrs fail? What happens when the
>>> rdmsr returns an error, but windows then uses some garbage value (as it
>>> thinks the wrmsr succeeded, so the rdmsr also should)?
>>>
>> rdmsr will inject #GP for these msrs. Implementing set_msr() doesn't
>> affect rdmsr.
>>
>
> >From the AMD programming manual, vol 2:
>
> The performance event-select registers can be read and written only by system
> software running at CPL = 0 using the RDMSR and WRMSR instructions,
> respectively. Any attempt to read or write these registers at CPL > 0 causes
> a general-protection exception to occur.
>
Look through the code that implements rdmsr, it doesn't care about the
manuals and will happily inject a #GP for rdmsr of any unimplemented msr
(like PerfEvtSel) wrmsr and rdmsr implementations are not linked.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-11-20 10:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 19:08 [PATCH] discard MSR writes Markus Rechberger
[not found] ` <4741DF15.20708-5C7GfCeVMHo@public.gmane.org>
2007-11-20 7:45 ` Amit Shah
[not found] ` <200711201315.15337.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-20 9:47 ` Avi Kivity
[not found] ` <4742AD4A.2080406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-20 10:09 ` Amit Shah
[not found] ` <200711201539.31712.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-20 10:12 ` Avi Kivity [this message]
[not found] ` <4742B313.4080704-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-20 10:32 ` Amit Shah
[not found] ` <200711201602.43331.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-20 10:35 ` Avi Kivity
[not found] ` <4742B88F.8000404-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-20 12:31 ` Markus Rechberger
[not found] ` <4742D3AC.2030108-5C7GfCeVMHo@public.gmane.org>
2007-11-20 12:34 ` Avi Kivity
2007-11-20 9:24 ` 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=4742B313.4080704@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=Joerg.Roedel-5C7GfCeVMHo@public.gmane.org \
--cc=amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=markus.rechberger-5C7GfCeVMHo@public.gmane.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