All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@linux.intel.com (Keith Busch)
Subject: nvme-cli shows failed to map on Kernel 4.16.16
Date: Wed, 18 Jul 2018 17:12:11 -0600	[thread overview]
Message-ID: <20180718231211.GE32160@localhost.localdomain> (raw)
In-Reply-To: <CAGSHeY1JpRAXzbdYKpwVnB5Wug=6iyUZVUqLteQCgOOEqq5RoA@mail.gmail.com>

On Wed, Jul 18, 2018@04:08:43PM -0700, Yogi Wannabe wrote:
> Hi all,
> 
> I downloaded the latest nvme-cli-master and ran the following command
> on a Centos 7.4 with kernel 3.19.8. The command worked fine
> 
> ./nvme list /dev/nvme0n1
> 
> I ran the same command on a Debian 9.5 with Kernel 4.16.16 and I got
> the error msg "failed to map". Googling led me to this link
> https://github.com/linux-nvme/nvme-cli/issues/81
> 
> I checked the kernel configuration on 4.16.16 and I see this setting:
> CONFIG_IO_STRICT_DEVMEM=y
> 
> Does this mean that nvme list won't work until I rebuild the kernel
> with CONFIG_IO_STRICT_DEVMEM=n?

That is correct, you will not be able to use that command when
CONFIG_IO_STRICT_DEVMEM=y. When that kernel config option is set, the
kernel will not allow user space to mmap io memory if a driver also
mapped it.

  reply	other threads:[~2018-07-18 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 23:08 nvme-cli shows failed to map on Kernel 4.16.16 Yogi Wannabe
2018-07-18 23:12 ` Keith Busch [this message]
2018-07-19 12:41   ` Christoph Hellwig

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=20180718231211.GE32160@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.