From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH] x86, kvm: Add MSR_AMD64_BU_CFG2 to the list of ignored MSRs Date: Wed, 13 Feb 2013 12:55:26 +0100 Message-ID: <20130213115526.GA15210@pd.tnic> References: <1360755761-725-1-git-send-email-bp@alien8.de> <20130213114747.GC9817@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: kvm@vger.kernel.org, LKML , X86 ML , Borislav Petkov , Boris Ostrovsky , Andre Przywara , Marcelo Tosatti To: Gleb Natapov Return-path: Content-Disposition: inline In-Reply-To: <20130213114747.GC9817@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 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 > > > > 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. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --