Thread (33 messages) 33 messages, 5 authors, 2021-12-15

Re: [PATCH 5/5] dax: always use _copy_mc_to_iter in dax_copy_to_iter

From: Vivek Goyal <vgoyal@redhat.com>
Date: 2021-12-14 13:59:09
Also in: dm-devel, linux-fsdevel, nvdimm, virtualization

On Sun, Dec 12, 2021 at 06:48:05AM -0800, Dan Williams wrote:
On Fri, Dec 10, 2021 at 6:05 AM Vivek Goyal [off-list ref] wrote:
quoted
On Thu, Dec 09, 2021 at 07:38:28AM +0100, Christoph Hellwig wrote:
quoted
While using the MC-safe copy routines is rather pointless on a virtual device
like virtiofs,
I was wondering about that. Is it completely pointless.

Typically we are just mapping host page cache into qemu address space.
That shows as virtiofs device pfn in guest and that pfn is mapped into
guest application address space in mmap() call.

Given on host its DRAM, so I would not expect machine check on load side
so there was no need to use machine check safe variant.
That's a broken assumption, DRAM experiences multi-bit ECC errors.
Machine checks, data aborts, etc existed before PMEM.
So we should use MC safe variant when loading from DRAM as well?
(If needed platoform support is there).

Vivek
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help