linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
	rdunlap@infradead.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/P2PDMA: start with a whitelist for root complexes
Date: Thu, 18 Apr 2019 12:24:26 -0500	[thread overview]
Message-ID: <20190418172426.GB213349@google.com> (raw)
In-Reply-To: <22b686f0-572b-d083-915f-5c46c89dfbc3@deltatee.com>

On Thu, Apr 18, 2019 at 10:58:55AM -0600, Logan Gunthorpe wrote:
> On 2019-04-18 10:33 a.m., Bjorn Helgaas wrote:
> > On Thu, Apr 18, 2019 at 01:58:59PM +0200, Christian König wrote:
> > > A lot of root complexes can still do P2P even when PCI devices
> > > don't share a common upstream bridge.
> > > 
> > > Start adding a whitelist and allow P2P if both participants are
> > > attached to known good root complex.
> > 
> > Is there a plan for addressing this in a generic way that doesn't
> > require an OS modification for every new "known good root complex",
> > e.g., some PCIe or ACPI spec update that allows the OS to discover
> > this?
> 
> I'm aware of work going on in the PCI SIG to address this [1].
> 
> But I expect it's going to be a long time before actual hardware advertises
> this capability to indicate support. So in the interim we either need to not
> use p2pdma on root complexes or create a white list. I'm in favour of the
> white list approach.

I agree we need a whitelist; I just want to make sure we also make
progress on some way to limit the amount of time we need to update it.

> [1] https://lore.kernel.org/linux-pci/20181210115653.0000615a@huawei.com/

  reply	other threads:[~2019-04-18 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 11:58 [PATCH] PCI/P2PDMA: start with a whitelist for root complexes Christian König
2019-04-18 16:33 ` Bjorn Helgaas
2019-04-18 16:58   ` Logan Gunthorpe
2019-04-18 17:24     ` Bjorn Helgaas [this message]
2019-04-19 14:24       ` Koenig, Christian
2019-04-19 18:47         ` Bjorn Helgaas
2019-04-18 16:45 ` Logan Gunthorpe
2019-04-19 19:19 ` Bjorn Helgaas
2019-04-24  8:51   ` Christian König
2019-05-01 21:58 ` Bjorn Helgaas

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=20190418172426.GB213349@google.com \
    --to=helgaas@kernel.org \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=rdunlap@infradead.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).