From: Gustavo Romero <gromero@linux.vnet.ibm.com>
To: Cyril Bur <cyrilbur@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: leitao@debian.org
Subject: Re: [PATCH] selftests/powerpc: Check FP/VEC on exception in TM
Date: Fri, 3 Nov 2017 10:28:10 -0200 [thread overview]
Message-ID: <59FC60DA.6060100@linux.vnet.ibm.com> (raw)
In-Reply-To: <1509574233.1667.4.camel@gmail.com>
Hi Cyril!
On 01-11-2017 20:10, Cyril Bur wrote:
> Thanks Gustavo,
>
> I do have one more thought on an improvement for this test which is
> that:
> + /* Counter for busy wait *
> + uint64_t counter = 0x1ff000000;
> is a bit fragile, what we should do is have the test work out long it
> should spin until it reliably gets a TM_CAUSE_FAC_UNAV failure and then
> use that for these tests.
>
> This will only become a problem if we were to change kernel heuristics
> which is fine for now. I'll try to get that added soon but for now this
> test has proven too useful to delay adding as is.
I see. Yup, 'counter' value was indeed determined experimentally under many
different scenarios (VM and BM, different CPU loads, etc). At least if the
heuristics changes hurting the test it will catch that pointing out that
the expected failure did not happen, like:
Checking if FP/VEC registers are sane after a FP unavailable exception...
If MSR.FP=0 MSR.VEC=0:
Expecting the transaction to fail, but it didn't
FP ok VEC ok
...
So it won't let the hurting change pass fine silently :-)
>> Signed-off-by: Gustavo Romero <gromero@linux.vnet.ibm.com>
>> Signed-off-by: Breno Leitao <leitao@debian.org>
>> Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
Thanks a lot for reviewing it.
Cheers,
Gustavo
next prev parent reply other threads:[~2017-11-03 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 19:23 [PATCH] selftests/powerpc: Check FP/VEC on exception in TM Gustavo Romero
2017-11-01 22:10 ` Cyril Bur
2017-11-03 12:28 ` Gustavo Romero [this message]
2017-11-05 23:33 ` Cyril Bur
2017-11-14 11:12 ` Michael Ellerman
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=59FC60DA.6060100@linux.vnet.ibm.com \
--to=gromero@linux.vnet.ibm.com \
--cc=cyrilbur@gmail.com \
--cc=leitao@debian.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.