From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: jinsong.liu@intel.com, chegger@amazon.de,
suravee.suthikulpanit@amd.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] mcheck, vmce: Allow vmce_amd_* functions to handle AMD thresolding MSRs
Date: Mon, 27 Jan 2014 16:46:01 -0600 [thread overview]
Message-ID: <52E6E1A9.3030903@amd.com> (raw)
In-Reply-To: <52E6B0DA.8070708@oracle.com>
On 1/27/2014 1:17 PM, Boris Ostrovsky wrote:
> On 03/15/2008 05:50 PM, Aravind Gopalakrishnan wrote:
>>
>> diff --git a/xen/arch/x86/cpu/mcheck/vmce.c
>> b/xen/arch/x86/cpu/mcheck/vmce.c
>> index f6c35db..cb4fd12 100644
>> --- a/xen/arch/x86/cpu/mcheck/vmce.c
>> +++ b/xen/arch/x86/cpu/mcheck/vmce.c
>> @@ -107,7 +107,7 @@ static int bank_mce_rdmsr(const struct vcpu *v,
>> uint32_t msr, uint64_t *val)
>> *val = 0;
>> - switch ( msr & (MSR_IA32_MC0_CTL | 3) )
>> + switch ( msr & (MSR_IA32_MC0_CTL | (0x3 << 30) | 0x13))
>
> Which MSRs are going to be handled in the non-default cases?
> MSR0000_040[0:3] and MSRC000_040[0:3]? The first four already have
> explicit cases and I think it would be more readable if you explicitly
> created case statements for the latter four and had a simple
> 'switch(msr)'.
>
In non-default cases, we need to handle MSR0x40[0:7]. MSR0x40[0:3] is
bank 0 and remaining ones are bank 1.
We can't do a simple switch(msr) since if we do that, MSR0x40[4:7] will
fall to 'default' (which is incorrect)
> In fact, do MSRC000_040[0:3] even exist?
>
Nope. They don't..
we only allow MCE MSR's here anyway:
ret = mce_bank_msr(cur, msr) ? bank_mce_rdmsr(cur, msr, val) : 0;
'mce_bank_msr' returns 1 only if we see MSR0x40[0:7] or some 'special
MSR's' which in AMD's case are the three thresholding regs
MSR_F10_MC4_MISC1 to MSR_F10_MC4_MISC3
> (You may also want to adjust your clock --- your emails are being sent
> from distant past ;-) )
>
>
Yes, thanks for pointing that out :)
I'll correct that and send V2
-Aravind.
next prev parent reply other threads:[~2014-01-27 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 21:50 [PATCH 0/2] Fix AMD threshold register definitions and activate vmce_amd_* functions Aravind Gopalakrishnan
2008-03-15 21:50 ` [PATCH 1/2] hvm, svm: Update AMD Thresholding MSR definitions Aravind Gopalakrishnan
2014-01-28 9:13 ` Egger, Christoph
2014-01-28 10:27 ` George Dunlap
2008-03-15 21:50 ` [PATCH 2/2] mcheck, vmce: Allow vmce_amd_* functions to handle AMD thresolding MSRs Aravind Gopalakrishnan
2014-01-27 19:17 ` Boris Ostrovsky
2014-01-27 22:46 ` Aravind Gopalakrishnan [this message]
2014-01-27 23:29 ` Boris Ostrovsky
2014-01-28 9:09 ` Egger, Christoph
2014-02-03 22:48 ` [PATCH 0/2] Fix AMD threshold register definitions and activate vmce_amd_* functions Matt Wilson
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=52E6E1A9.3030903@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chegger@amazon.de \
--cc=jinsong.liu@intel.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xen.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.