From: Won-Kyo Choe <heysid@ajou.ac.kr>
To: dave.hansen@intel.com
Cc: jsahn@ajou.ac.kr, linux-mm@kvack.org, linux-nvdimm@lists.01.org
Subject: A write error on converting dax0.0 to kmem
Date: Thu, 27 Jun 2019 14:19:53 +0000 [thread overview]
Message-ID: <20190627141953.GC3624@swarm07> (raw)
Hi, Dave. I hope this message is sent appropriately in this time.
We've recently got a new machine which contains Optane DC memory and
tried to use your patch set[1] in a recent kernel version(5.1.15).
Unfortunately, we've failed on the last step[2] that describes
converting device-dax driver as kmem. The main error is "echo: write error: No such device".
We are certain that there must be a device and it should be recognized
since we can see it in a path "/dev/dax0.0", however, somehow it keeps saying that error.
We've followed all your steps in the first patch[1] except a step about qemu configuration
since we already have a persistent memory. We even checked that there is a region
mapped with persistent memory from a command, `dmesg | grep e820` described in below.
BIOS-e820: [mem 0x0000000880000000-0x00000027ffffffff] persistent (type 7)
As the address is shown above, the thing is that in the qemu, the region is set as
persistent (type 12) but in the native machine, it says persistent (type 7).
We've still tried to find what type means and we simply guess that this is one
of the reasons why we are not able to set the device as kmem.
We'd like to know why this error comes up and how can we handle this problem.
We would really appreciate it if you are able to little bit help us.
Regards,
Won-Kyo
1. https://patchwork.kernel.org/cover/10829019/
2. https://patchwork.kernel.org/patch/10829041/
next reply other threads:[~2019-06-27 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 14:19 Won-Kyo Choe [this message]
2019-06-27 21:22 ` Dan Williams
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=20190627141953.GC3624@swarm07 \
--to=heysid@ajou.ac.kr \
--cc=dave.hansen@intel.com \
--cc=jsahn@ajou.ac.kr \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.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