From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, 0day robot <lkp@intel.com>,
Like Xu <likexu@tencent.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, kvm@vger.kernel.org
Subject: Re: [KVM] 9daee8ca83: kvm-unit-tests.apic.fail
Date: Fri, 25 Feb 2022 16:24:45 +0000 [thread overview]
Message-ID: <YhkCzS1rGYyJ0mKP@google.com> (raw)
In-Reply-To: <20220225014911.GA30182@xsang-OptiPlex-9020>
On Fri, Feb 25, 2022, kernel test robot wrote:
> commit: 9daee8ca835bf3ba264414c6f3a3924e23455449 ("[PATCH v2] KVM: x86: pull kvm->srcu read-side to kvm_arch_vcpu_ioctl_run")
> url: https://github.com/0day-ci/linux/commits/Paolo-Bonzini/KVM-x86-pull-kvm-srcu-read-side-to-kvm_arch_vcpu_ioctl_run/20220220-190039
> base: https://git.kernel.org/cgit/virt/kvm/kvm.git master
> patch link: https://lore.kernel.org/lkml/20220219093404.367207-1-pbonzini@redhat.com
>
> in testcase: kvm-unit-tests
> version: kvm-unit-tests-x86_64-882825e-1_20220215
> with following parameters:
>
> ucode: 0x28
> please be noted, besides kvm-unit-tests.apic.fail in title, we also found below
> cases fail upon this commit while pass on parent:
Same thing I hit[*]. Paolo temporarily dropped the buggy patch, a new one will
presumably show up soonish.
[*] https://lore.kernel.org/all/20220224212646.3544811-1-seanjc@google.com
prev parent reply other threads:[~2022-02-25 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 9:34 [PATCH v2] KVM: x86: pull kvm->srcu read-side to kvm_arch_vcpu_ioctl_run Paolo Bonzini
2022-02-21 3:51 ` Like Xu
2022-02-25 1:49 ` [KVM] 9daee8ca83: kvm-unit-tests.apic.fail kernel test robot
2022-02-25 16:24 ` Sean Christopherson [this message]
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=YhkCzS1rGYyJ0mKP@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=likexu@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox