All of lore.kernel.org
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Bjorn Helgaas <helgaas@kernel.org>
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>,
	"Jonathan Cameron" <jonathan.cameron@huawei.com>
Subject: Re: [PATCH] PCI/P2PDMA: Add AMD Zen 2 root complex to the list of allowed bridges
Date: Fri, 24 Jul 2020 09:56:39 -0600	[thread overview]
Message-ID: <59b68da4-cd3c-bf65-6654-02d4feaede27@deltatee.com> (raw)
In-Reply-To: <20200724150641.GA1518875@bjorn-Precision-5520>

[+cc Jonathan]

On 2020-07-24 9:06 a.m., Bjorn Helgaas wrote:
> 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.

Agreed, though I'm not really hooked into the PCI SIG. The last email I
got about this was an RFC from Jonathan Cameron in late 2018. I've CC'd
him here, maybe he'll have a bit more insight.

Logan

  reply	other threads:[~2020-07-24 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 17:43 [PATCH] PCI/P2PDMA: Add AMD Zen 2 root complex to the list of allowed bridges 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
2020-07-24 15:56         ` Logan Gunthorpe [this message]
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=59b68da4-cd3c-bf65-6654-02d4feaede27@deltatee.com \
    --to=logang@deltatee.com \
    --cc=alexdeucher@gmail.com \
    --cc=andrew.maier@eideticom.com \
    --cc=bhelgaas@google.com \
    --cc=christian.koenig@amd.com \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.