On Tue, Jun 23, 2020 at 11:17:41PM +0100, Matthew Wilcox wrote: > It might also be nice to have an madvise() MADV_ZERO option so the > application doesn't have to look up the fd associated with that memory > range, but we haven't floated that idea with the customer yet; I just > thought of it now.
So the conversation between OS and kernel goes like this? 1) machine check 2) Kernel unmaps the 4K page surroundinng the poison and sends SIGBUS to the application to say that one cache line is gone 3) App says madvise(MADV_ZERO, that cache line) 4) Kernel says ... "oh, you know how to deal with this" and allocates a new page, copying the 63 good cache lines from the old page and zeroing the missing one. New page is mapped to user. Do you have folks lined up to use that? I don't know that many folks are even catching the SIGBUS :-( -Tony _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-le...@lists.01.org
