From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "osstest service owner" <osstest-admin@xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org,
"Ian Jackson" <iwj@xenproject.org>
Subject: Re: Regressed XSA-286, was [xen-unstable test] 161917: regressions - FAIL
Date: Mon, 17 May 2021 12:59:01 +0200 [thread overview]
Message-ID: <f365c8f9-362c-f7f5-6ed4-34131a1dce63@suse.com> (raw)
In-Reply-To: <e8fae962-1a5b-cc91-d429-a716b009f062@suse.com>
On 17.05.2021 10:43, Jan Beulich wrote:
> On 13.05.2021 22:15, Andrew Cooper wrote:
>> Second, the unexplained OSSTest behaviour.
>>
>> When I repro'd this on pinot1, test-pv32pae-xsa-286 failing was totally
>> deterministic and repeatable (I tried 100 times because the test is a
>> fraction of a second).
>>
>> From the log trawling which Ian already did, the first recorded failure
>> was flight 160912 on April 11th. All failures (12, but this number is a
>> few flights old now) were on pinot*.
>>
>> What would be interesting to see is whether there have been any passes
>> on pinot since 160912.
>>
>> I can't see any reason why the test would be reliable for me, but
>> unreliable for OSSTest, so I'm wondering whether it is actually
>> reliable, and something is wrong with the stickiness heuristic.
>
> Isn't (un)reliability of this test, besides the sensitivity to IRQs
> and context switches, tied to hardware behavior, in particular TLB
> capacity and replacement policy? Aiui the test has
>
> xtf_success("Success: Probably not vulnerable to XSA-286\n");
>
> for the combination of all of these reasons.
I've just done a dozen runs on my Skylake - all reported SUCCESS.
Jan
next prev parent reply other threads:[~2021-05-17 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 3:56 [xen-unstable test] 161917: regressions - FAIL osstest service owner
2021-05-13 20:15 ` Regressed XSA-286, was " Andrew Cooper
2021-05-17 8:43 ` Jan Beulich
2021-05-17 10:59 ` Jan Beulich [this message]
2021-06-16 8:48 ` Jan Beulich
2021-06-16 15:43 ` Andrew Cooper
2021-06-17 11:56 ` Jan Beulich
2021-06-17 13:05 ` Ian Jackson
2021-06-17 14:40 ` Jan Beulich
2021-06-17 14:49 ` Ian Jackson
2021-06-17 14:55 ` Jan Beulich
2021-06-28 12:35 ` Ping: " Jan Beulich
2021-06-17 21:26 ` Stefano Stabellini
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=f365c8f9-362c-f7f5-6ed4-34131a1dce63@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=iwj@xenproject.org \
--cc=osstest-admin@xenproject.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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).