From: Borislav Petkov <bp@alien8.de>
To: Joel Schopp <joel.schopp@amd.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"jesse.larrew@amd.com" <jesse.larrew@amd.com>,
"x86@kernel.org" <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mce: use safe MSR accesses
Date: Thu, 12 Mar 2015 18:30:56 +0100 [thread overview]
Message-ID: <20150312173056.GD25505@pd.tnic> (raw)
In-Reply-To: <5501CAC7.6090306@amd.com>
On Thu, Mar 12, 2015 at 12:20:07PM -0500, Joel Schopp wrote:
> These MSRs don't make sense in guest mode. The real question is if we
> fix that in KVM, here, or both. I'm a fan of fixing it in both places.
> Xen's behavior is to return a value of 0 if the guest tries to access
> these, that seems like a reasonable thing to do in KVM as well. I am
> volunteering myself to write that patch for KVM, but I would encourage
This should be first and foremost fixed in KVM as it is KVM which is
advertizing MCA CPUID feature and the guest simply uses it with all MSRs
which belong to it.
> accepting an updated version of this patch as well.
If you want to do that, I'd suggest using the error checking variants
in arch/x86/lib/msr.c which should also facilitate toggling of bits in
MSRs.
> Initializing val to 0 where it is declared should have the desired
> effect.
Yes, as long as KVM returns 0 for MC4_MISC0/1.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-03-12 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 22:09 [PATCH] mce: use safe MSR accesses jesse.larrew
2015-03-11 22:47 ` Luck, Tony
2015-03-12 17:20 ` Joel Schopp
2015-03-12 17:30 ` Borislav Petkov [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=20150312173056.GD25505@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jesse.larrew@amd.com \
--cc=joel.schopp@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@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 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.