From: tndave <tushar.n.dave@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: davem@davemloft.net, chris.hyser@oracle.com,
sowmini.varadhan@oracle.com, vgupta@synopsys.com,
robin.murphy@arm.com, jroedel@suse.de, egtvedt@samfundet.no,
krzk@kernel.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 6/6] sparc64: Enable 64-bit DMA
Date: Fri, 7 Oct 2016 01:09:15 -0700 [thread overview]
Message-ID: <4a70e648-a854-55d1-54ac-313b84841d04@oracle.com> (raw)
In-Reply-To: <20161007073252.GA8290@infradead.org>
On 10/07/2016 12:32 AM, Christoph Hellwig wrote:
> On Thu, Oct 06, 2016 at 04:33:36PM -0700, Tushar Dave wrote:
>> ATU 64bit addressing allows PCIe devices with 64bit DMA capabilities
>> to use ATU for 64bit DMA.
>
> Any chance to always enable this? Last I checked sparc was the only
> architecture still using a 32-bit dma_addr_t, leading to some fun
> breakage in things like the software RDMA drivers that abuse it to
> store a kernel pointer..
With change made by patch 6/6, dma_addr_t is always 64-bit, no matter if
device DMA mask is 32-bit (i.e. using existing IOMMU) or 64-bit (i.e
using ATU)
-Tushar
>
next prev parent reply other threads:[~2016-10-07 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 23:33 [RFC PATCH 0/6] sparc: Enable sun4v hypervisor PCI IOMMU v2 APIs and ATU Tushar Dave
2016-10-06 23:33 ` [RFC PATCH 1/6] sparc64: Add FORCE_MAX_ZONEORDER and default to 13 Tushar Dave
2016-10-06 23:33 ` [RFC PATCH 2/6] sparc64: Add ATU (new IOMMU) support Tushar Dave
2016-10-06 23:33 ` [RFC PATCH 3/6] sparc64: Initialize iommu_map_table and iommu_pool Tushar Dave
2016-10-06 23:33 ` [RFC PATCH 4/6] sparc64: Bind PCIe devices to use IOMMU v2 service Tushar Dave
2016-10-06 23:33 ` [RFC PATCH 5/6] sparc64: Enable sun4v dma ops to use IOMMU v2 APIs Tushar Dave
2016-10-06 23:33 ` [RFC PATCH 6/6] sparc64: Enable 64-bit DMA Tushar Dave
2016-10-07 7:32 ` Christoph Hellwig
2016-10-07 8:09 ` tndave [this message]
2016-10-11 16:38 ` Christoph Hellwig
2016-10-11 19:42 ` tndave
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=4a70e648-a854-55d1-54ac-313b84841d04@oracle.com \
--to=tushar.n.dave@oracle.com \
--cc=chris.hyser@oracle.com \
--cc=davem@davemloft.net \
--cc=egtvedt@samfundet.no \
--cc=hch@infradead.org \
--cc=jroedel@suse.de \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=sowmini.varadhan@oracle.com \
--cc=sparclinux@vger.kernel.org \
--cc=vgupta@synopsys.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
all inboxes | Powered by JetHome®