From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Wei Liu <wei.liu2@citrix.com>,
osstest service owner <osstest-admin@xenproject.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 94442: regressions - FAIL
Date: Tue, 17 May 2016 10:01:15 +0100 [thread overview]
Message-ID: <573ADDDB.8000802@citrix.com> (raw)
In-Reply-To: <573AF98302000078000EC020@prv-mh.provo.novell.com>
On 17/05/16 09:59, Jan Beulich wrote:
>>>> On 16.05.16 at 11:29, <andrew.cooper3@citrix.com> wrote:
>> On 16/05/16 10:24, Wei Liu wrote:
>>> On Mon, May 16, 2016 at 02:57:13AM +0000, osstest service owner wrote:
>>>> flight 94442 xen-unstable real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/94442/
>>> [...]
>>>> test-amd64-i386-qemuu-rhel6hvm-intel 9 redhat-install fail REGR. vs. 94368
>>> The changes in this flight shouldn't cause failure like this. See below.
>>>
>>> It is more likely to be caused by SMEP/SMAP fix, which are now in
>>> master. It seems that previous run didn't discover this.
>> Indeed - definitely from the SMEP/SMAP fix. What kind of hardware is
>> italia0?
> E3-1220V2 according to the copy of the spreadsheet of systems
> I have. Aiui v2 should have neither SMEP nor SMAP, and hence we
> shouldn't even get into cr4_pv32_restore(). Suggests an issue with
> alternative insn patching ...
v2 is IvyBridge, and has SMEP but not SMAP.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-17 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 2:57 [xen-unstable test] 94442: regressions - FAIL osstest service owner
2016-05-16 9:24 ` Wei Liu
2016-05-16 9:29 ` Andrew Cooper
2016-05-16 9:39 ` Wei Liu
2016-05-16 9:42 ` Andrew Cooper
2016-05-17 8:59 ` Jan Beulich
2016-05-17 9:01 ` Andrew Cooper [this message]
2016-05-17 9:08 ` Jan Beulich
2016-05-17 9:06 ` Jan Beulich
2016-05-17 10:57 ` Jan Beulich
2016-05-17 13:08 ` Andrew Cooper
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=573ADDDB.8000802@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=osstest-admin@xenproject.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 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).