All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@linux.intel.com (Keith Busch)
Subject: NVME-CLI : Fabrics property-get and 64 bit property (CAP)
Date: Tue, 19 Jun 2018 14:25:14 -0600	[thread overview]
Message-ID: <20180619202514.GG19922@localhost.localdomain> (raw)
In-Reply-To: <CAPrnrPCM79jUwngOQd0t6-pT3RocHNBnt_TS059d+NK-rodqDA@mail.gmail.com>

On Tue, Jun 19, 2018@11:00:00PM +0300, Eyal BenDavid wrote:
> Does it mean that a user space program can't get the missing dword by
> nvme-cli / ioctl ?

Right, no way to get this back to user space through the ioctl.

> Is there another way to get the information from user space? (e.g.
> sysfs / proc / dmesg etc)

Yeah, you should be able to see it if you've a recent enough kernel with
event tracers enabled. First enable the tracing:

  echo 1 > /sys/kernel/debug/tracing/events/nvme/enable

Then after running your nvme command, you should see the result with:

  cat /sys/kernel/debug/tracing/trace

  reply	other threads:[~2018-06-19 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 16:23 NVME-CLI : Fabrics property-get and 64 bit property (CAP) Eyal BenDavid
2018-06-19 17:54 ` Daniel Verkamp
2018-06-19 19:02   ` Eyal BenDavid
2018-06-19 19:48     ` Keith Busch
2018-06-19 20:00       ` Eyal BenDavid
2018-06-19 20:25         ` Keith Busch [this message]
2018-06-19 20:55           ` Eyal BenDavid
2018-06-19 21:33             ` Eyal BenDavid
2018-06-20 16:20               ` Eyal BenDavid

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=20180619202514.GG19922@localhost.localdomain \
    --to=keith.busch@linux.intel.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 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.