public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Keith Busch <kbusch@kernel.org>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH 1/2] nvme-core: add ctrl state transition debug helper
Date: Wed, 6 Mar 2024 05:21:11 +0000	[thread overview]
Message-ID: <db18830a-ec4a-411e-b9b3-1951965abbb5@nvidia.com> (raw)
In-Reply-To: <ZedJeFUpuogtBSd5@kbusch-mbp.mynextlight.net>

On 3/5/24 08:34, Keith Busch wrote:
> On Sun, Feb 11, 2024 at 08:26:40PM -0800, Chaitanya Kulkarni wrote:
>> @@ -621,6 +636,9 @@ bool nvme_change_ctrl_state(struct nvme_ctrl *ctrl,
>>   	}
>>   
>>   	if (changed) {
>> +		dev_dbg(ctrl->device, "%s %s -> %s\n", __func__,
>> +			nvme_ctrl_state_str(old_state),
>> +			nvme_ctrl_state_str(new_state));
>>   		WRITE_ONCE(ctrl->state, new_state);
>>   		wake_up_all(&ctrl->state_wq);
>>   	}
> Turing the system logs up to debug level might get you a whole lot of
> unrelated stuff. Could a new trace_event get you what you need instead?
> There's more fine grain control on those.

totally agree with you, I have patches to add few more tracepoints
I'll add v2 to that series and post soon, thanks for the suggestion ...

-ck



  reply	other threads:[~2024-03-06  5:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240212070024epcas5p15af7a6b038a30b3918adc517641b8eb1@epcas5p1.samsung.com>
2024-02-12  4:26 ` [PATCH 1/2] nvme-core: add ctrl state transition debug helper Chaitanya Kulkarni
2024-02-12  4:26   ` [PATCH 2/2] nvme: export and use previously added helper Chaitanya Kulkarni
2024-02-12  6:54     ` Nitesh Shetty
2024-03-07  8:03     ` Sagi Grimberg
2024-02-12  6:53   ` [PATCH 1/2] nvme-core: add ctrl state transition debug helper Nitesh Shetty
2024-02-21  5:34   ` Chaitanya Kulkarni
2024-03-05  4:34     ` Chaitanya Kulkarni
2024-03-05 16:34   ` Keith Busch
2024-03-06  5:21     ` Chaitanya Kulkarni [this message]
2024-03-07  8:03     ` Sagi Grimberg
2024-03-07  8:03   ` Sagi Grimberg

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=db18830a-ec4a-411e-b9b3-1951965abbb5@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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