Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp206632pxb; Fri, 15 Jan 2021 10:52:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJxEpXAQ3nXJrXXLqUHoKOncns+wvY2Y7f78tbg1tuzHXZ4uM12oGwYK3A0ww546JD/Cl5mH X-Received: by 2002:a17:906:7090:: with SMTP id b16mr10093457ejk.76.1610736771172; Fri, 15 Jan 2021 10:52:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610736771; cv=none; d=google.com; s=arc-20160816; b=Ib7+cR/QC2mljc5hXhJ4GQyH9YppM0e8j2pp4l/aIcpvS9Pkv15R88qPfw7ReowuAA r4nVVN/s0E9jRV8J2A2XTOllDhGO1P9pHZPZzccLvVL2xGkciG+Q7B55hUkOU3JblNDk iBa3MKbJW2Gs3n5hvZqOyNUzSVLK3Y3Rlne6iSZswsRh9TKkIGy2Ni1BQYIZCB614Zo2 uG+WPjER8QW8pjtTussJ10KaXyGxNYoKdXg0FUwAy4uyv4+RPwOGgk1KYrW9WzGHGpav U0pB8H13DweOFNgPxWOYzIJlMcqbs2v5BZE1EFIb7Eo+k1Sj9PSMuPYTYYePUl/gjRGN JN4Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=td9ljhBfRhhhiYyPxr1NZ6B4xk7kNiJ11Tu96is8E74=; b=bKR/rADbedpqQt6C+sCqlJSpyCgRf+rGPSv7vEZuwB/aNdiIDNKuhx8RtQ1cBCLYtm 12MK2pRZ0Aea2uyuPu2Vy1zBxz48jZRGUDDbfXWmTuJm1wtRhOLwEvukJg2TavDZovhk HViZjM+aSdAK7hHIIMTDVqCbu/II5osggSH2GlSsxzC8VpuoLNz/B3/U7IsKW3q5848l 1VmWgq5X5iEN6mizStPlLldRysMmRi4FUyzzAgf84c1cOZgJIL+Yy+M6V/0kuD82kCMG q7qFAlYIMPHGRUcACNNVpFc6ikKesPyWGws20RG8/wUmbywB4a5lPdymkq2ScSgJ2Ngq i3qg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@firstfloor.org header.s=mail header.b=uHSPvcfF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a42si5254204edf.469.2021.01.15.10.52.26; Fri, 15 Jan 2021 10:52:51 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@firstfloor.org header.s=mail header.b=uHSPvcfF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729075AbhAOSvj (ORCPT + 99 others); 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: linux-kernel@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