lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 14 Jan 2015 10:44:31 +1100
From:	Michael Ellerman <mpe@...erman.id.au>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	Anshuman Khandual <khandual@...ux.vnet.ibm.com>,
	linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	benh@...nel.crashing.org, anton@...ba.org, mikey@...ling.org
Subject: Re: [PATCH V2 06/12] selftests, powerpc: Add test for system wide
 DSCR default

On Tue, 2015-01-13 at 08:22 -0700, Shuah Khan wrote:
> On 01/13/2015 03:22 AM, Anshuman Khandual wrote:
> > This patch adds a test case for the system wide DSCR default
> > value, which when changed through it's sysfs interface must
> > be visible to all threads reading DSCR either through the
> > privilege state SPR or the problem state SPR. The DSCR value
> > change should be immediate as well.
> > 
> > Signed-off-by: Anshuman Khandual <khandual@...ux.vnet.ibm.com>
> > ---
> >  tools/testing/selftests/powerpc/Makefile           |   2 +-
> >  tools/testing/selftests/powerpc/dscr/Makefile      |  17 +++
> >  tools/testing/selftests/powerpc/dscr/dscr.h        | 120 ++++++++++++++++++++
> >  .../selftests/powerpc/dscr/dscr_default_test.c     | 121 +++++++++++++++++++++
> >  4 files changed, 259 insertions(+), 1 deletion(-)
> >  create mode 100644 tools/testing/selftests/powerpc/dscr/Makefile
> >  create mode 100644 tools/testing/selftests/powerpc/dscr/dscr.h
> >  create mode 100644 tools/testing/selftests/powerpc/dscr/dscr_default_test.c
> 
> Could you please add a .gitignore for powerpc targets as we
> discussed earlier. It can be separate patch.

I can do that.
 
> Also, I would like to see the test results reports using
> kselftest.h - it can be separate patch in the interest of
> getting tests in.

Sorry but kselftest.h doesn't do anything useful for us.

We have existing test reporting that uses the subunit protocol.

I'm happy to convert that to TAP, or some other well defined output format, but
not to something ad-hoc like kselftest.h currently provides.

cheers


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ