From: Christoph Hellwig <hch@infradead.org>
To: tndave <tushar.n.dave@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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: Tue, 11 Oct 2016 09:38:06 -0700 [thread overview]
Message-ID: <20161011163806.GA21231@infradead.org> (raw)
In-Reply-To: <4a70e648-a854-55d1-54ac-313b84841d04@oracle.com>
Hi Tushar,
On Fri, Oct 07, 2016 at 01:09:15AM -0700, tndave wrote:
> 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)
But only iff CONFIG_ARCH_ATU is set. Anyway, I'll wait for your patches
to got in first and will then propose getting rid of
CONFIG_ARCH_DMA_ADDR_T_64BIT separately.
next prev parent reply other threads:[~2016-10-11 17:05 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
2016-10-11 16:38 ` Christoph Hellwig [this message]
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=20161011163806.GA21231@infradead.org \
--to=hch@infradead.org \
--cc=chris.hyser@oracle.com \
--cc=davem@davemloft.net \
--cc=egtvedt@samfundet.no \
--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=tushar.n.dave@oracle.com \
--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
Powered by JetHome