From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Tim Deegan <tim@xen.org>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Jan Beulich <jbeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: Problem with Xen 4.5 failing XTF tests on old AMD cpus ?
Date: Thu, 22 Sep 2016 10:29:17 +0100 [thread overview]
Message-ID: <22499.42093.421856.865826@mariner.uk.xensource.com> (raw)
In-Reply-To: <8419ad72-db6d-8d62-297a-79e9db506837@citrix.com>
Andrew Cooper writes ("Re: Problem with Xen 4.5 failing XTF tests on old AMD cpus ?"):
> It will be because of Gen1 SVM which doesn't have NRIP support. This
> case requires emulation of the invlpg instruction, rather than just
> using the information provided by the intercept.
So it seems that the xtf test is not effective at detecting the Xen
bug except on old hardware ? Is there some way it could be improved ?
It's obviously not desirable that we should have tests which pass in
the production colo and fail in the ancient Citrix Cambridge instance.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-22 9:29 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
2016-09-21 18:20 ` Andrew Cooper
2016-09-22 9:29 ` Ian Jackson [this message]
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=22499.42093.421856.865826@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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 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.