From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: "Alex Deucher" <alexdeucher@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Linux PCI" <linux-pci@vger.kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Christian König" <christian.koenig@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Andrew Maier" <andrew.maier@eideticom.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] PCI/P2PDMA: Add AMD Zen 2 root complex to the list of allowed bridges
Date: Fri, 24 Jul 2020 10:06:41 -0500 [thread overview]
Message-ID: <20200724150641.GA1518875@bjorn-Precision-5520> (raw)
In-Reply-To: <89d853d1-9e45-1ba5-5be7-4bbce79c7fb8@deltatee.com>
On Thu, Jul 23, 2020 at 02:10:52PM -0600, Logan Gunthorpe wrote:
> On 2020-07-23 1:57 p.m., Bjorn Helgaas wrote:
> > On Thu, Jul 23, 2020 at 02:01:17PM -0400, Alex Deucher wrote:
> >> On Thu, Jul 23, 2020 at 1:43 PM Logan Gunthorpe <logang@deltatee.com> wrote:
> >>>
> >>> The AMD Zen 2 root complex (Starship/Matisse) was tested for P2PDMA
> >>> transactions between root ports and found to work. Therefore add it
> >>> to the list.
> >>>
> >>> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> >>> Cc: Bjorn Helgaas <bhelgaas@google.com>
> >>> Cc: Christian König <christian.koenig@amd.com>
> >>> Cc: Huang Rui <ray.huang@amd.com>
> >>> Cc: Alex Deucher <alexdeucher@gmail.com>
> >>
> >> Starting with Zen, all AMD platforms support P2P for reads and writes.
> >
> > What's the plan for getting out of the cycle of "update this list for
> > every new chip"? Any new _DSMs planned, for instance?
>
> Well there was an effort to add capabilities in the PCI spec to describe
> this but, as far as I know, they never got anywhere, and hardware still
> doesn't self describe with this.
Any idea what happened? Is there hope for the future? I'm really not
happy about signing up for open-ended device-specific patches like
this. It's certainly not in the plug and play spirit that has made
PCI successful. I know, preaching to the choir here.
Bjorn
next prev parent reply other threads:[~2020-07-24 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 17:43 Logan Gunthorpe
2020-07-23 18:01 ` Alex Deucher
2020-07-23 19:57 ` Bjorn Helgaas
2020-07-23 20:10 ` Logan Gunthorpe
2020-07-23 20:18 ` Alex Deucher
2020-07-23 20:45 ` Logan Gunthorpe
2020-07-24 16:07 ` Alex Deucher
2020-07-24 19:20 ` Logan Gunthorpe
2020-07-24 15:06 ` Bjorn Helgaas [this message]
2020-07-24 15:56 ` Logan Gunthorpe
2020-07-27 9:20 ` Jonathan Cameron
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=20200724150641.GA1518875@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=alexdeucher@gmail.com \
--cc=andrew.maier@eideticom.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=ray.huang@amd.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®