From: Oliver Sang <oliver.sang@intel.com>
To: Like Xu <like.xu.linux@gmail.com>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <jmattson@google.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org
Subject: Re: [KVM] db16e9b28b: kvm-unit-tests.pmu.fail
Date: Tue, 24 May 2022 21:36:05 +0800 [thread overview]
Message-ID: <20220524133604.GA34870@xsang-OptiPlex-9020> (raw)
In-Reply-To: <d741a183-6180-1a49-fffb-b62d36286a04@gmail.com>
Hi Like Xu,
On Sun, May 15, 2022 at 05:25:21PM +0800, Like Xu wrote:
> On 15/5/2022 5:22 pm, kernel test robot wrote:
> > patch link:https://lore.kernel.org/kvm/20220509102204.62389-2-likexu@tencent.com
>
> Fixed by the V2 version. Please help try.
we tested the V2 version and could not reproduce pmu.fail on it:
=========================================================================================
compiler/kconfig/rootfs/tbox_group/testcase/ucode:
gcc-11/x86_64-rhel-8.3-func/debian-10.4-x86_64-20200603.cgz/lkp-hsw-d02/kvm-unit-tests/0x28
commit:
bec9b596f911 ("KVM: x86/pmu: Ignore pmu->global_ctrl check if vPMU doesn't support global_ctrl")
db16e9b28b05 ("KVM: x86/pmu: Don't pre-set the pmu->global_ctrl when refreshing")
3fa1b82c692b ("KVM: x86/pmu: Don't pre-set the pmu->global_ctrl when refreshing") v2
bec9b596f911252e db16e9b28b05f069d01b76886b6 3fa1b82c692b513878a23e07efc
---------------- --------------------------- ---------------------------
fail:runs %reproduction fail:runs %reproduction fail:runs
| | | | |
:6 50% 3:3 0% :10 kvm-unit-tests.pmu.fail
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Sang <oliver.sang@intel.com>
To: lkp@lists.01.org
Subject: Re: [KVM] db16e9b28b: kvm-unit-tests.pmu.fail
Date: Tue, 24 May 2022 21:36:05 +0800 [thread overview]
Message-ID: <20220524133604.GA34870@xsang-OptiPlex-9020> (raw)
In-Reply-To: <d741a183-6180-1a49-fffb-b62d36286a04@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
Hi Like Xu,
On Sun, May 15, 2022 at 05:25:21PM +0800, Like Xu wrote:
> On 15/5/2022 5:22 pm, kernel test robot wrote:
> > patch link:https://lore.kernel.org/kvm/20220509102204.62389-2-likexu(a)tencent.com
>
> Fixed by the V2 version. Please help try.
we tested the V2 version and could not reproduce pmu.fail on it:
=========================================================================================
compiler/kconfig/rootfs/tbox_group/testcase/ucode:
gcc-11/x86_64-rhel-8.3-func/debian-10.4-x86_64-20200603.cgz/lkp-hsw-d02/kvm-unit-tests/0x28
commit:
bec9b596f911 ("KVM: x86/pmu: Ignore pmu->global_ctrl check if vPMU doesn't support global_ctrl")
db16e9b28b05 ("KVM: x86/pmu: Don't pre-set the pmu->global_ctrl when refreshing")
3fa1b82c692b ("KVM: x86/pmu: Don't pre-set the pmu->global_ctrl when refreshing") v2
bec9b596f911252e db16e9b28b05f069d01b76886b6 3fa1b82c692b513878a23e07efc
---------------- --------------------------- ---------------------------
fail:runs %reproduction fail:runs %reproduction fail:runs
| | | | |
:6 50% 3:3 0% :10 kvm-unit-tests.pmu.fail
next prev parent reply other threads:[~2022-05-24 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 10:22 [PATCH 1/3] KVM: x86/pmu: Ignore pmu->global_ctrl check if vPMU doesn't support global_ctrl Like Xu
2022-05-09 10:22 ` [PATCH 2/3] KVM: x86/pmu: Don't pre-set the pmu->global_ctrl when refreshing Like Xu
2022-05-10 4:37 ` [PATCH V2 " Like Xu
2022-05-10 4:44 ` [PATCH v2] " Like Xu
2022-05-20 14:25 ` Paolo Bonzini
2022-05-15 9:22 ` [KVM] db16e9b28b: kvm-unit-tests.pmu.fail kernel test robot
2022-05-15 9:22 ` kernel test robot
2022-05-15 9:25 ` Like Xu
2022-05-15 9:25 ` Like Xu
2022-05-24 13:36 ` Oliver Sang [this message]
2022-05-24 13:36 ` Oliver Sang
2022-05-09 10:22 ` [PATCH 3/3] KVM: x86/pmu: Drop redundant-clumsy-asymmetric PERFCTR_CORE MSRs handling Like Xu
2022-05-20 14:32 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220524133604.GA34870@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.