From: William Davis <wdavis@nvidia.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "joro@8bytes.org" <joro@8bytes.org>,
"jglisse@redhat.com" <jglisse@redhat.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
John Hubbard <jhubbard@nvidia.com>,
Terence Ripperda <TRipperda@nvidia.com>
Subject: RE: [PATCH 0/6] IOMMU/DMA map_resource support for peer-to-peer
Date: Mon, 11 May 2015 19:49:20 +0000 [thread overview]
Message-ID: <2fb918c2fb734b4189a5ab2a25d98de8@HQMAIL106.nvidia.com> (raw)
In-Reply-To: <20150508202134.GB26795@l.oracle.com>
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Friday, May 08, 2015 3:22 PM
> To: William Davis
> Cc: joro@8bytes.org; jglisse@redhat.com; linux-pci@vger.kernel.org; iommu@lists.linux-foundation.org;
> John Hubbard; Terence Ripperda
> Subject: Re: [PATCH 0/6] IOMMU/DMA map_resource support for peer-to-peer
>
> ...
> >
> > The Intel and nommu versions have been verified on a dual Intel Xeon E5405
> > workstation. I'm in the process of obtaining hardware to test the AMD version
> > as well. Please review.
>
> Does it work if you boot with 'iommu=soft swiotlb=force' which will mandate
> an strict usage of the DMA API?
>
This patch series doesn't yet add a SWIOTLB implementation, and so the dma_map_resource() call would return 0 to indicate the path is not implemented (see patch 2/6). So no, the new interfaces would not work with that configuration, but they're also not expected to at this point.
Thanks,
Will
--
nvpublic
next prev parent reply other threads:[~2015-05-11 19:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 18:32 [PATCH 0/6] IOMMU/DMA map_resource support for peer-to-peer wdavis
2015-05-01 18:32 ` [PATCH 1/6] dma-debug: add checking for map/unmap_resource wdavis
2015-05-01 18:32 ` [PATCH 2/6] DMA-API: Introduce dma_(un)map_resource wdavis
2015-05-07 15:09 ` Bjorn Helgaas
2015-05-07 16:10 ` William Davis
2015-05-01 18:32 ` [PATCH 3/6] dma-mapping: pci: add pci_(un)map_resource wdavis
2015-05-07 15:19 ` Bjorn Helgaas
2015-05-11 14:30 ` Konrad Rzeszutek Wilk
2015-05-11 15:27 ` Bjorn Helgaas
2015-05-01 18:32 ` [PATCH 4/6] iommu/amd: Implement (un)map_resource wdavis
2015-05-01 18:32 ` [PATCH 5/6] iommu/vt-d: implement (un)map_resource wdavis
2015-05-01 18:32 ` [PATCH 6/6] x86: add pci-nommu implementation of map_resource wdavis
2015-05-07 15:08 ` Bjorn Helgaas
2015-05-07 16:07 ` William Davis
2015-05-06 22:18 ` [PATCH 0/6] IOMMU/DMA map_resource support for peer-to-peer Bjorn Helgaas
2015-05-06 22:30 ` Alex Williamson
2015-05-07 1:48 ` Yijing Wang
2015-05-07 13:13 ` Bjorn Helgaas
2015-05-07 16:23 ` William Davis
2015-05-07 17:16 ` Bjorn Helgaas
2015-05-07 18:11 ` Jerome Glisse
2015-05-11 19:21 ` Don Dutile
2015-05-08 20:21 ` Konrad Rzeszutek Wilk
2015-05-11 19:49 ` William Davis [this message]
[not found] ` <554D2099.2030907@compro.net>
2015-05-11 14:32 ` Konrad Rzeszutek Wilk
2015-05-11 20:05 ` William Davis
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=2fb918c2fb734b4189a5ab2a25d98de8@HQMAIL106.nvidia.com \
--to=wdavis@nvidia.com \
--cc=TRipperda@nvidia.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).