From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Jim Mattson <jmattson@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Dan Cross <dcross@google.com>, Peter Shier <pshier@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkp@lists.01.org
Subject: Re: [KVM] 671ddc700f: kvm-unit-tests.vmx.fail
Date: Wed, 6 Nov 2019 07:18:22 -0800 [thread overview]
Message-ID: <20191106151822.GC16249@linux.intel.com> (raw)
In-Reply-To: <20191106144548.GA32541@xsang-OptiPlex-9020>
On Wed, Nov 06, 2019 at 10:45:48PM +0800, Oliver Sang wrote:
> On Wed, Oct 30, 2019 at 09:56:16AM -0700, Jim Mattson wrote:
> > It's unclear to me what the delta is, but I do see that the 'vmx'
> > suite has failed. That is to be expected if you're getting your
> > kvm-unit-tests from the 'master' branch of the kvm-unit-tests repo.
> > You will need commit 591b5b54bba1 ("x86: Skip APIC-access address
> > tests beyond mapped RAM"), which is in the 'next' branch of the
> > kvm-unit-tests repo, but which has not yet made it to the 'master'
> > branch.
>
> Thanks for information! We will wait for master upgrade to update our test
> binary.
This reminds me, are we still planning on creating "stable" branches for
kvm-unit-tests[*]? This topic of came up in a discussion at KVM Forum as
well, though I can't remember any of the details.
Paolo?
[*] https://lkml.kernel.org/r/dc5ff4ed-c6dd-74ea-03ae-4f65c5d58073@redhat.com
prev parent reply other threads:[~2019-11-06 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 14:23 [KVM] 671ddc700f: kvm-unit-tests.vmx.fail kernel test robot
2019-10-30 16:56 ` Jim Mattson
2019-11-06 14:45 ` Oliver Sang
2019-11-06 15:18 ` 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=20191106151822.GC16249@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=dcross@google.com \
--cc=jmattson@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).