Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp3025143pxb; Mon, 4 Apr 2022 06:06:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzMc7c1mESqMfKSScz9ukm+CGyqunMpdGz698DSy7wLJNqQKGenJ6lKigIjFs74oV1GzEBG X-Received: by 2002:a17:906:e5b:b0:6e7:f3a7:7b66 with SMTP id q27-20020a1709060e5b00b006e7f3a77b66mr3367661eji.355.1649077575548; Mon, 04 Apr 2022 06:06:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649077575; cv=none; d=google.com; s=arc-20160816; b=w+LMovxLc5x4nQkyn4H4Oi0FarR+ra1IlQ391+X07MUXfFJe1NuDJA51h6kk3aZTYC 3t4amsKljxTam6QRGRSuSpQQxtTkLx1GAQxNKEzxVQyS5bc6i9d2UHBP5KbpuE1fw0HD v3wGlcdtOsklmVdOB4HkXnEI4qyYJrWFfXqaDy10Sz0nJII2Xje9fEqo5IYLd0xTSCie RtjIor2LbZvHRKV/y0qKD0HPdcc9LmYFlUObTQHTxrRxRI6nLjmXpjZkoF1dGDPzVYKE xk/ZhOv3EJXKGbyCdMN0tD6ZjgXflIF++XQv/4feBT4mLNV0Mj5LG+Swgkw5VRKAOsxX Xf7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=MGpdsUgeU20LgBuDXB+NmysxzRrBIqWkuKnTRQ4cJj0=; b=gG+XUpjYfD29FYUEbelqx8TJA4o3Fwf6cGJMnQLbH9r8BwiDyj6H72xEUErEG6pnkV 5PZCnzTgl6Z4xYtCyPitvZu8ef3ZLOlit0TkjhagI3rx9dEdDMyfpGNdVDKbLLhMZ9Jk 5BhXxsJQLJTKeNUkV18xPl37odqzC680XPsbwtQzWmsM6pfFkPD4d66dZsRN8ZDA1FYi Ga9oFQrdarGbkh7xRAXby7dcJHa4LJdDuY8oOtvEB393QI03VqBFO1oooXLvFXQVyeSA Q61r4F6Jk9ud3Z7VPGd9jGFkruhicCEzDcC58jZlu6gFrvmyjcgWme4CI6YR1A9z2zXZ y9UA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=aiBkZqE7; 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 d16-20020a170906641000b006df86351032si6510890ejm.194.2022.04.04.06.05.48; Mon, 04 Apr 2022 06:06:15 -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=20210112 header.b=aiBkZqE7; 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 S1350996AbiDAS2e (ORCPT + 99 others); Fri, 1 Apr 2022 14:28:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57750 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345972AbiDAS2d (ORCPT ); Fri, 1 Apr 2022 14:28:33 -0400 Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1664E1AC710 for ; Fri, 1 Apr 2022 11:26:43 -0700 (PDT) Received: by mail-oi1-x231.google.com with SMTP id b188so3596961oia.13 for ; Fri, 01 Apr 2022 11:26:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MGpdsUgeU20LgBuDXB+NmysxzRrBIqWkuKnTRQ4cJj0=; b=aiBkZqE7yk6o2sGGdrjmlF6VLxoE/QsqdWTRKaC1hibWaS67x5lCoqPB9YMyCC6t2x JsxZiR9RLdlTJYLNZ2nXhalhdOEkbRrW7okbFQntFeyvLVnd+YfOaniPvZxDgRFtwdQ8 NvsC9dddsPamXwaB4f7593BXIPRbPnDYeab5vMnlvVNR+4jer4/aN4W+eeYmCPLnNYS4 0grai+oljzag9E+YX1qXV8YlnDu0swMJm3E0gl3tmakt6j48eMqBVUVbWa/8p1zti4ud rcqBqLsYKRC5Jzrz3cEUNKQwJYU18TNvRCW8Nur9QTL7TIDO6fPFYmhPg5S/51RMmXlb qcQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MGpdsUgeU20LgBuDXB+NmysxzRrBIqWkuKnTRQ4cJj0=; b=4PdX7xL23b8qfLqBfmLEI3XxKmpISyCZQpP0iE4F5OoeXXEPdDbE3IYzs4yFMYjfvq TRo6YRsW/W1/vVzB7TbBAR8lxzc8vwIKcYARe4YNHTNVZc9KtsZgFMbpddUrNAQ3X4I3 ogGgVDXglibx9HJ/FZHZtANegLM2VQsLDibYBcK+roRA7HcxOMPzEMhoxXmjgQQHLGGd xuuw3unpcWrKYqwD0bwabP/24UaMWWpHLkRlpqfsVxLAKKXcyDaQzWN63R2xpFFEghTd tM7wMQoKYR30vDS0d+YiNaJA+A9ySbsRapE875pwfdvGQJRLqS2QibSAfK1SBrnGmgZe lvzA== X-Gm-Message-State: AOAM5302Tl6EtQMXloa68c3nKC5c6oClO/BdZAc3KoLdNk624LSq/gyK /N/PxEnw2Lg5AyO4D083POQE0XdkOlwc5vemffkmiQ== X-Received: by 2002:a05:6808:2207:b0:2f9:35b6:8866 with SMTP id bd7-20020a056808220700b002f935b68866mr5382338oib.269.1648837602235; Fri, 01 Apr 2022 11:26:42 -0700 (PDT) MIME-Version: 1.0 References: <20220329134632.6064-1-likexu@tencent.com> In-Reply-To: <20220329134632.6064-1-likexu@tencent.com> From: Jim Mattson Date: Fri, 1 Apr 2022 11:26:31 -0700 Message-ID: Subject: Re: [PATCH] KVM: x86/pmu: Update AMD PMC smaple period to fix guest NMI-watchdog To: Like Xu Cc: Paolo Bonzini , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Joerg Roedel , Eric Hankland , kvm@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL 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 Tue, Mar 29, 2022 at 6:46 AM Like Xu wrote: > > From: Like Xu > > NMI-watchdog is one of the favorite features of kernel developers, > but it does not work in AMD guest even with vPMU enabled and worse, > the system misrepresents this capability via /proc. > > This is a PMC emulation error. KVM does not pass the latest valid > value to perf_event in time when guest NMI-watchdog is running, thus > the perf_event corresponding to the watchdog counter will enter the > old state at some point after the first guest NMI injection, forcing > the hardware register PMC0 to be constantly written to 0x800000000001. > > Meanwhile, the running counter should accurately reflect its new value > based on the latest coordinated pmc->counter (from vPMC's point of view) > rather than the value written directly by the guest. > > Fixes: 168d918f2643 ("KVM: x86: Adjust counter sample period after a wrmsr") > Reported-by: Dongli Cao > Signed-off-by: Like Xu Reviewed-by: Jim Mattson