From: Tom Hromatka <tom.hromatka@oracle.com>
To: Shuah Khan <shuah@kernel.org>, davem@davemloft.net
Cc: sparclinux@vger.kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, allen.pais@oracle.com,
khalid.aziz@oracle.com, shannon.nelson@oracle.com,
anthony.yznaga@oracle.com, Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 2/2] selftests: sparc64: char: Selftest for privileged ADI driver
Date: Wed, 18 Apr 2018 14:03:37 -0600 [thread overview]
Message-ID: <a44ead3d-8565-2d44-5a28-dfc51d4920d9@oracle.com> (raw)
In-Reply-To: <6ef81e28-7656-ccf5-5d4d-ef315ae250ce@kernel.org>
On 04/18/2018 01:58 PM, Shuah Khan wrote:
> Hi Tom,
>
> On 04/18/2018 10:29 AM, Tom Hromatka wrote:
>> Add a selftest for the sparc64 privileged ADI driver. These
>> tests verify the read(), pread(), write(), pwrite(), and seek()
>> functionality of the driver. The tests also report simple
>> performance statistics:
>>
>> Syscall Call AvgTime AvgSize
>> Count (ticks) (bytes)
>> -------------------------------
>> read 3 167134 8133
>> pread 4 137217 6741
>> write 3 73787 8133
>> pwrite 4 65832 6741
>> seek 10 2422 0
>>
>> Ran 8 tests
>> All tests passed
>>
>> Signed-off-by: Tom Hromatka <tom.hromatka@oracle.com>
>> Reviewed-by: Allen Pais <allen.pais@oracle.com>
> Thanks for the patch. A few comments below:
Thanks for the quick turnaround, Shuah. I'll work through your
comments and get a v2 out in the next few days.
Regards.
Tom
prev parent reply other threads:[~2018-04-18 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 16:29 [PATCH 0/2] sparc64: Add " Tom Hromatka
2018-04-18 16:29 ` [PATCH 1/2] char: " Tom Hromatka
2018-04-19 7:45 ` Greg KH
2018-04-19 13:14 ` Tom Hromatka
2018-04-18 16:29 ` [PATCH 2/2] selftests: sparc64: char: Selftest for " Tom Hromatka
2018-04-18 19:58 ` Shuah Khan
2018-04-18 20:03 ` Tom Hromatka [this message]
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=a44ead3d-8565-2d44-5a28-dfc51d4920d9@oracle.com \
--to=tom.hromatka@oracle.com \
--cc=allen.pais@oracle.com \
--cc=anthony.yznaga@oracle.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=khalid.aziz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shannon.nelson@oracle.com \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®