[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190725160939.GC18612@linux.intel.com>
Date: Thu, 25 Jul 2019 09:09:39 -0700
From: Sean Christopherson <sean.j.christopherson@...el.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Anders Roxell <anders.roxell@...aro.org>,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
wanpengli@...cent.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
patches@...nelci.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
linux- stable <stable@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Shuah Khan <shuah@...nel.org>,
Guenter Roeck <linux@...ck-us.net>, jmattson@...gle.com
Subject: Re: [PATCH 5.2 000/413] 5.2.3-stable review
On Thu, Jul 25, 2019 at 07:35:13PM +0530, Naresh Kamboju wrote:
> Paolo,
>
> On Thu, 25 Jul 2019 at 19:17, Paolo Bonzini <pbonzini@...hat.com> wrote:
> >
> > On 25/07/19 13:34, Greg Kroah-Hartman wrote:
> > > Any chance you can run 'git bisect' to find the offending patch? Or
> > > just try reverting a few, you can ignore the ppc ones, so that only
> > > leaves you 7 different commits.
> > >
> > > Does this same test pass in 5.3-rc1?
>
> Yes. same test pass on 5.3-rc1
> kvm unit test always fetching master branch and at tip
> runs the latest test code on all branches
> mainline 5.3-rc1 and stable-rc-5.2 branch
>
> >
> > Anders, are you running the same kvm-unit-tests commit that passed for
> > 5.2.2? My suspicion is that your previous test didn't have this commit
>
> No.
> I see two extra test code commits for 5.2.3
> Re-tested 5.2.2 with tip of kvm unit tests sources and vmx test FAILED [1].
>
> Greg,
> This investigation confirms it is a new test code failure on stable-rc 5.2.3
No, it only confirms that kvm-unit-tests/master fails on 5.2.*. To confirm
a new failure in 5.2.3 you would need to show a test that passes on 5.2.2
and fails on 5.2.3.
As Paolo suspected, kvm-unit-tests/master fails on 5.2.* and passes if
commit 95d6d2c ("nVMX: Test Host Segment Registers and Descriptor Tables on
vmentry of nested guests") is reverted (from kvm-unit-tests).
The failures are quite clearly in the new test(s).
PASS: HOST_SEL_CS 8: vmlaunch succeeds
FAIL: HOST_SEL_CS 9: vmlaunch fails
FAIL: HOST_SEL_CS c: vmlaunch fails
PASS: HOST_SEL_SS 10: vmlaunch succeeds
FAIL: HOST_SEL_SS 11: vmlaunch fails
FAIL: HOST_SEL_SS 14: vmlaunch fails
PASS: HOST_SEL_DS 10: vmlaunch succeeds
FAIL: HOST_SEL_DS 11: vmlaunch fails
FAIL: HOST_SEL_DS 14: vmlaunch fails
PASS: HOST_SEL_ES 10: vmlaunch succeeds
FAIL: HOST_SEL_ES 11: vmlaunch fails
FAIL: HOST_SEL_ES 14: vmlaunch fails
PASS: HOST_SEL_FS 10: vmlaunch succeeds
FAIL: HOST_SEL_FS 11: vmlaunch fails
FAIL: HOST_SEL_FS 14: vmlaunch fails
PASS: HOST_SEL_GS 10: vmlaunch succeeds
FAIL: HOST_SEL_GS 11: vmlaunch fails
FAIL: HOST_SEL_GS 14: vmlaunch fails
PASS: HOST_SEL_TR 80: vmlaunch succeeds
FAIL: HOST_SEL_TR 81: vmlaunch fails
KVM: entry failed, hardware error 0x80000021
Powered by blists - more mailing lists