From: Jason Gunthorpe <jgg@ziepe.ca>
To: mpenttil@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
apopple@nvidia.com, jhubbard@nvidia.com, rcampbell@nvidia.com,
vbabka@suse.cz
Subject: Re: [PATCH v6] mm/hmm/test: use char dev with struct device to get device node
Date: Wed, 30 Mar 2022 11:34:58 -0300 [thread overview]
Message-ID: <20220330143458.GM64706@ziepe.ca> (raw)
In-Reply-To: <20220330004725.13428-1-mpenttil@redhat.com>
On Wed, Mar 30, 2022 at 03:47:25AM +0300, mpenttil@redhat.com wrote:
> From: Mika Penttilä <mpenttil@redhat.com>
>
> HMM selftests use an in-kernel pseudo device to emulate device private
> memory. The pseudo device registers a major device range for two pseudo
> device instances. User space has a script that reads /proc/devices in
> order to find the assigned major number, and sends that to mknod(1),
> once for each node.
>
> Change this to properly use cdev and struct device APIs.
>
> Delete the /proc/devices parsing from the user-space test script, now
> that it is unnecessary.
>
> Also, deleted an unused field in struct dmirror_device: devmem.
>
> Signed-off-by: Mika Penttilä <mpenttil@redhat.com>
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>
> Cc: Alistair Popple <apopple@nvidia.com>
> Cc: Ralph Campbell <rcampbell@nvidia.com>
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Vlastimil Babka <vbabka@suse.cz>
> ---
> v6:
> - remove device names array
> - check return value of dev_set_name()
> v5:
> - fix whitespace
> . delete unused structure field
> v4:
> - fix commit log
> v3:
> - use cdev_device_add() instead of miscdevice
> v2:
> - Cleanups per review comments from John Hubbard
> - Added Tested-by and Ccs
>
>
> lib/test_hmm.c | 13 ++++++++++---
> tools/testing/selftests/vm/test_hmm.sh | 6 ------
> 2 files changed, 10 insertions(+), 9 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
prev parent reply other threads:[~2022-03-30 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 0:47 mpenttil
2022-03-30 5:18 ` Christoph Hellwig
2022-03-30 14:34 ` Jason Gunthorpe [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=20220330143458.GM64706@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=apopple@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpenttil@redhat.com \
--cc=rcampbell@nvidia.com \
--cc=vbabka@suse.cz \
/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