From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH 1/1] nvme: add get-feature to admin cmds tracer
Date: Mon, 4 Feb 2019 09:23:49 +0100 [thread overview]
Message-ID: <bcbfb9ea-88ff-d8c7-22ba-8f1df7104930@suse.de> (raw)
In-Reply-To: <63c08f3a-a109-9441-df53-6a65b1db9ab9@mellanox.com>
On 31/01/2019 18:01, Max Gurtovoy wrote:
>
> On 1/31/2019 6:11 PM, Keith Busch wrote:
>> On Thu, Jan 31, 2019@05:13:30PM +0200, Max Gurtovoy wrote:
>>> +static const char *nvme_trace_admin_get_features(struct trace_seq *p,
>>> +???????????????????????? u8 *cdw10)
>>> +{
>>> +??? const char *ret = trace_seq_buffer_ptr(p);
>>> +??? u8 fid = cdw10[0];
>>> +??? u8 sel = cdw10[1];
>
> u8 sel = cdw10[1] & 0x7;
Yup
[...]
> Well, I guess that nvme-cli is the only common tool used by the majority
> of the community.
>
> we can add something like "nvme trace-parse <raw-cmd>".
>
> but this will open a various places to go wrong (and it will happen for
> sure).
>
> Let's see what other guys think..
I'm open for both sides, but we're already decoding a bunch of commands
in the kernel and so does the SCSI tracing, so I don't see a compelling
reason to stop it now.
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-02-04 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 15:13 [PATCH 1/1] nvme: add get-feature to admin cmds tracer Max Gurtovoy
2019-01-31 16:11 ` Keith Busch
2019-01-31 17:01 ` Max Gurtovoy
2019-02-04 8:23 ` Johannes Thumshirn [this message]
2019-02-07 10:28 ` Max Gurtovoy
2019-02-08 8:42 ` Christoph Hellwig
2019-02-08 8:49 ` Johannes Thumshirn
2019-02-08 15:30 ` Keith Busch
2019-02-08 15:39 ` Johannes Thumshirn
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=bcbfb9ea-88ff-d8c7-22ba-8f1df7104930@suse.de \
--to=jthumshirn@suse.de \
/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