From: Gleb Natapov <gleb@redhat.com>
To: Borislav Petkov <bp@alien8.de>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Borislav Petkov <bp@suse.de>,
Boris Ostrovsky <boris.ostrovsky@amd.com>,
Andre Przywara <andre@andrep.de>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] x86, kvm: Add MSR_AMD64_BU_CFG2 to the list of ignored MSRs
Date: Wed, 13 Feb 2013 14:10:02 +0200 [thread overview]
Message-ID: <20130213121002.GD9817@redhat.com> (raw)
In-Reply-To: <20130213115526.GA15210@pd.tnic>
On Wed, Feb 13, 2013 at 12:55:26PM +0100, Borislav Petkov wrote:
> On Wed, Feb 13, 2013 at 01:47:47PM +0200, Gleb Natapov wrote:
> > On Wed, Feb 13, 2013 at 12:42:41PM +0100, Borislav Petkov wrote:
> > > From: Borislav Petkov <bp@suse.de>
> > >
> > > The "x86, AMD: Enable WC+ memory type on family 10 processors" patch
> > > currently in -tip added a workaround for AMD F10h CPUs which #GPs my
> > > guest when booted in kvm. This is because it accesses MSR_AMD64_BU_CFG2
> > > which is not currently ignored by kvm. Do that because this MSR is only
> > > baremetal-relevant anyway. While at it, move the ignored MSRs at the
> > > beginning of kvm_set_msr_common so that we exit then and there.
> > >
> > Is your guest compiled without PV support? With PV Linux traps #GP for
> > all MSRs and it saves us in more than one places.
>
> Yes, CONFIG_PARAVIRT_GUEST is not set on the guest kernel.
>
Thanks. It does not mean that the patch should not be applied though.
I cannot seems to find the documentation for the MSR anywhere, do you
have a pointer?
--
Gleb.
next prev parent reply other threads:[~2013-02-13 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 11:42 [PATCH] x86, kvm: Add MSR_AMD64_BU_CFG2 to the list of ignored MSRs Borislav Petkov
2013-02-13 11:47 ` Gleb Natapov
2013-02-13 11:55 ` Borislav Petkov
2013-02-13 12:10 ` Gleb Natapov [this message]
2013-02-13 13:35 ` Borislav Petkov
2013-02-13 15:37 ` Gleb Natapov
2013-02-13 15:39 ` Gleb Natapov
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=20130213121002.GD9817@redhat.com \
--to=gleb@redhat.com \
--cc=andre@andrep.de \
--cc=boris.ostrovsky@amd.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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.