Hi Jean, On 4/27/21 4:23 PM, Jean-Philippe Brucker wrote: > On Tue, Apr 27, 2021 at 03:52:46PM +0100, Alexandru Elisei wrote: >> The comment [1] suggested that the panic is triggered during page aging. > I think only with an out-of-tree patch applied > https://jpbrucker.net/git/linux/commit/?h=sva/2021-03-01&id=d32d8baaf293aaefef8a1c9b8a4508ab2ec46c61 > which probably is not going upstream. Thanks for that, that explains why I wasn't able to trigger the notification. I did a grep for all the places where mmu_notifier_change_pte() and set_pte_at_notify() are used in the kernel, and from what I can tell they are only called for a new pte which has a struct page. From my investigation, the notifiers are called from ksm (which deals with physical memory), swap migration (so still pages in memory) and on copy-on-write. On Linux v5.12, I tried to trigger the copy-on-write notification by forking kvmtool right after the BAR region is mapped and then reading from the userspace BAR address, but the new pte (for which the notifier is called) is valid. I also looked at what x86 does, but I couldn't find where cache maintenance is performed (wouldn't surprise me if it's not necessary at all). So I guess my question is what kind of pfns the MMU notifiers for the secondary MMUs are required to handle. If the requirement is that they should handle both device and struct page backed pfns, then the patch looks correct to me (user_mem_abort() also uses kvm_is_device_pfn() to decide if dcache maintenance is needed). Thanks, Alex > Thanks, > Jean > >> vfio_pci_mmap() sets the VM_PFNMAP for the VMA and I see in the Documentation that >> pages with VM_PFNMAP are added to the unevictable LRU list, doesn't that mean it's >> not subject the page aging? I feel like there's something I'm missing. >> >> [1] >> https://lore.kernel.org/kvm/BY5PR12MB37642B9AC7E5D907F5A664F6B3459@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ >> >> Thanks, >> >> Alex
