All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Gabriele Paoloni <gabriele.paoloni@huawei.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linuxarm <linuxarm@huawei.com>,
	"liudongdong (C)" <liudongdong3@huawei.com>,
	zhangjukuo <zhangjukuo@huawei.com>,
	"Wangzhou (B)" <wangzhou1@hisilicon.com>
Subject: Re: Question: PCIe DPC not allowing for link retraining and bus re-scan
Date: Tue, 31 Jan 2017 10:53:36 -0500	[thread overview]
Message-ID: <20170131155336.GA24601@localhost.localdomain> (raw)
In-Reply-To: <EE11001F9E5DDD47B7634E2F8A612F2E1F9F9345@lhreml507-mbx>

On Tue, Jan 31, 2017 at 09:35:58AM +0000, Gabriele Paoloni wrote:
> I don't mind writing the patches but currently I also do not have a
> platform to test on.
> 
> Do you know if there is any Intel Server/Desktop with full support of
> DPC on the RP including "Software Triggering of DPC" (maybe some
> machines that are out on the market but you do not have there with you)?

Currently available Intel offerings do not have eDPC capable root ports.
I use switches from Microsemi and PLX with these capabilities on their
downstream ports so I'm limited to non-root port testing at the moment.

> As an alternative I am thinking that maybe I can find a switch with
> full DPC support including "Software Triggering of DPC". In this case
> we test anything except the RP Busy bit...
> 
> The idea is to have a sort of DPC SW Injection module to test DPC.

I think you can s/w inject from userspace with setpci:

  # setpci -s <B:D.f> ECAP_DPC+6.w=40:40

The port has to have a software trigger capability. I can get such a
switch, but don't have one immediately available.

Anyway, I'll write a couple patches and post them when I can get
validation. Thank you for pointing out the current gaps.

  reply	other threads:[~2017-01-31 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 11:56 Question: PCIe DPC not allowing for link retraining and bus re-scan Gabriele Paoloni
2017-01-30 16:14 ` Keith Busch
2017-01-31  9:35   ` Gabriele Paoloni
2017-01-31 15:53     ` Keith Busch [this message]
2017-01-31 16:59       ` Gabriele Paoloni
2017-02-02 23:22         ` Keith Busch
2017-02-03  8:26           ` Gabriele Paoloni
2017-02-03 10:35 ` Gabriele Paoloni
2017-02-03 20:52   ` Keith Busch
2017-02-04  6:29     ` Gabriele Paoloni

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=20170131155336.GA24601@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=gabriele.paoloni@huawei.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=zhangjukuo@huawei.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.