From: Daniel Axtens <dja@axtens.net>
To: Cyril Bur <cyrilbur@gmail.com>, mpe@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, mikey@neuling.org,
Anshuman Khandual <khandual@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/5] selftests/powerpc: Check for VSX preservation across userspace preemption
Date: Thu, 09 Jun 2016 11:35:55 +1000 [thread overview]
Message-ID: <87mvmvqh38.fsf@possimpible.ozlabs.ibm.com> (raw)
In-Reply-To: <20160608040036.13064-2-cyrilbur@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4140 bytes --]
Yay for tests!
I have a few minor nits, and one more major one (rc == 2 below).
> +/*
> + * Copyright 2015, Cyril Bur, IBM Corp.
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License
> + * as published by the Free Software Foundation; either version
> + * 2 of the License, or (at your option) any later version.
> + */
I realise this is well past a lost cause by now, but isn't the idea to
be version 2, not version 2 or later?
> +
> +#include "../basic_asm.h"
> +#include "../vsx_asm.h"
> +
Some of your other functions start with a comment. That would be super
helpful here - I'm still not super comfortable I understand the calling
convention.
> +FUNC_START(check_vsx)
> + PUSH_BASIC_STACK(32)
> + std r3,STACK_FRAME_PARAM(0)(sp)
> + addi r3, r3, 16 * 12 #Second half of array
> + bl store_vsx
> + ld r3,STACK_FRAME_PARAM(0)(sp)
> + bl vsx_memcmp
> + POP_BASIC_STACK(32)
> + blr
> +FUNC_END(check_vsx)
> +
> +long vsx_memcmp(vector int *a) {
> + vector int zero = {0,0,0,0};
> + int i;
> +
> + FAIL_IF(a != varray);
> +
> + for(i = 0; i < 12; i++) {
> + if (memcmp(&a[i + 12], &zero, 16) == 0) {
> + fprintf(stderr, "Detected zero from the VSX reg %d\n", i + 12);
> + return 1;
> + }
> + }
> +
> + if (memcmp(a, &a[12], 12 * 16)) {
I'm somewhat confused as to how this comparison works. You're comparing
the new saved ones to the old saved ones, yes?
> + long *p = (long *)a;
> + fprintf(stderr, "VSX mismatch\n");
> + for (i = 0; i < 24; i=i+2)
> + fprintf(stderr, "%d: 0x%08lx%08lx | 0x%08lx%08lx\n",
> + i/2 + i%2 + 20, p[i], p[i + 1], p[i + 24], p[i + 25]);
> + return 1;
> + }
> + return 0;
> +}
> +
> +void *preempt_vsx_c(void *p)
> +{
> + int i, j;
> + long rc;
> + srand(pthread_self());
> + for (i = 0; i < 12; i++)
> + for (j = 0; j < 4; j++) {
> + varray[i][j] = rand();
> + /* Don't want zero because it hides kernel problems */
> + if (varray[i][j] == 0)
> + j--;
> + }
> + rc = preempt_vsx(varray, &threads_starting, &running);
> + if (rc == 2)
How would rc == 2? AIUI, preempt_vsx returns the value of check_vsx,
which in turn returns the value of vsx_memcmp, which returns 1 or 0.
> + fprintf(stderr, "Caught zeros in VSX compares\n");
Isn't it zeros or a mismatched value?
> + return (void *)rc;
> +}
> +
> +int test_preempt_vsx(void)
> +{
> + int i, rc, threads;
> + pthread_t *tids;
> +
> + threads = sysconf(_SC_NPROCESSORS_ONLN) * THREAD_FACTOR;
> + tids = malloc(threads * sizeof(pthread_t));
> + FAIL_IF(!tids);
> +
> + running = true;
> + threads_starting = threads;
> + for (i = 0; i < threads; i++) {
> + rc = pthread_create(&tids[i], NULL, preempt_vsx_c, NULL);
> + FAIL_IF(rc);
> + }
> +
> + setbuf(stdout, NULL);
> + /* Not really nessesary but nice to wait for every thread to start */
> + printf("\tWaiting for %d workers to start...", threads_starting);
> + while(threads_starting)
> + asm volatile("": : :"memory");
I think __sync_synchronise() might be ... more idiomatic or something?
Not super fussy.
> + printf("done\n");
> +
> + printf("\tWaiting for %d seconds to let some workers get preempted...", PREEMPT_TIME);
> + sleep(PREEMPT_TIME);
> + printf("done\n");
> +
> + printf("\tStopping workers...");
> + /*
> + * Working are checking this value every loop. In preempt_vsx 'cmpwi r5,0; bne 2b'.
> + * r5 will have loaded the value of running.
> + */
> + running = 0;
Do you need some sort of synchronisation here? You're assuming it
eventually gets to the threads, which is of course true, but maybe it
would be a good idea to synchronise it more explicitly? Again, not super
fussy.
> + for (i = 0; i < threads; i++) {
> + void *rc_p;
> + pthread_join(tids[i], &rc_p);
> +
> + /*
> + * Harness will say the fail was here, look at why preempt_vsx
> + * returned
> + */
> + if ((long) rc_p)
> + printf("oops\n");
> + FAIL_IF((long) rc_p);
> + }
> + printf("done\n");
> +
> + return 0;
> +}
> +
Regards,
Daniel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 859 bytes --]
next prev parent reply other threads:[~2016-06-09 1:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 4:00 [PATCH 0/5] Consistent TM structures Cyril Bur
2016-06-08 4:00 ` [PATCH 1/5] selftests/powerpc: Check for VSX preservation across userspace preemption Cyril Bur
2016-06-09 1:35 ` Daniel Axtens [this message]
2016-06-09 3:52 ` Michael Ellerman
2016-06-10 6:10 ` Cyril Bur
2016-06-08 4:00 ` [PATCH 2/5] selftests/powerpc: Add test to check TM ucontext creation Cyril Bur
2016-06-09 5:12 ` Daniel Axtens
2016-06-10 5:55 ` Cyril Bur
2016-06-08 4:00 ` [PATCH 3/5] powerpc: tm: Always use fp_state and vr_state to store live registers Cyril Bur
2016-06-28 3:53 ` Simon Guo
2016-06-30 1:31 ` Cyril Bur
2016-07-17 3:25 ` Simon Guo
2016-07-18 1:28 ` Cyril Bur
2016-07-20 9:36 ` Simon Guo
2016-06-08 4:00 ` [PATCH 4/5] powerpc: tm: Rename transct_(*) to ck(\1)_state Cyril Bur
2016-06-08 4:00 ` [PATCH 5/5] powerpc: Remove do_load_up_transact_{fpu,altivec} Cyril Bur
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=87mvmvqh38.fsf@possimpible.ozlabs.ibm.com \
--to=dja@axtens.net \
--cc=cyrilbur@gmail.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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).