Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752428AbdLFP5h (ORCPT ); Wed, 6 Dec 2017 10:57:37 -0500 Received: from mga01.intel.com ([192.55.52.88]:7019 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752270AbdLFP5a (ORCPT ); Wed, 6 Dec 2017 10:57:30 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,368,1508828400"; d="scan'208";a="13657061" Date: Wed, 6 Dec 2017 07:57:28 -0800 From: Andi Kleen To: Jan Dakinevich Cc: linux-kernel@vger.kernel.org, "Denis V . Lunev" , Roman Kagan , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Thomas Gleixner , "H. Peter Anvin" , x86@kernel.org, Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , Kan Liang , Stephane Eranian , Colin King , Sebastian Andrzej Siewior , Jin Yao , kvm@vger.kernel.org Subject: Re: [PATCH RFC 2/2] KVM: x86/vPMU: ignore access to LBR-related MSRs Message-ID: <20171206155728.GL3070@tassilo.jf.intel.com> References: <1512560585-27263-1-git-send-email-jan.dakinevich@virtuozzo.com> <1512560585-27263-3-git-send-email-jan.dakinevich@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1512560585-27263-3-git-send-email-jan.dakinevich@virtuozzo.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 358 Lines: 11 If you do all this it's only a small step to fully enable LBRs for guests. Just need to allow them to be written, expose PERF_CAPABILITIES too, and start/stop them on entry/exit, and enable context switching through perf in the host. That would be far better than creating a frankenstate where LBR is there but mostly broken on some KVM versions. -Andi