Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp1251080rwd; Thu, 18 May 2023 09:43:25 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5GjIwLNd6fZM0LGO3kHQIvEofI6Dua05UfcEBTzPE8Hts1X0OHWSG4bEAiIh15206a9e7t X-Received: by 2002:a05:6a21:1692:b0:106:c9b7:c93d with SMTP id np18-20020a056a21169200b00106c9b7c93dmr321031pzb.19.1684428204693; Thu, 18 May 2023 09:43:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684428204; cv=none; d=google.com; s=arc-20160816; b=uej4nGB77HImAKKNHvIuy+2jHGcfVgEjYZrPhqFg0ZzsEFWvfD8GqW01AaA/eSxAvc fPIK1uaAUb87ZvLW9gPPYHtXbSkH5Kw1XSP5BWFTt9eHZKgmtpjAojja3k8+A+ASMpMX HqE3Uy12yxWC3ZQjecnQAjzJjcFygNYJhDfZl6eCg5ktPbFPpzBD+5b2ch6zY+r+CvI/ yXcXMlOLuqZSJ9lplZK7SPjAuWT94T6dyGK6ouGfifZzCk/eJnbOXAug+ec7wJilY+Dv Vb0cAd5+v+IeGphGH3acd5AH9SnnhWex/kyEVjStpxlQv4C9WekkrkzRkxfL5LA5AMmU Vi8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=b/k7Bavm6Lw4AsVDYKE7OFlJNNdKR1gkmQmj5zQSYNU=; b=WFKCR4/E4wOjjTGKXWiaCMjngX5tTm+ZsDgEJ+YtGTl4hsBHv4yns0EVEnVPaETsbQ xjVxniw1FzKqiGwl8P0Lxh4nXcTFtCxYtL8LY9qKrK+rPu2TDzGH1mEffhmkFLnnhIt3 q6JtXe8zuAvQr7mOSwUuts8YjSwx45LdeHEffgf+bEizCdTmL3nFwL6OaQaF7GisY+aw /SaisLDnl4bbTU+mErAcjBl/FSKy9PvHZVz1Vet+NL8eDlITLt+2Ug6aALQnO/16cqEW NfQtHbGtVHjksD6yAYeqK8ISC+PGzYKcibUlV3BpDPD0qtnNeieLNdof2n1OL25zeVJ8 HrQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Uuew0uNv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d7-20020aa797a7000000b0063b8eec0832si2094308pfq.114.2023.05.18.09.43.08; Thu, 18 May 2023 09:43:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Uuew0uNv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229476AbjERQbe (ORCPT + 99 others); Thu, 18 May 2023 12:31:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229449AbjERQbV (ORCPT ); Thu, 18 May 2023 12:31:21 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA3A1B3; Thu, 18 May 2023 09:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1684427479; x=1715963479; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=WUUsMc2BhnwkTh/1UnMlHwzt6z3OUDJZykERpb42rPE=; b=Uuew0uNv78dYF624B5rvZZhpipLohFg7eBk8mFY7+GyvM/uDHjqG6R5A 5Cxc7BZ79m8pxJnVfTa/eMuf5tRcEp5bHbDyW0hNXp+AU90uZPKdpfB9D e4Ez7P5364FwhwWZXgvzL0q27e0uAguuYLoogvJWsdPelmxFx1i7tMi8w 7TOJ1M3BBuWEcGs6pb5x73SkfOKC6YXqIlsVPhK9TI4y3jODysxrb8TYp w1pXy0kODInO9Br54hPE+HTH43J/pWjATNe+J1YSn9QjxNZgIIeBJG6iT 5PU3db+OwPx1VBTs62O6xwdxJx2HxP9MSnwekVbGiN7iOH1zxVZlBajs3 w==; X-IronPort-AV: E=McAfee;i="6600,9927,10714"; a="417803672" X-IronPort-AV: E=Sophos;i="6.00,285,1681196400"; d="scan'208";a="417803672" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2023 09:31:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10714"; a="948749658" X-IronPort-AV: E=Sophos;i="6.00,285,1681196400"; d="scan'208";a="948749658" Received: from linux.intel.com ([10.54.29.200]) by fmsmga006.fm.intel.com with ESMTP; 18 May 2023 09:31:14 -0700 Received: from [10.209.99.208] (kliang2-mobl1.ccr.corp.intel.com [10.209.99.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id 9C4555808EF; Thu, 18 May 2023 09:31:13 -0700 (PDT) Message-ID: <3dca8ccf-081a-0765-b5e3-9584f9128137@linux.intel.com> Date: Thu, 18 May 2023 12:31:12 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: [PATCH] perf/x86/intel: Save/restore cpuc->active_pebs_data_cfg when using guest PEBS Content-Language: en-US To: Like Xu , Peter Zijlstra Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230517133808.67885-1-likexu@tencent.com> From: "Liang, Kan" In-Reply-To: <20230517133808.67885-1-likexu@tencent.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023-05-17 9:38 a.m., Like Xu wrote: > From: Like Xu > > After commit b752ea0c28e3 ("perf/x86/intel/ds: Flush PEBS DS when changing > PEBS_DATA_CFG"), the cpuc->pebs_data_cfg may save some bits that are not > supported by real hardware, such as PEBS_UPDATE_DS_SW. This would cause > the VMX hardware MSR switching mechanism to save/restore invalid values > for PEBS_DATA_CFG MSR, thus crashing the host when PEBS is used for guest. I believe we clear the SW bit when it takes effect. + if (cpuc->pebs_data_cfg & PEBS_UPDATE_DS_SW) { + cpuc->pebs_data_cfg = pebs_data_cfg; + pebs_update_threshold(cpuc); + } I think the SW bit can only be seen in a shot period between add() and enable(). Is it caused by a VM enter which just happens on the period? > Fix it by using the active host value from cpuc->active_pebs_data_cfg. I don't see a problem of using active_pebs_data_cfg, since it reflects the current MSR setting. Just curious about how it's triggered. > > Cc: Kan Liang > Cc: Peter Zijlstra > Signed-off-by: Like Xu > --- Reviewed-by: Kan Liang Thanks, Kan > arch/x86/events/intel/core.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c > index 070cc4ef2672..89b9c1cebb61 100644 > --- a/arch/x86/events/intel/core.c > +++ b/arch/x86/events/intel/core.c > @@ -4074,7 +4074,7 @@ static struct perf_guest_switch_msr *intel_guest_get_msrs(int *nr, void *data) > if (x86_pmu.intel_cap.pebs_baseline) { > arr[(*nr)++] = (struct perf_guest_switch_msr){ > .msr = MSR_PEBS_DATA_CFG, > - .host = cpuc->pebs_data_cfg, > + .host = cpuc->active_pebs_data_cfg, > .guest = kvm_pmu->pebs_data_cfg, > }; > }