From: Bjorn Helgaas <helgaas@kernel.org>
To: sathyanarayanan.kuppuswamy@linux.intel.com
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 0/5] Fix PF/VF dependency issues
Date: Fri, 19 Apr 2019 09:13:45 -0500 [thread overview]
Message-ID: <20190419141345.GD173520@google.com> (raw)
In-Reply-To: <cover.1551907663.git.sathyanarayanan.kuppuswamy@linux.intel.com>
On Wed, Mar 06, 2019 at 02:11:13PM -0800, sathyanarayanan.kuppuswamy@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
>
> Current implementation of ATS, PASID, PRI does not handle the PF/VF
> dependencies as defined in PCIe spec r4.0. Following patches
> addresses this issue.
Some of these patches probably fix issues, like making PASID work
correctly on VFs. But that needs to be made explicit in the commit
logs.
The current commit logs read more like "make XYZ follow the spec",
and that's not really what we need to know. The commit log needs to
tell us why we need the change, not just what the spec says.
For example, maybe VFs can't use PASID because Linux incorrectly tries
to use the PASID capability on the VF when it should be using the
capability on the PF. The commit log should say that explicitly and
also say what the current behavior is, e.g., does it cause IOMMU
faults, does it cause data corruption, does some DMA mapping interface
called by the VF driver fail when it shouldn't, etc?
Bjorn
> Kuppuswamy Sathyanarayanan (5):
> PCI/IOV: Add support to verify PF/VF spec compliance
> PCI/ATS: Fix PRI PF/VF dependency issues
> PCI/ATS: Fix PASID PF/VF dependency issues
> PCI/ATS: For PF/VF skip ATS initalization if spec check failed
> PCI/ATS: Fix ATS PF/VF dependency issues
>
> .../admin-guide/kernel-parameters.txt | 2 +
> drivers/pci/ats.c | 129 ++++-
> drivers/pci/iov.c | 468 ++++++++++++++++++
> drivers/pci/pci.c | 2 +
> drivers/pci/pci.h | 6 +
> include/linux/pci.h | 33 +-
> include/uapi/linux/pci_regs.h | 15 +-
> 7 files changed, 639 insertions(+), 16 deletions(-)
>
> --
> 2.20.1
>
prev parent reply other threads:[~2019-04-19 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 22:11 [PATCH v1 0/5] Fix PF/VF dependency issues sathyanarayanan.kuppuswamy
2019-04-19 14:13 ` Bjorn Helgaas [this message]
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=20190419141345.GD173520@google.com \
--to=helgaas@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).