linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Yong, Jonathan" <jonathan.yong@intel.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [RFC v4] PCI: PTM Driver
Date: Tue, 3 May 2016 09:55:07 -0500	[thread overview]
Message-ID: <20160503145506.GA30040@localhost> (raw)
In-Reply-To: <57286935.3090409@intel.com>

On Tue, May 03, 2016 at 05:02:45PM +0800, Yong, Jonathan wrote:
> On 04/29/2016 22:17, Bjorn Helgaas wrote:
> >On Tue, Apr 19, 2016 at 06:29:17AM +0000, Yong, Jonathan wrote:
> >>Hello LKML,
> >>
> >>This is a preliminary implementation of the PTM[1] support driver. This driver
> >>has only been tested against a virtual PCI bus since there are no known
> >>endpoints utilizing it yet.
> >
> >What sort of testing is this, exactly?  Is this using a software model
> >of devices that support PTM?
> >
> 
> We wrote another driver to fake the PCI config space with
> pci_scan_bus, with fake switches and fake devices. Convenient since
> the driver only deals with the config space.
> 
> >When will hardware that supports PTM be available to you for testing?
> >When will it be available on the market?
> >
> 
> I don't have any dates for when consumer endpoints will hit the
> market. PTM aware FPGA device models might come around Q3/Q4 this
> year, with exercisers around 2017.
> 
> >I'm trying to figure out whether there's any benefit to merging
> >something before it is useful to anybody.
> >
> 
> True it won't be useful to anybody until such a device is available.
> What is the general policy for future hardware standards?

I don't know if there is a real consensus about that.  In this case,
the feature is relatively simple (at least compared to, say ASPM), and
it's defined by a spec that's already been published, so I don't think
there's really much reason to wait.

I think the most expedient thing is to get it merged now so it'll be
easier to test and deploy it.

Bjorn

  reply	other threads:[~2016-05-03 14:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  6:29 [RFC v4] PCI: PTM Driver Yong, Jonathan
2016-04-19  6:29 ` [PATCH] PCI: PTM preliminary implementation Yong, Jonathan
2016-04-29 16:20   ` Bjorn Helgaas
2016-04-30 12:19     ` Bjorn Helgaas
2016-05-10  3:52     ` Yong, Jonathan
2016-05-08  2:38   ` Bjorn Helgaas
2016-05-09  3:11     ` Yong, Jonathan
2016-05-09 13:35       ` Bjorn Helgaas
2016-04-27 23:18 ` [RFC v4] PCI: PTM Driver Yong, Jonathan
2016-04-29 14:17 ` Bjorn Helgaas
2016-05-03  9:02   ` Yong, Jonathan
2016-05-03 14:55     ` Bjorn Helgaas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-19  6:24 Yong, Jonathan

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=20160503145506.GA30040@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=jonathan.yong@intel.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).