linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sathyanarayanan Kuppuswamy  <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
	joro@8bytes.org, bhelgaas@google.com, robin.murphy@arm.com,
	will@kernel.org
Cc: jean-philippe@linaro.org, darren@os.amperecomputing.com,
	scott@os.amperecomputing.com
Subject: Re: [PATCH v2 0/2] Add support to enable ATS on VFs independently
Date: Wed, 1 Mar 2023 20:24:10 -0800	[thread overview]
Message-ID: <917b1d52-54c2-ea8b-5382-dbd8ce71a76c@linux.intel.com> (raw)
In-Reply-To: <20230228042137.1941024-1-gankulkarni@os.amperecomputing.com>



On 2/27/23 8:21 PM, Ganapatrao Kulkarni wrote:
> As discussed in [1], adding a helper function to configure the STU of an
> ATS capability. Function pci_ats_stu_configure() can be called to program
> the STU while enumerating the PF, to support scenarios like PF is not
> enabled with ATS, whereas VFs can enable it.
> 
> In SMMU-V3 driver, calling pci_ats_stu_configure() to confgiure the STU
> while enumerating a PF in passthrough mode.

It looks like you are fixing this issue only for your platform. Is there any
way to generically program PF STU? May be from pci_ats_init()?

-- 
Sathyanarayanan Kuppuswamy
Linux Kernel Developer

      parent reply	other threads:[~2023-03-02  4:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  4:21 [PATCH v2 0/2] Add support to enable ATS on VFs independently Ganapatrao Kulkarni
2023-02-28  4:21 ` [PATCH v2 1/2] PCI/ATS: Add a helper function to configure ATS STU of a PF Ganapatrao Kulkarni
2023-02-28 16:30   ` Sathyanarayanan Kuppuswamy
2023-03-08  8:54   ` Ganapatrao Kulkarni
2023-03-13 21:12   ` Bjorn Helgaas
2023-03-13 22:30     ` Sathyanarayanan Kuppuswamy
2023-03-13 22:42       ` Bjorn Helgaas
2023-03-14 10:08       ` Ganapatrao Kulkarni
2023-03-14 12:52         ` Sathyanarayanan Kuppuswamy
2023-03-14 14:36           ` Ganapatrao Kulkarni
2023-03-14 16:02             ` Bjorn Helgaas
2023-03-14 16:50               ` Sathyanarayanan Kuppuswamy
2023-03-14 17:10                 ` Bjorn Helgaas
2023-03-14 18:01                   ` Ganapatrao Kulkarni
2023-03-14 18:12                   ` Sathyanarayanan Kuppuswamy
2023-03-14 21:17                     ` Bjorn Helgaas
2023-03-15  4:22                       ` Sathyanarayanan Kuppuswamy
2023-03-15 14:30                     ` Ganapatrao Kulkarni
2023-02-28  4:21 ` [PATCH v2 2/2] iommu/arm-smmu-v3: Configure STU of a PF if ATS is not enabled Ganapatrao Kulkarni
2023-03-13 14:19   ` Ganapatrao Kulkarni
2023-03-02  4:24 ` Sathyanarayanan Kuppuswamy [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=917b1d52-54c2-ea8b-5382-dbd8ce71a76c@linux.intel.com \
    --to=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=darren@os.amperecomputing.com \
    --cc=gankulkarni@os.amperecomputing.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=scott@os.amperecomputing.com \
    --cc=will@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).