[ adding linux-fsdevel and linux-nvdimm ] On Wed, Sep 7, 2016 at 8:36 PM, Xiao Guangrong <guangrong.xiao@xxxxxxxxxxxxxxx> wrote: [..] > However, it is not easy to handle the case that the new VMA overlays with > the old VMA > already got by userspace. I think we have some choices: > 1: One way is completely skipping the new VMA region as current kernel code > does but i > do not think this is good as the later VMAs will be dropped. > > 2: show the un-overlayed portion of new VMA. In your case, we just show the > region > (0x2000 -> 0x3000), however, it can not work well if the VMA is a new > created > region with different attributions. > > 3: completely show the new VMA as this patch does. > > Which one do you prefer? > I don't have a preference, but perhaps this breakage and uncertainty is a good opportunity to propose a more reliable interface for NVML to get the information it needs? My understanding is that it is looking for the VM_MIXEDMAP flag which is already ambiguous for determining if DAX is enabled even if this dynamic listing issue is fixed. XFS has arranged for DAX to be a per-inode capability and has an XFS-specific inode flag. We can make that a common inode flag, but it seems we should have a way to interrogate the mapping itself in the case where the inode is unknown or unavailable. I'm thinking extensions to mincore to have flags for DAX and possibly whether the page is part of a pte, pmd, or pud mapping. Just floating that idea before starting to look into the implementation, comments or other ideas welcome... -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
