Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp318378rwd; Mon, 12 Jun 2023 14:08:36 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4HiAl4zaUXNd29zcVu/2xFDnFLo9KivJs53h1vVZ4EdOsRGOAKoSbhfBw1sIFSyto8TuUm X-Received: by 2002:a17:907:7e85:b0:978:90cc:bf79 with SMTP id qb5-20020a1709077e8500b0097890ccbf79mr10617680ejc.4.1686604116010; Mon, 12 Jun 2023 14:08:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686604115; cv=none; d=google.com; s=arc-20160816; b=toaQEZpsSs9+EF5jSDBb2XjkEO6ZIDVsy+s4JSYfHhoVBTwRfzhZUFZ+JWJI8d8xt2 RZXERiY+lIzw7NiMD5xJYWoqTWUi3odmXPJQWnCbfz+pnoJUE3qJ7eCLJxoFexGApyXj HekGjTulns1Wc0tVrcXbZdOydbH/cxowGxweizQag0epytMNAHkjmo1F1YL8opf0DdZ2 F4cHpJHTa7weSJ0IWpyxVEr7VcwRDEbYQ9NujJvhxQ3qhlPh02ftKk1ffmF5eltJUHQP aJPcpbsqILiwlXwxnQm5QKReq5T8wf4iINa3NBeW48TB3m2MuScmJtb1yIsuVb9gUyTP qV/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:dkim-signature; bh=drJuJWNwArkfxWzubYqBhjyWEE7jVbV5pqjBOdAZiV0=; b=YZ8gvWFbTy/kiV5yhB27I3vykuFUrmIlTxYSsJ0C5vxpkNuNS7gMl04miqAvH2/qvu Kgz7bFtnSaG4mBJ0bNP7M1yzhk7IfQHzUIZt4Aq809OdMMuCywS5fHXbMfnXjGbtHgWJ lLYN326XTTtsqtjbl7qPCk0JUvTlWD9MB7TxygeI5JGQKgH31UfQv6waOC0Hr95p7cxR XS6AfsB9qe5dlI6P7zpkCqZTt2LQIJZaidyShFe8gmoslwDqKuzPowfselwF5P8GVckn k+mhtwhGiZiTR0/uueKa0BjeYm/FcW9sgAVjifoxVaw1WJaazQjHNnPWa91bmI54BEjl m1GQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b=CY4o4ik1; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id dk13-20020a170906f0cd00b00978923a8fc8si5693578ejb.383.2023.06.12.14.08.10; Mon, 12 Jun 2023 14:08:35 -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=@google.com header.s=20221208 header.b=CY4o4ik1; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236433AbjFLUpk (ORCPT + 99 others); Mon, 12 Jun 2023 16:45:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234464AbjFLUpb (ORCPT ); Mon, 12 Jun 2023 16:45:31 -0400 Received: from mail-pl1-x64a.google.com (mail-pl1-x64a.google.com [IPv6:2607:f8b0:4864:20::64a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5AD8AC7 for ; Mon, 12 Jun 2023 13:45:05 -0700 (PDT) Received: by mail-pl1-x64a.google.com with SMTP id d9443c01a7336-1b3c1bd4866so16123355ad.1 for ; Mon, 12 Jun 2023 13:45:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1686602702; x=1689194702; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=drJuJWNwArkfxWzubYqBhjyWEE7jVbV5pqjBOdAZiV0=; b=CY4o4ik1gLa9xfMuvdv8OGscu/Dg++2BDkdIvAQtBymy4uSSRRKpuADMPmkLBlQVDi USw6XZs33kqAgsGRls0e+5GLpRkF2IopqZ7JiFgFSIh41ekKxI+pdWJ9Wu+TAlV0TfoU QXGkz4CmByld2iKwvpqHPBiz5/K+MHgFl2Gimk8PgyICYQIksEFxl0v1AN/TfE+x3pXZ 3JNezCrbhCe/64vzUtJugwJ3jb4ri6s0BN8FtBIM7oXVLZgqPa5oJuFGwOuywFQ5rfDP scgqUd1yPv70JiQmWBFqTIAFR7YpVo37aNfpTdva7cKU5qoGEmQF4cuv5aDFVBpFM5nk iuJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686602702; x=1689194702; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=drJuJWNwArkfxWzubYqBhjyWEE7jVbV5pqjBOdAZiV0=; b=VN71nkmnZHkziuqWjnnHNIgD7DajImM6/k5jWeuHlihdvVFwsduWK33B54SJhtOyz5 W3lJCGtg1gfDjY5XMu5PUw5iEkq/OLJMNuu2gGIYdXSGIHLe8FaQ2kOFvvR03RDExLlX bq/p1+p9rEXfp/ZEKw5CYeyWcKVBgqp1tLnfVe4u70sP8yV5K/WrsOnnDuWciRrCzE3t FAVpXopbGhGJyw+BOWtRpjUFeCwuHqxvTKyLa0rmZZzpFqAvu4ZtSxb69o89mSxa7qNE qwVw3iJgn6oucWnQ6Su5lsSkjZ3dAIyJ9om1Qu/QLD/NpJteINW72amigQgu7IWKg3Eg S1EQ== X-Gm-Message-State: AC+VfDzEGTJ1WkSGt24+rPB9LU4XnjnmVSFr5HAuHDyGb6g+wtwslDmO hrujmDzpK5gJDEu+DEaFicz5WbyeVmQ= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:903:1cd:b0:1a9:8e56:9e14 with SMTP id e13-20020a17090301cd00b001a98e569e14mr1512425plh.3.1686602701672; Mon, 12 Jun 2023 13:45:01 -0700 (PDT) Date: Mon, 12 Jun 2023 13:45:00 -0700 In-Reply-To: <20230517133808.67885-1-likexu@tencent.com> Mime-Version: 1.0 References: <20230517133808.67885-1-likexu@tencent.com> Message-ID: Subject: Re: [PATCH] perf/x86/intel: Save/restore cpuc->active_pebs_data_cfg when using guest PEBS From: Sean Christopherson To: Like Xu Cc: Peter Zijlstra , Kan Liang , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-9.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL autolearn=unavailable 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 +KVM On Wed, May 17, 2023, 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. > Fix it by using the active host value from cpuc->active_pebs_data_cfg. In the future, please Cc: kvm@vger.kernel.org when posting fixes that obviously affect KVM. I wasted several hours bisecting these crashes. In hindsight, I should have searched all of lore sooner, but it really shouldn't have been that hard for me to find this fix. > Cc: Kan Liang > Cc: Peter Zijlstra > Signed-off-by: Like Xu > --- > 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, > }; > } > -- > 2.40.1 >