From: Kalle Valo <kvalo@kernel.org>
To: Zhenghao Gu <imguzh@gmail.com>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] wifi: ath11k: fix IOMMU errors on buffer rings
Date: Tue, 09 Jan 2024 17:41:46 +0200 [thread overview]
Message-ID: <8734v6ecp1.fsf@kernel.org> (raw)
In-Reply-To: <20231212031914.47339-1-imguzh@gmail.com> (Zhenghao Gu's message of "Mon, 11 Dec 2023 21:19:14 -0600")
Zhenghao Gu <imguzh@gmail.com> writes:
> virt_to_phys doesn't work on systems with IOMMU enabled,
> which have non-identity physical-to-IOVA mappings.
Can you give an example of such system? Just curious where you are
seeing this.
> It leads to IO_PAGE_FAULTs like this:
> [IO_PAGE_FAULT domain=0x0023 address=0x1cce00000 flags=0x0020]
> and no link can be established.
What do you mean with link in this context? Are you talking about 802.11
association?
> This patch changes that to dma_map_single(), which works correctly.
Good catch. And virt_to_phys() documentation even says this:
* This function does not give bus mappings for DMA transfers. In
* almost all conceivable cases a device driver should not be using
* this function
> Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
> Signed-off-by: Zhenghao Gu <imguzh@gmail.com>
Jeff, are you ok with this?
I did some cosmetics changes in the pending branch (removed unnecessary
parenthesis, reverse xmas tree etc), please check:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=fefa43d63e1928fce6e8c2bb626900e9ce98ca69
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-01-09 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 3:19 [PATCH v2] wifi: ath11k: fix IOMMU errors on buffer rings Zhenghao Gu
2024-01-09 15:41 ` Kalle Valo [this message]
2024-01-09 17:04 ` Jeff Johnson
2024-01-10 0:42 ` Zhenghao Gu
2024-01-11 11:18 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734v6ecp1.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=imguzh@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox