Re: [PATCH] PCI/ATS: Allow to enable ATS on VFs even if it is not enabled on PF
From: Leon Romanovsky <leon@kernel.org>
Date: 2023-02-16 07:26:27
Also in:
linux-iommu, linux-pci, lkml
From: Leon Romanovsky <leon@kernel.org>
Date: 2023-02-16 07:26:27
Also in:
linux-iommu, linux-pci, lkml
On Wed, Feb 15, 2023 at 02:57:26PM -0600, Bjorn Helgaas wrote:
[+cc Will, Robin, Joerg for arm-smmu-v3 page size question] On Sun, Feb 12, 2023 at 08:14:48PM +0200, Leon Romanovsky wrote:quoted
On Wed, Feb 08, 2023 at 10:43:21AM -0800, Ganapatrao Kulkarni wrote:quoted
As per PCIe specification(section 10.5), If a VF implements an ATS capability, its associated PF must implement an ATS capability. The ATS Capabilities in VFs and their associated PFs are permitted to be enabled independently. Also, it states that the Smallest Translation Unit (STU) for VFs must be hardwired to Zero and the associated PF's value applies to VFs STU. The current code allows to enable ATS on VFs only if it is already enabled on associated PF, which is not necessary as per the specification. It is only required to have valid STU programmed on PF to enable ATS on VFs. Adding code to write the first VFs STU to a PF's STU when PFs ATS is not enabled.Can you please add here quotes from the spec and its version? I don't see anything like this in my version of PCIe specification.See PCIe r6.0, sec 10.5.1.
Awesome, I have old versions. Thanks _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel