RE: [RFC PATCH v2 1/7] IB/mlx5: Change ib_umem_odp_map_dma_single_page() to retain umem_mutex

2022-11-17 Thread Daisuke Matsuda (Fujitsu)
On Thu, Nov 17, 2022 10:21 PM Li, Zhijian wrote: > On 11/11/2022 17:22, Daisuke Matsuda wrote: > > ib_umem_odp_map_dma_single_page(), which has been used only by the mlx5 > > driver, holds umem_mutex on success and releases on failure. This > > behavior is not convenient for other drivers to use it

Re: [PATCH v2 2/2] ACPI: HMAT: Fix initiator registration for single-initiator systems

2022-11-17 Thread Rafael J. Wysocki
On 11/17/2022 12:37 AM, Vishal Verma wrote: In a system with a single initiator node, and one or more memory-only 'target' nodes, the memory-only node(s) would fail to register their initiator node correctly. i.e. in sysfs: # ls /sys/devices/system/node/node0/access0/targets/ node0 Where

Re: [RFC PATCH v2 1/7] IB/mlx5: Change ib_umem_odp_map_dma_single_page() to retain umem_mutex

2022-11-17 Thread lizhij...@fujitsu.com
On 11/11/2022 17:22, Daisuke Matsuda wrote: > ib_umem_odp_map_dma_single_page(), which has been used only by the mlx5 > driver, holds umem_mutex on success and releases on failure. This > behavior is not convenient for other drivers to use it, so change it to > always retain mutex on return. > >