From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Daniel Wagner <wagi@kernel.org>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests 2/3] nvme/060: add test nvme fabrics target resetting during I/O
Date: Wed, 19 Mar 2025 16:54:03 +0000 [thread overview]
Message-ID: <d9e7020d-9516-4f67-befe-86a47fcb3f49@nvidia.com> (raw)
In-Reply-To: <040089eb-aee4-4311-b1d1-d8d11d242804@flourine.local>
On 3/19/25 02:26, Daniel Wagner wrote:
> On Tue, Mar 18, 2025 at 08:40:39PM +0000, Chaitanya Kulkarni wrote:
>> On 3/18/25 03:39, Daniel Wagner wrote:
>>> Newer kernel support to reset the target via the debugfs. Add a new test
>>> case which exercises this interface.
>>>
>>> Signed-off-by: Daniel Wagner<wagi@kernel.org>
>> Looks useful to me given that its a different code path in the target.
> One thing I forgot to add a check if the feature is available. I think
> the only way is to setup a target and see if the relevant file shows
> up...
perhaps create a controller and in absence of NVMET_DFS skipping the
test with right reason is a way to go ?
It will also be helpful if you just create a helper that will create
a controller that way any future tests that needs to check for
specific feature via configfs files can use it. That helper will also
get called from requires() in order to set the right SKIP_REASON.
>> do we have any testcaes similar for non-debugfs code path ?
>> (don't remember at this point)
> There is not direct way to trigger a target reset via a nvme command
> yet. The upcoming TP8028 brings cross controller reset.
It will be nice.
> We have an indirect way to trigger a reset, via changing the number of
> queues the target supports (this test case is already there).
ahh thanks..
-ck
next prev parent reply other threads:[~2025-03-19 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:38 [PATCH blktests 0/3] blktests: add target test cases Daniel Wagner
2025-03-18 10:38 ` [PATCH blktests 1/3] common/nvme: add debug nvmet path variable Daniel Wagner
2025-03-18 20:37 ` Chaitanya Kulkarni
2025-04-04 8:03 ` Shinichiro Kawasaki
2025-04-04 10:08 ` Daniel Wagner
2025-03-18 10:39 ` [PATCH blktests 2/3] nvme/060: add test nvme fabrics target resetting during I/O Daniel Wagner
2025-03-18 20:40 ` Chaitanya Kulkarni
2025-03-19 9:26 ` Daniel Wagner
2025-03-19 16:54 ` Chaitanya Kulkarni [this message]
2025-04-04 8:08 ` Shinichiro Kawasaki
2025-04-04 10:15 ` Daniel Wagner
2025-03-18 10:39 ` [PATCH blktests 3/3] nvme/061: add test teardown and setup fabrics target " Daniel Wagner
2025-03-18 20:42 ` Chaitanya Kulkarni
2025-04-04 8:22 ` Shinichiro Kawasaki
2025-04-04 10:16 ` Daniel Wagner
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=d9e7020d-9516-4f67-befe-86a47fcb3f49@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=wagi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.