From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5B83EC433E0 for ; Fri, 15 Jan 2021 18:52:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 29A3423A59 for ; Fri, 15 Jan 2021 18:52:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729353AbhAOSvj (ORCPT ); Fri, 15 Jan 2021 13:51:39 -0500 Received: from one.firstfloor.org ([193.170.194.197]:42214 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726136AbhAOSvi (ORCPT ); Fri, 15 Jan 2021 13:51:38 -0500 X-Greylist: delayed 898 seconds by postgrey-1.27 at vger.kernel.org; Fri, 15 Jan 2021 13:51:38 EST Received: by one.firstfloor.org (Postfix, from userid 503) id D269386852; Fri, 15 Jan 2021 19:27:00 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=firstfloor.org; s=mail; t=1610735220; bh=31CxBw19B4liGLfT90HOu8/1FDJ+TbGT3dFu6N0lNBI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uHSPvcfFdbSWbNz+YfxwNvqKiskkpFagDxHS0TXKIQgSWMgf5g6rVdtG3tu1CfyPI 7t7kVXfAWQZXmb6fB+vHxkQN0ONY7dfrbwgx0t0b078NA7Hv5sd9v/OwQa65iLR0/j CpN1I6wWSLzgX/CoOOw89o/9mlG2gVuVjzbU2Z04= Date: Fri, 15 Jan 2021 10:27:00 -0800 From: Andi Kleen To: Sean Christopherson Cc: "Xu, Like" , Andi Kleen , Kan Liang , Peter Zijlstra , Paolo Bonzini , eranian@google.com, kvm@vger.kernel.org, Ingo Molnar , Thomas Gleixner , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , wei.w.wang@intel.com, luwei.kang@intel.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 00/17] KVM: x86/pmu: Add support to enable Guest PEBS via DS Message-ID: <20210115182700.byczztx3vjhsq3p3@two.firstfloor.org> References: <20210104131542.495413-1-like.xu@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org > I'm asking about ucode/hardare. Is the "guest pebs buffer write -> PEBS PMI" > guaranteed to be atomic? Of course not. > > In practice, under what scenarios will guest counters get cross-mapped? And, > how does this support affect guest accuracy? I.e. how bad do things get for the > guest if we simply disable guest counters if they can't have a 1:1 association > with their physical counter? This would completely break perfmon for the guest, likely with no way to recover. -Andi