From: William Davis <wdavis@nvidia.com>
To: "Goz, Ben" <Ben.Goz@amd.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"Bridgman, John" <John.Bridgman@amd.com>,
Terence Ripperda <TRipperda@nvidia.com>,
"John Hubbard" <jhubbard@nvidia.com>
Subject: RE: IOMMU/DMA map_resource support for peer-to-peer
Date: Tue, 22 Dec 2015 16:18:58 +0000 [thread overview]
Message-ID: <05d2feba45a84e67b63fb8f15e8bfa02@HQMAIL106.nvidia.com> (raw)
In-Reply-To: <BY2PR12MB0290BA809C4EB9D64A810155E8E50@BY2PR12MB0290.namprd12.prod.outlook.com>
> Hi Will I can't find your commits on linux-pci git repository and the only
> tag that I can think that you meant to say is pci-v4.2-fixes-2 and the
> patches not found there.
> Can you please refer me to the exact place I can find the patch set?
>
As I said below, the patches aren't hosted in any externally-accessible repo - that is, the only git repository to which the patches have been committed is a local development repo that is a clone of linux-pci.
Each of the patch set versions are only available via the mailing list archives, e.g., (this is the latest version)
http://www.spinics.net/lists/linux-pci/msg44560.html
You'll have to apply the patches manually.
>
> Hi Ben,
>
> > I'm interesting on your work on this patch set to support map_resource
> > for peer to peer memory mapping, if you can please refer me to git
> > repository includes your patches.
>
> The patches are not hosted in any externally-accessible repo. The last
> patch set was built on top of the linux-pci tree at commit
> bc0195aad0daa2ad5b0d76cce22b167bc3435590 (linux 4.2-rc2).
>
> > And I want to know please if the IOMMU should be configured with pass
> > through or any other configuration, and if there is a general
> > limitation or something I should know for bringing it up.
>
> My testing was mostly Intel-based, but it did not require passthrough mode;
> the goal of the patches was to get PCI P2P working on configurations where
> the IOMMU is configured for full translation. It should only be limited to
> what the chipset is capable of, in terms of PCI P2P topologies.
>
> Thanks,
> Will
>
--
nvpublic
prev parent reply other threads:[~2015-12-22 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 15:32 IOMMU/DMA map_resource support for peer-to-peer Goz, Ben
2015-12-21 16:45 ` William Davis
2015-12-22 14:19 ` Goz, Ben
2015-12-22 16:18 ` William Davis [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=05d2feba45a84e67b63fb8f15e8bfa02@HQMAIL106.nvidia.com \
--to=wdavis@nvidia.com \
--cc=Ben.Goz@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=John.Bridgman@amd.com \
--cc=TRipperda@nvidia.com \
--cc=jhubbard@nvidia.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).