From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752664AbdGLNrX (ORCPT ); Wed, 12 Jul 2017 09:47:23 -0400 Received: from mail.skyhub.de ([5.9.137.197]:59754 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751015AbdGLNrW (ORCPT ); Wed, 12 Jul 2017 09:47:22 -0400 Date: Wed, 12 Jul 2017 15:47:06 +0200 From: Borislav Petkov To: Mikulas Patocka Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/kernel/cpu/amd.c: don't apply the lahf_lm workaround in a hypervisor Message-ID: <20170712134706.GA20584@nazgul.tnic> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 12, 2017 at 03:19:56AM -0400, Mikulas Patocka wrote: > When I start a virtual machine, kvm complains about accesses to an unknown > MSR ("vcpu0 unhandled rdmsr: 0xc001100d"). This is caused by the code in > init_amd_k8 that tries to work around a BIOS bug that incorrectly sets > lahf_lm. No need - there are a lot of qemu configurations which cause the unhandled MSR warning so no need to pollute the kernel unnecessarily. The warning is harmless at that. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --