From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH v4 05/10] KVM/x86: expose MSR_IA32_PERF_CAPABILITIES to the guest Date: Mon, 7 Jan 2019 10:20:12 -0800 Message-ID: <20190107182012.GL6118@tassilo.jf.intel.com> References: <1545816338-1171-1-git-send-email-wei.w.wang@intel.com> <1545816338-1171-6-git-send-email-wei.w.wang@intel.com> <5C2DC132.9050103@intel.com> <5C3318A1.9090009@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Wei Wang , LKML , kvm list , Paolo Bonzini , Peter Zijlstra , Kan Liang , Ingo Molnar , Radim =?utf-8?B?S3LEjW3DocWZ?= , like.xu@intel.com, Jann Horn , arei.gonglei@huawei.com To: Jim Mattson Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org > The issue is compatibility. Prior to your change, reading this MSR > from a VM would raise #GP. After your change, it won't. That means > that if you have a VM migrating between hosts with kernel versions > before and after this change, the results will be inconsistent. In the No it will not be. All Linux kernel uses of this MSR are guarded by a CPUID check. -Andi