public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests v2 2/2] block/031: allow to run with built-in null_blk driver
Date: Tue, 9 Jan 2024 19:34:49 +0000	[thread overview]
Message-ID: <faea1bbb-cf01-455e-9986-3bbe2391d5f8@nvidia.com> (raw)
In-Reply-To: <20240109104453.3764096-3-shinichiro.kawasaki@wdc.com>

On 1/9/24 02:44, Shin'ichiro Kawasaki wrote:
> The test case block/031 sets null_blk parameter shared_tag_bitmap=1 for
> testing. The parameter has been set as a module parameter then null_blk
> driver must be loadable. However, null_blk allows to set
> shared_tag_bitmap as a configfs parameter since the kernel commit
> 7012eef520cb ("null_blk: add configfs variables for 2 options"). Then
> the test case now can be run with built-in null_blk driver by specifying
> shared_tag_bitmap through configfs.
>
> Modify the test case for that purpose. Refer null_blk feature list and
> check if shared_tag_bitmap can be specified through configfs. If so,
> specify the parameter as an option of _configure_null_blk and set it
> through configfs. If not, check in requires() that shared_tag_bitmap can
> be specified as a module parameter. Then call _init_null_blk() in test()
> and specify shared_tag_bitmap=1 at null_blk module load.
>
> Also change null_blk device name from nullb0 to nullb1 since the default
> null_blk device name nullb0 is not usable with built-in null_blk driver.
>
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> ---
>

Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck



  reply	other threads:[~2024-01-09 19:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 10:44 [PATCH blktests v2 0/2] block/031: allow to run with built-in null_blk driver Shin'ichiro Kawasaki
2024-01-09 10:44 ` [PATCH blktests v2 1/2] common/null_blk: introduce _have_null_blk_feature Shin'ichiro Kawasaki
2024-01-09 19:20   ` Chaitanya Kulkarni
2024-01-09 20:14   ` Bart Van Assche
2024-01-09 10:44 ` [PATCH blktests v2 2/2] block/031: allow to run with built-in null_blk driver Shin'ichiro Kawasaki
2024-01-09 19:34   ` Chaitanya Kulkarni [this message]
2024-01-09 20:19   ` Bart Van Assche
2024-01-10  2:19     ` Shinichiro Kawasaki
2024-01-10 17:50       ` Bart Van Assche
2024-01-11  7:34         ` Shinichiro Kawasaki

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=faea1bbb-cf01-455e-9986-3bbe2391d5f8@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    /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