linux-kernel - Re: [PATCH] dmatest: masking tests for channel capabilities

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]

Message-ID: <CAHp75Vf-bE1cYmj543U=Wk-=iEgTfpnezXSjPjHUiYdM8G-C+A@mail.gmail.com>
Date:	Tue, 18 Jun 2013 23:01:19 +0300
From:	Andy Shevchenko <andy.shevchenko@...il.com>
To:	Dan Williams <djbw@...com>
Cc:	Jubin Mehta <jubin.mehta@...el.com>,
	Vinod Koul <vinod.koul@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	Dave Jiang <dave.jiang@...el.com>,
	Jon Mason <jon.mason@...el.com>
Subject: Re: [PATCH] dmatest: masking tests for channel capabilities

On Tue, Jun 18, 2013 at 10:16 PM, Dan Williams <djbw@...com> wrote:
> On Tue, Jun 18, 2013 at 10:34 AM, Jubin Mehta <jubin.mehta@...el.com> wrote:

>> Would you like to have some changes regarding the configuration
>> process for the module parameters of the dmatest?
>
> Yes, as a first step I would like to see a clean up of the the
> configuration parameters to be available via
> /sys/module/dmatest/parameters rather than /sys/kernel/debug/dmatest

Do  you mean to enable write access to them?

> As for "run" and "results" I see Andy's point that those are a bit
> awkward as parameters.  However, we do have trace points as a more
> general mechanism for dumping events and data to userspace.  If we had
> /sys/module/dmatest/parameters/run with a tracepoint for the result
> line does that get us everything we need for automation?  I can see
> more tracepoints beng added to get some perf metrics out of the tests.

I'm not familiar neither with perf, nor with tracepoints. Could you
elaborate and show here the scheme how it should work? How we will get
results? In what form?


--
With Best Regards,
Andy Shevchenko
--
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/