Re: Questions about vNVDIMM on qemu/KVM

> > > > But ,I would like understand one more thing. > > In the following mail, it seems that e820 bus will be used for fake DAX. > > > > https://lists.01.org/pipermail/linux-nvdimm/2018-January/013926.html > > > > Could you tell me what is relationship between "fake DAX" in this mail > > and

Re: [PATCH 1/7] fs: allow per-device dax status checking for filesystems

On Thu, May 24, 2018 at 08:55:12PM -0600, Ross Zwisler wrote: > From: "Darrick J. Wong" > > Remove __bdev_dax_supported and change to bdev_dax_supported that takes a > bdev parameter. This enables multi-device filesystems like xfs to check > that a dax device can work

Re: [PATCH 2/7] dax: change bdev_dax_supported() to support boolean returns

On Thu, May 24, 2018 at 08:55:13PM -0600, Ross Zwisler wrote: > From: Dave Jiang > > The function return values are confusing with the way the function is > named. We expect a true or false return value but it actually returns > 0/-errno. This makes the code very

[no subject]

The original message was received at Fri, 25 May 2018 11:26:13 +0800 from lists.01.org [137.8.247.250] - The following addresses had permanent fatal errors - ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org

[PATCH 0/7] Fix DM DAX handling

This series fixes a few issues that I found with DM's handling of DAX devices. Here are some of the issues I found: * We can create a dm-stripe or dm-linear device which is made up of an fsdax PMEM namespace and a raw PMEM namespace but which can hold a filesystem mounted with the -o dax

[PATCH 4/7] dm: prevent DAX mounts if not supported

Currently the code in dm_dax_direct_access() only checks whether the target type has a direct_access() operation defined, not whether the underlying block devices all support DAX. This latter property can be seen by looking at whether we set the QUEUE_FLAG_DAX request queue flag when creating the

[PATCH 1/7] fs: allow per-device dax status checking for filesystems

From: "Darrick J. Wong" Remove __bdev_dax_supported and change to bdev_dax_supported that takes a bdev parameter. This enables multi-device filesystems like xfs to check that a dax device can work for the particular filesystem. Once that's in place, actually fix all

[PATCH 3/7] dm: fix test for DAX device support

Currently device_supports_dax() just checks to see if the QUEUE_FLAG_DAX flag is set on the device's request queue to decide whether or not the device supports filesystem DAX. This is insufficient because there are devices like PMEM namespaces in raw mode which have QUEUE_FLAG_DAX set but which

[PATCH 6/7] dm-snap: remove unnecessary direct_access() stub

This stub was added so that we could use dm-snap with DM_TYPE_DAX_BIO_BASED mode devices. That mode and the transition issues associated with it no longer exist, so we can remove this dead code. Signed-off-by: Ross Zwisler --- drivers/md/dm-snap.c | 8 1

[PATCH 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode

The DM_TYPE_DAX_BIO_BASED dm_queue_mode was introduced to prevent DM devices that could possibly support DAX from transitioning into DM devices that cannot support DAX. For example, the following transition will currently fail: dm-linear: [fsdax pmem][fsdax pmem] => [fsdax pmem][fsdax raw]

[PATCH 2/7] dax: change bdev_dax_supported() to support boolean returns

From: Dave Jiang The function return values are confusing with the way the function is named. We expect a true or false return value but it actually returns 0/-errno. This makes the code very confusing. Changing the return values to return a bool where if DAX is supported

Re: [PATCH 07/11] mm, madvise_inject_error: fix page count leak

On Tue, May 22, 2018 at 9:19 PM, Naoya Horiguchi wrote: > On Tue, May 22, 2018 at 07:40:09AM -0700, Dan Williams wrote: >> The madvise_inject_error() routine uses get_user_pages() to lookup the >> pfn and other information for injected error, but it fails to release >>

Re: Questions about vNVDIMM on qemu/KVM

On Thu, May 24, 2018 at 12:19 AM, Yasunori Goto wrote: >> On Tue, May 22, 2018 at 10:08 PM, Yasunori Goto >> wrote: >> > Hello, >> > >> > I'm investigating status of vNVDIMM on qemu/KVM, >> > and I have some questions about it. I'm glad if anyone

Re: [patch 4/4] dm-writecache: use new API for flushing

On Tue, 22 May 2018, Dan Williams wrote: > On Tue, May 22, 2018 at 11:41 AM, Mike Snitzer wrote: > > On Tue, May 22 2018 at 2:39am -0400, > > Christoph Hellwig wrote: > > > >> On Sat, May 19, 2018 at 07:25:07AM +0200, Mikulas Patocka wrote: > >> > Use

（AD）邀请函： P*M*C-生-产-物-料-计-划

___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm

Re: Questions about vNVDIMM on qemu/KVM

> On Tue, May 22, 2018 at 10:08 PM, Yasunori Goto wrote: > > Hello, > > > > I'm investigating status of vNVDIMM on qemu/KVM, > > and I have some questions about it. I'm glad if anyone answer them. > > > > In my understanding, qemu/KVM has a feature to show NFIT for guest, >