1. 06 May, 2024 6 commits
    • David Hildenbrand's avatar
      drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map() · 3d658600
      David Hildenbrand authored
      Patch series "mm: follow_pte() improvements and acrn follow_pte() fixes".
      
      Patch #1 fixes a bunch of issues I spotted in the acrn driver.  It
      compiles, that's all I know.  I'll appreciate some review and testing from
      acrn folks.
      
      Patch #2+#3 improve follow_pte(), passing a VMA instead of the MM, adding
      more sanity checks, and improving the documentation.  Gave it a quick test
      on x86-64 using VM_PAT that ends up using follow_pte().
      
      
      This patch (of 3):
      
      We currently miss handling various cases, resulting in a dangerous
      follow_pte() (previously follow_pfn()) usage.
      
      (1) We're not checking PTE write permissions.
      
      Maybe we should simply always require pte_write() like we do for
      pin_user_pages_fast(FOLL_WRITE)? Hard to tell, so let's check for
      ACRN_MEM_ACCESS_WRITE for now.
      
      (2) We're not rejecting refcounted pages.
      
      As we are not using MMU notifiers, messing with refcounted pages is
      dangerous and can result in use-after-free. Let's make sure to reject them.
      
      (3) We are only looking at the first PTE of a bigger range.
      
      We only lookup a single PTE, but memmap->len may span a larger area.
      Let's loop over all involved PTEs and make sure the PFN range is
      actually contiguous. Reject everything else: it couldn't have worked
      either way, and rather made use access PFNs we shouldn't be accessing.
      
      Link: https://lkml.kernel.org/r/20240410155527.474777-1-david@redhat.com
      Link: https://lkml.kernel.org/r/20240410155527.474777-2-david@redhat.com
      Fixes: 8a6e85f7 ("virt: acrn: obtain pa from VMA with PFNMAP flag")
      Signed-off-by: default avatarDavid Hildenbrand <david@redhat.com>
      Cc: Alex Williamson <alex.williamson@redhat.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Fei Li <fei1.li@intel.com>
      Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
      Cc: Heiko Carstens <hca@linux.ibm.com>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Yonghua Huang <yonghua.huang@intel.com>
      Cc: Sean Christopherson <seanjc@google.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      3d658600
    • Huang Ying's avatar
      mm,swap: add document about RCU read lock and swapoff interaction · d4a34d7f
      Huang Ying authored
      During reviewing a patch to fix the race condition between
      free_swap_and_cache() and swapoff() [1], it was found that the document
      about how to prevent racing with swapoff isn't clear enough.  Especially
      RCU read lock can prevent swapoff from freeing data structures.  So, the
      document is added as comments.
      
      [1] https://lore.kernel.org/linux-mm/c8fe62d0-78b8-527a-5bef-ee663ccdc37a@huawei.com/
      
      Link: https://lkml.kernel.org/r/20240407065450.498821-1-ying.huang@intel.comSigned-off-by: default avatar"Huang, Ying" <ying.huang@intel.com>
      Reviewed-by: default avatarRyan Roberts <ryan.roberts@arm.com>
      Reviewed-by: default avatarDavid Hildenbrand <david@redhat.com>
      Reviewed-by: default avatarMiaohe Lin <linmiaohe@huawei.com>
      Cc: Hugh Dickins <hughd@google.com>
      Cc: Minchan Kim <minchan@kernel.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      d4a34d7f
    • Hao Ge's avatar
      mm/mmap: make accountable_mapping return bool · 2bd9e6ee
      Hao Ge authored
      accountable_mapping() can return bool, so change it.
      
      Link: https://lkml.kernel.org/r/20240407063843.804274-1-gehao@kylinos.cnSigned-off-by: default avatarHao Ge <gehao@kylinos.cn>
      Cc: Liam R. Howlett <Liam.Howlett@oracle.com>
      Cc: Lorenzo Stoakes <lstoakes@gmail.com>
      Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
      Cc: Vlastimil Babka <vbabka@suse.cz>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      2bd9e6ee
    • Hao Ge's avatar
      mm/mmap: make vma_wants_writenotify return bool · 38bc9c28
      Hao Ge authored
      vma_wants_writenotify() should return bool, so change it.
      
      Link: https://lkml.kernel.org/r/20240407062653.803142-1-gehao@kylinos.cnSigned-off-by: default avatarHao Ge <gehao@kylinos.cn>
      Cc: Liam R. Howlett <Liam.Howlett@oracle.com>
      Cc: Lorenzo Stoakes <lstoakes@gmail.com>
      Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
      Cc: Vlastimil Babka <vbabka@suse.cz>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      38bc9c28
    • Ho-Ren (Jack) Chuang's avatar
      memory tier: create CPUless memory tiers after obtaining HMAT info · cf93be18
      Ho-Ren (Jack) Chuang authored
      The current implementation treats emulated memory devices, such as CXL1.1
      type3 memory, as normal DRAM when they are emulated as normal memory
      (E820_TYPE_RAM).  However, these emulated devices have different
      characteristics than traditional DRAM, making it important to distinguish
      them.  Thus, we modify the tiered memory initialization process to
      introduce a delay specifically for CPUless NUMA nodes.  This delay ensures
      that the memory tier initialization for these nodes is deferred until HMAT
      information is obtained during the boot process.  Finally, demotion tables
      are recalculated at the end.
      
      * late_initcall(memory_tier_late_init);
        Some device drivers may have initialized memory tiers between
        `memory_tier_init()` and `memory_tier_late_init()`, potentially bringing
        online memory nodes and configuring memory tiers.  They should be
        excluded in the late init.
      
      * Handle cases where there is no HMAT when creating memory tiers
        There is a scenario where a CPUless node does not provide HMAT
        information.  If no HMAT is specified, it falls back to using the
        default DRAM tier.
      
      * Introduce another new lock `default_dram_perf_lock` for adist
        calculation In the current implementation, iterating through CPUlist
        nodes requires holding the `memory_tier_lock`.  However,
        `mt_calc_adistance()` will end up trying to acquire the same lock,
        leading to a potential deadlock.  Therefore, we propose introducing a
        standalone `default_dram_perf_lock` to protect `default_dram_perf_*`. 
        This approach not only avoids deadlock but also prevents holding a large
        lock simultaneously.
      
      * Upgrade `set_node_memory_tier` to support additional cases, including
        default DRAM, late CPUless, and hot-plugged initializations.  To cover
        hot-plugged memory nodes, `mt_calc_adistance()` and
        `mt_find_alloc_memory_type()` are moved into `set_node_memory_tier()` to
        handle cases where memtype is not initialized and where HMAT information
        is available.
      
      * Introduce `default_memory_types` for those memory types that are not
        initialized by device drivers.  Because late initialized memory and
        default DRAM memory need to be managed, a default memory type is created
        for storing all memory types that are not initialized by device drivers
        and as a fallback.
      
      Link: https://lkml.kernel.org/r/20240405000707.2670063-3-horenchuang@bytedance.comSigned-off-by: default avatarHo-Ren (Jack) Chuang <horenchuang@bytedance.com>
      Signed-off-by: default avatarHao Xiang <hao.xiang@bytedance.com>
      Reviewed-by: default avatar"Huang, Ying" <ying.huang@intel.com>
      Reviewed-by: default avatarJonathan Cameron <Jonathan.Cameron@huawei.com>
      Cc: Alistair Popple <apopple@nvidia.com>
      Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
      Cc: Dan Williams <dan.j.williams@intel.com>
      Cc: Dave Jiang <dave.jiang@intel.com>
      Cc: Gregory Price <gourry.memverge@gmail.com>
      Cc: Michal Hocko <mhocko@suse.com>
      Cc: Ravi Jonnalagadda <ravis.opensrc@micron.com>
      Cc: SeongJae Park <sj@kernel.org>
      Cc: Tejun Heo <tj@kernel.org>
      Cc: Vishal Verma <vishal.l.verma@intel.com>
      Cc: Jonathan Cameron <Jonathan.Cameron@huawie.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      cf93be18
    • Ho-Ren (Jack) Chuang's avatar
      memory tier: dax/kmem: introduce an abstract layer for finding, allocating,... · a72a30af
      Ho-Ren (Jack) Chuang authored
      memory tier: dax/kmem: introduce an abstract layer for finding, allocating, and putting memory types
      
      Patch series "Improved Memory Tier Creation for CPUless NUMA Nodes", v11.
      
      When a memory device, such as CXL1.1 type3 memory, is emulated as normal
      memory (E820_TYPE_RAM), the memory device is indistinguishable from normal
      DRAM in terms of memory tiering with the current implementation.  The
      current memory tiering assigns all detected normal memory nodes to the
      same DRAM tier.  This results in normal memory devices with different
      attributions being unable to be assigned to the correct memory tier,
      leading to the inability to migrate pages between different types of
      memory. 
      https://lore.kernel.org/linux-mm/PH0PR08MB7955E9F08CCB64F23963B5C3A860A@PH0PR08MB7955.namprd08.prod.outlook.com/T/
      
      This patchset automatically resolves the issues.  It delays the
      initialization of memory tiers for CPUless NUMA nodes until they obtain
      HMAT information and after all devices are initialized at boot time,
      eliminating the need for user intervention.  If no HMAT is specified, it
      falls back to using `default_dram_type`.
      
      Example usecase:
      We have CXL memory on the host, and we create VMs with a new system memory
      device backed by host CXL memory.  We inject CXL memory performance
      attributes through QEMU, and the guest now sees memory nodes with
      performance attributes in HMAT.  With this change, we enable the guest
      kernel to construct the correct memory tiering for the memory nodes.
      
      
      This patch (of 2):
      
      Since different memory devices require finding, allocating, and putting
      memory types, these common steps are abstracted in this patch, enhancing
      the scalability and conciseness of the code.
      
      Link: https://lkml.kernel.org/r/20240405000707.2670063-1-horenchuang@bytedance.com
      Link: https://lkml.kernel.org/r/20240405000707.2670063-2-horenchuang@bytedance.comSigned-off-by: default avatarHo-Ren (Jack) Chuang <horenchuang@bytedance.com>
      Reviewed-by: default avatar"Huang, Ying" <ying.huang@intel.com>
      Reviewed-by: default avatarJonathan Cameron <Jonathan.Cameron@huawie.com>
      Cc: Alistair Popple <apopple@nvidia.com>
      Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
      Cc: Dan Williams <dan.j.williams@intel.com>
      Cc: Dave Jiang <dave.jiang@intel.com>
      Cc: Gregory Price <gourry.memverge@gmail.com>
      Cc: Hao Xiang <hao.xiang@bytedance.com>
      Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
      Cc: Michal Hocko <mhocko@suse.com>
      Cc: Ravi Jonnalagadda <ravis.opensrc@micron.com>
      Cc: SeongJae Park <sj@kernel.org>
      Cc: Tejun Heo <tj@kernel.org>
      Cc: Vishal Verma <vishal.l.verma@intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      a72a30af
  2. 26 Apr, 2024 34 commits