From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 85A4A304BA3 for ; Fri, 1 May 2026 17:00:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.13 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777654841; cv=none; b=Vau730XW/p+e4j24Qf7karjo8hWlLNxSo+5HN7xaTmpqj9qovdieAxOkxUbhbeUycILNzDEvfVZ+RUAFBWSc6rCjjwSn+gkhy2LlvQqyJWHHYIDOPCEHeLN2/jcWEGkLpu6FNlUtSdRh9NB9ZtpABOP8ta9rXm4KJVkQZo5ULq8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777654841; c=relaxed/simple; bh=MMHiPEfA3OPcjaDzqcD1mgeXkac1NUhCuQyTITSnWnU=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=bVFFniYq3HXj/Rygzvq2KUXheH9mfTben5uNGi8COMbiv/BGWvphPQVPK9PXAhm6vMjr3Yg3Gn3G2uXdyD1bL1O8LFnWxlMsWgEtoIrin8kU5RaSSXEcFibVYWIabE35NUWJr/5RLnIfT8fC/1kikpXGhE3dwSAQixqAWAFuGhI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=GX3rAXP6; arc=none smtp.client-ip=192.198.163.13 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="GX3rAXP6" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1777654837; x=1809190837; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=MMHiPEfA3OPcjaDzqcD1mgeXkac1NUhCuQyTITSnWnU=; b=GX3rAXP6K9mv7jKWC0E5fkmGvcT8D6xkJktt/Vl338pBFKG9hXdlte7v t7z6eGa6O9Hz/CvL4bHK+Wzy7YTlfIy1B8uDm9vAShdPsbUkk2iqvRuge ESxQLYDOzmRPzxZst1stRq55Ou5Pxt1JXImnPCpghCoOJn3r691RuYzrg eKTtOqTqdxu3UaeNbaP8j/AnqQ4tEplRens2i3c/ZcKAszxtz3SOL+5pK LJNwfixNgLTqju0jFVkqB5CKsdoHkvPpveRAeDh1xoBIQgEZiJ/mf/Df2 Te0hKxwf1o7T6QOvFVV5Qd468/5ZdxX9hfSYvGmN4YOKyFNI2LCBjiVhb A==; X-CSE-ConnectionGUID: J4QD3zZITNmSmi7LgYtnZQ== X-CSE-MsgGUID: 7jQH3fTxRXi7lALkuQ960w== X-IronPort-AV: E=McAfee;i="6800,10657,11773"; a="81186466" X-IronPort-AV: E=Sophos;i="6.23,210,1770624000"; d="scan'208";a="81186466" Received: from orviesa004.jf.intel.com ([10.64.159.144]) by fmvoesa107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 May 2026 10:00:29 -0700 X-CSE-ConnectionGUID: KsjoK2uUTASap7x3n6yknw== X-CSE-MsgGUID: ECdjj8MUQNW2v1RUXRgJGA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,210,1770624000"; d="scan'208";a="239233535" Received: from aduenasd-mobl5.amr.corp.intel.com (HELO [10.125.109.150]) ([10.125.109.150]) by orviesa004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 May 2026 10:00:28 -0700 Message-ID: <4dcc8e09-3e8c-4d94-b5b2-a025ae375b08@intel.com> Date: Fri, 1 May 2026 10:00:28 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 2/6] ntb: Use consistent DMA attributes when freeing DMA mappings To: Leon Romanovsky , Marek Szyprowski , Robin Murphy , Jon Mason , Allen Hubbe Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org, ntb@lists.linux.dev References: <20260501-dma-attrs-debug-v2-0-8dbac75cd501@nvidia.com> <20260501-dma-attrs-debug-v2-2-8dbac75cd501@nvidia.com> Content-Language: en-US From: Dave Jiang In-Reply-To: <20260501-dma-attrs-debug-v2-2-8dbac75cd501@nvidia.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 4/30/26 11:35 PM, Leon Romanovsky wrote: > From: Leon Romanovsky > > The counterpart of dma_alloc_attrs() is dma_free_attrs(), which must > receive the same DMA attributes used during allocation. The code > previously used dma_free_coherent(), which does not accept or apply any > DMA attributes. > > Fixes: 061a785a114f ("ntb: Force physically contiguous allocation of rx ring buffers") > Signed-off-by: Leon Romanovsky Reviewed-by: Dave Jiang > --- > drivers/ntb/ntb_transport.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c > index 771eb7d9f4356..f59f926d4bfaa 100644 > --- a/drivers/ntb/ntb_transport.c > +++ b/drivers/ntb/ntb_transport.c > @@ -766,8 +766,8 @@ static void ntb_free_mw(struct ntb_transport_ctx *nt, int num_mw) > return; > > ntb_mw_clear_trans(nt->ndev, PIDX, num_mw); > - dma_free_coherent(dma_dev, mw->alloc_size, > - mw->alloc_addr, mw->original_dma_addr); > + dma_free_attrs(dma_dev, mw->alloc_size, mw->alloc_addr, > + mw->original_dma_addr, DMA_ATTR_FORCE_CONTIGUOUS); > mw->xlat_size = 0; > mw->buff_size = 0; > mw->alloc_size = 0; > @@ -828,8 +828,8 @@ static int ntb_alloc_mw_buffer(struct ntb_transport_mw *mw, > return 0; > > err: > - dma_free_coherent(ntb_dev, mw->alloc_size, alloc_addr, dma_addr); > - > + dma_free_attrs(ntb_dev, mw->alloc_size, alloc_addr, dma_addr, > + DMA_ATTR_FORCE_CONTIGUOUS); > return rc; > } > >