From: hch@infradead.org (Christoph Hellwig)
Subject: nvme-cli shows failed to map on Kernel 4.16.16
Date: Thu, 19 Jul 2018 05:41:58 -0700 [thread overview]
Message-ID: <20180719124158.GA3147@infradead.org> (raw)
In-Reply-To: <20180718231211.GE32160@localhost.localdomain>
On Wed, Jul 18, 2018@05:12:11PM -0600, Keith Busch wrote:
> 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.
Yikes. We really ought to have a way to scrape that information
without reading the bar..
prev parent reply other threads:[~2018-07-19 12:41 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
2018-07-19 12:41 ` Christoph Hellwig [this message]
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=20180719124158.GA3147@infradead.org \
--to=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).