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=-2.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 2975DC48BCF for ; Wed, 9 Jun 2021 02:16:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0E48161287 for ; Wed, 9 Jun 2021 02:16:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233597AbhFICSV (ORCPT ); Tue, 8 Jun 2021 22:18:21 -0400 Received: from mail-oi1-f174.google.com ([209.85.167.174]:46007 "EHLO mail-oi1-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232224AbhFICSU (ORCPT ); Tue, 8 Jun 2021 22:18:20 -0400 Received: by mail-oi1-f174.google.com with SMTP id w127so23599070oig.12; Tue, 08 Jun 2021 19:16:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Df8t1QJutzCUZPX7EISyP+4HxHgoT0YA70uuZIR5B6o=; b=Zi9J/0ym37D+zXhLM7/YAWLx6IOFr76XVw0l3r/xPNWxTc7NeLpT82qb2L7c7Ge/BC xtyVYSsAEY3MNmpX/EOZq/FQUA/uff6fLssVN78w+/5ltjrmXoFp/1SQB5sWWxdfxtVl gTAuRCf08LgCybgyqjLxNdasxgbL2WdAvubwZdv8mBZV/UWZQb+5sjw+d04oUYb8x/EF 0mtkQ4WcqT7N/gva9senlpQOAfG1hdNk6aFsQ/wijbYzvcLD1MgBulUDXYHAb8WTKuWP UaGzZ6gh/XkgVFGZoQl3QdTJlWCIU/CE+wWxScartoY3ND09CXpxHbKz4GLpd+teHyN9 T7hQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Df8t1QJutzCUZPX7EISyP+4HxHgoT0YA70uuZIR5B6o=; b=uZDZ4pwvog6nyMquaJcFF4DKDyzMkYVGGpAftSNJyAksOQeWrfI4oScfaW0zh6Qq8y c7xKuHA5x1nzvZy1/QimncZaTqw3HUs7Wt1cAT4d6sxDjWquKKmJDaz4hStjJRDnC002 Q5WbQO2YC5s774JdGkOOjADon1evcijZD3R1ERVh0rggOeNIK4HuDiD3AMsqB/5bXkT0 LgHNwVZyImBqQDjTGiWEcwWMQxiko5xB/qbEGUNaICFmBv20qO55IzU9NBf4rd5x6BJa WHU3jYMHBCNc76cYGDH68fZtq+34iznJZU5ymS6mm5pAa+TAgntDkLhHgJ5jPfdKb4vl /08A== X-Gm-Message-State: AOAM532aU53Utge+CG+RE/Hh6BlpQDmQmkN6Af8O3XVTtkr+du1t4n5q hrFU50M1zjG6ceIUrHzJecz4COcQvJ8t/v6ef+h3/Ygtogk= X-Google-Smtp-Source: ABdhPJw+RVlVDUG2zRXgiVMWgTXdzzWRLwkU3MLbSSijsAVchAyBr4VRJaUNqQse3cIPEuKaoWXg0BWP6DjEH3JJhyU= X-Received: by 2002:a05:6808:c3:: with SMTP id t3mr4582410oic.5.1623204911286; Tue, 08 Jun 2021 19:15:11 -0700 (PDT) MIME-Version: 1.0 References: <1623050385-100988-1-git-send-email-wanpengli@tencent.com> <1623050385-100988-2-git-send-email-wanpengli@tencent.com> <0584d79d-9f2c-52dd-5dcc-beffd18f265b@redhat.com> In-Reply-To: <0584d79d-9f2c-52dd-5dcc-beffd18f265b@redhat.com> From: Wanpeng Li Date: Wed, 9 Jun 2021 10:15:00 +0800 Message-ID: Subject: Re: [PATCH v2 2/3] KVM: LAPIC: Reset TMCCT during vCPU reset To: Paolo Bonzini Cc: LKML , kvm , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 9 Jun 2021 at 00:27, Paolo Bonzini wrote: [...] > Perhaps instead set TMCCT to 0 in kvm_apic_set_state, instead of keeping > the value that was filled in by KVM_GET_LAPIC? Keeping the value that was filled in by KVM_GET_LAPIC is introduced by commit 24647e0a39b6 (KVM: x86: Return updated timer current count register from KVM_GET_LAPIC), could you elaborate more? :) Wanpeng