From: patchwork-bot+netdevbpf@kernel.org
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: kuba@kernel.org, davem@davemloft.net, wintera@linux.ibm.com,
wenjia@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-pci@vger.kernel.org, mjrosato@linux.ibm.com,
pmorel@linux.ibm.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH net-next] s390/ism: Set DMA coherent mask
Date: Thu, 25 May 2023 14:00:21 +0000 [thread overview]
Message-ID: <168502322128.12931.12742922917026189347.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230524075411.3734141-1-schnelle@linux.ibm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 24 May 2023 09:54:10 +0200 you wrote:
> A future change will convert the DMA API implementation from the
> architecture specific arch/s390/pci/pci_dma.c to using the common code
> drivers/iommu/dma-iommu.c which the utilizes the same IOMMU hardware
> through the s390-iommu driver. Unlike the s390 specific DMA API this
> requires devices to correctly set the coherent mask to be allowed to use
> IOVAs >2^32 in dma_alloc_coherent(). This was however not done for ISM
> devices. ISM requires such addresses since currently the DMA aperture
> for PCI devices starts at 2^32 and all calls to dma_alloc_coherent()
> would thus fail.
>
> [...]
Here is the summary with links:
- [net-next] s390/ism: Set DMA coherent mask
https://git.kernel.org/netdev/net-next/c/657d42cf5df6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-25 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 7:54 [PATCH net-next] s390/ism: Set DMA coherent mask Niklas Schnelle
2023-05-25 14:00 ` patchwork-bot+netdevbpf [this message]
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=168502322128.12931.12742922917026189347.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pmorel@linux.ibm.com \
--cc=schnelle@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.com \
/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