From: Wei Liu <wei.liu2@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Problem with Xen 4.5 failing XTF tests on old AMD cpus ?
Date: Wed, 21 Sep 2016 19:06:47 +0100 [thread overview]
Message-ID: <20160921180647.GC27172@citrix.com> (raw)
In-Reply-To: <095afbbe-ace9-44de-a890-1895f2418f95@oracle.com>
On Wed, Sep 21, 2016 at 02:00:50PM -0400, Boris Ostrovsky wrote:
> On 09/21/2016 01:36 PM, Wei Liu wrote:
> > On Wed, Sep 21, 2016 at 12:42:51PM -0400, Boris Ostrovsky wrote:
> >> On 09/21/2016 12:13 PM, Ian Jackson wrote:
> >>> Platform Team regression test user writes ("[xen-4.5-testing baseline-only test] 67737: regressions - FAIL"):
> >>>> test-xtf-amd64-amd64-1 19 xtf/test-hvm32-invlpg~shadow fail REGR. vs. 67706
> >>>> test-xtf-amd64-amd64-1 26 xtf/test-hvm32pae-invlpg~shadow fail REGR. vs. 67706
> >>> Several of these, 32bit and 64bit HVM. This is in the Citrix
> >>> Cambridge osstest instance. The Xen Project colo instance is
> >>> unaffected (flight 101045 there passed with the same revisions of
> >>> everything)
> >>>
> >>> This is with:
> >>>
> >>> xen e4ae4b03d35babc9624b7286f1ea4c6749bad84b
> >>> xtf b5c5332de4268d33a6f8eadc1d17c7b9cf0e7dc3
> >>> linux b65f2f457c49b2cfd7967c34b7a0b04c25587f13
> >>> linux-firmware c530a75c1e6a472b0eb9558310b518f0dfcd8860
> >> I can't get these commits neither for Xen nor for Linux. Are these from
> >> Citrix trees?
> > No. They are all upstream commits.
>
> Apparently xen commit *just* made it to the tree, after I checked it.
Yes, it passed in Mass COLO. We suspected it can be related to
generations of AMD cpus (hence the "old" in email title).
> And I still don't see Linux one.
>
It should be upstream commit, too. But I don't think it matters that
much anyway.
> I ran a quick test (not xtf, our internal one) with 32-bit shadow guest
> and didn't see anything. But then Andrew seems to have pointed out what
That's probably because your guest is a well-behaved guest.
> the problem is.
>
> -boris
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-21 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 14:09 [xen-4.5-testing baseline-only test] 67737: regressions - FAIL Platform Team regression test user
2016-09-21 16:13 ` Problem with Xen 4.5 failing XTF tests on old AMD cpus ? Ian Jackson
2016-09-21 16:15 ` Ian Jackson
2016-09-21 16:42 ` Boris Ostrovsky
2016-09-21 17:36 ` Wei Liu
2016-09-21 18:00 ` Boris Ostrovsky
2016-09-21 18:06 ` Wei Liu [this message]
2016-09-21 18:20 ` Andrew Cooper
2016-09-22 9:29 ` Ian Jackson
2016-09-26 16:56 ` Ian Jackson
2016-09-21 17:27 ` Andrew Cooper
2016-09-22 9:49 ` Ian Jackson
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=20160921180647.GC27172@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).