From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: iomap 5.15 branch construction ...
Date: Tue, 3 Aug 2021 18:40:24 +1000 [thread overview]
Message-ID: <20210803084024.GJ2757197@dread.disaster.area> (raw)
In-Reply-To: <YQj7oYHpz3zqOGCB@infradead.org>
On Tue, Aug 03, 2021 at 09:17:37AM +0100, Christoph Hellwig wrote:
> I'm on vacation this week, so just a quick note:
>
> I'd love to see 1. and 2. from your list in a public branch ASAP,
> maybe also 3 and 4 if they get positive reviews so that I can
> rebased the iter stuff ontop of that so that I can repost the iter
> series with that as a baseline.
>
> I still haven't succeeded getting a working DAX setup, though.
Just set up a VM with a chunk of RAM and then use the memmap=
command line option to use some of that RAM as pmem. I use a VM with 32GB
of RAM (-m 32768) and then use this command line:
-append "console=ttyS0,115200 root=/dev/sda1 scsi_debug.add_host=0 memmap=8G!15G,8G!24G $1"
that gives me two 8GB pmem devices, one at a base address of 15GB
and the other at a base address of 24GB. This is the only way I've
been able to get "pmem" to work reliably with qemu. The persistence
lasts for the qemu process lifetime, so you can reboot the VM and
the devices still contain the data from the previous boot, but they
do not persist across restarting the qemu process.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2021-08-03 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 22:11 iomap 5.15 branch construction Darrick J. Wong
2021-08-02 22:31 ` Andreas Gruenbacher
2021-08-02 22:34 ` Eric Biggers
2021-08-03 16:42 ` Darrick J. Wong
2021-08-03 0:21 ` Gao Xiang
2021-08-03 16:42 ` Darrick J. Wong
2021-08-03 3:21 ` Matthew Wilcox
2021-08-03 8:17 ` Christoph Hellwig
2021-08-03 8:40 ` Dave Chinner [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=20210803084024.GJ2757197@dread.disaster.area \
--to=david@fromorbit.com \
--cc=agruenba@redhat.com \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@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).