iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Ashok Raj <ashok.raj@intel.com>,
	iommu@lists.linux.dev, Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	Vinod Koul <vkoul@kernel.org>,
	Ethan Zhao <haifeng.zhao@linux.intel.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Will Deacon <will@kernel.org>,
	Jacob jun Pan <jacob.jun.pan@intel.com>
Subject: Re: [PATCH v9 10/11] iommu: Per-domain I/O page fault handling
Date: Tue, 28 Jun 2022 15:20:43 +0100	[thread overview]
Message-ID: <YrsOO9E+j+CMgKMA@myrica> (raw)
In-Reply-To: <935ca9e3-28c9-99af-5609-41bb1500b2b3@linux.intel.com>

On Tue, Jun 28, 2022 at 07:53:39PM +0800, Baolu Lu wrote:
> > > > Once the iopf_handle_single() is removed, the name of
> > > > iopf_handle_group() looks a little weired
> > > > 
> > > > and confused, does this group mean the iommu group (domain) ?
> > > > while I take some minutes to
> > > 
> > > No. This is not the iommu group. It's page request group defined by the
> > > PCI SIG spec. Multiple page requests could be put in a group with a
> > > same group id. All page requests in a group could be responded to device
> > > in one shot.
> > 
> > Thanks your explaination, understand the concept of PCIe PRG.  I meant
> > 
> > do we still have the necessity to mention the "group" here in the name
> > 
> > iopf_handle_group(),  which one is better ? iopf_handle_prg() or
> > 
> > iopf_handler(),  perhaps none of them ? :)
> 
> Oh! Sorry for the misunderstanding.
> 
> I have no strong feeling to change this naming. :-) All the names
> express what the helper does. Jean is the author of this framework. If
> he has the same idea as you, I don't mind renaming it in this patch.

I'm not attached to the name, and I see how it could be confusing. Given
that io-pgfault is not only for PCIe, 'prg' is not the best here either.
iopf_handle_faults(), or just iopf_handler(), seem more suitable.

Thanks,
Jean
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: Ethan Zhao <haifeng.zhao@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>, Jason Gunthorpe <jgg@nvidia.com>,
	Christoph Hellwig <hch@infradead.org>,
	Kevin Tian <kevin.tian@intel.com>,
	Ashok Raj <ashok.raj@intel.com>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	Dave Jiang <dave.jiang@intel.com>, Vinod Koul <vkoul@kernel.org>,
	Eric Auger <eric.auger@redhat.com>, Liu Yi L <yi.l.liu@intel.com>,
	Jacob jun Pan <jacob.jun.pan@intel.com>,
	iommu@lists.linux-foundation.org, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 10/11] iommu: Per-domain I/O page fault handling
Date: Tue, 28 Jun 2022 15:20:43 +0100	[thread overview]
Message-ID: <YrsOO9E+j+CMgKMA@myrica> (raw)
Message-ID: <20220628142043.ivGVse1-0jWi3BZzPejc7eimed91afNrNh1lldFdoAg@z> (raw)
In-Reply-To: <935ca9e3-28c9-99af-5609-41bb1500b2b3@linux.intel.com>

On Tue, Jun 28, 2022 at 07:53:39PM +0800, Baolu Lu wrote:
> > > > Once the iopf_handle_single() is removed, the name of
> > > > iopf_handle_group() looks a little weired
> > > > 
> > > > and confused, does this group mean the iommu group (domain) ?
> > > > while I take some minutes to
> > > 
> > > No. This is not the iommu group. It's page request group defined by the
> > > PCI SIG spec. Multiple page requests could be put in a group with a
> > > same group id. All page requests in a group could be responded to device
> > > in one shot.
> > 
> > Thanks your explaination, understand the concept of PCIe PRG.  I meant
> > 
> > do we still have the necessity to mention the "group" here in the name
> > 
> > iopf_handle_group(),  which one is better ? iopf_handle_prg() or
> > 
> > iopf_handler(),  perhaps none of them ? :)
> 
> Oh! Sorry for the misunderstanding.
> 
> I have no strong feeling to change this naming. :-) All the names
> express what the helper does. Jean is the author of this framework. If
> he has the same idea as you, I don't mind renaming it in this patch.

I'm not attached to the name, and I see how it could be confusing. Given
that io-pgfault is not only for PCIe, 'prg' is not the best here either.
iopf_handle_faults(), or just iopf_handler(), seem more suitable.

Thanks,
Jean

  parent reply	other threads:[~2022-06-28 14:21 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 14:43 [PATCH v9 00/11] iommu: SVA and IOPF refactoring Lu Baolu
2022-06-21 14:43 ` Lu Baolu
2022-06-21 14:43 ` [PATCH v9 01/11] iommu: Add max_pasids field in struct iommu_device Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-27  8:05   ` Tian, Kevin
2022-06-27  8:05     ` Tian, Kevin
2022-06-21 14:43 ` [PATCH v9 02/11] iommu: Add max_pasids field in struct dev_iommu Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-27  8:06   ` Tian, Kevin
2022-06-27  8:06     ` Tian, Kevin
2022-06-21 14:43 ` [PATCH v9 03/11] iommu: Remove SVM_FLAG_SUPERVISOR_MODE support Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-21 14:43 ` [PATCH v9 04/11] iommu: Add sva iommu_domain support Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-27  8:29   ` Tian, Kevin
2022-06-27  8:29     ` Tian, Kevin
2022-06-28  5:41     ` Baolu Lu
2022-06-28  5:41       ` Baolu Lu
2022-06-28  8:50       ` Tian, Kevin
2022-06-28  8:50         ` Tian, Kevin
2022-06-28 11:33         ` Baolu Lu
2022-06-28 11:33           ` Baolu Lu
2022-06-29  1:54           ` Tian, Kevin
2022-06-29  1:54             ` Tian, Kevin
2022-06-29  4:44             ` Baolu Lu
2022-06-29  4:44               ` Baolu Lu
2022-06-28 11:41         ` Baolu Lu
2022-06-28 11:41           ` Baolu Lu
2022-06-21 14:43 ` [PATCH v9 05/11] iommu/vt-d: Add SVA domain support Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-27  8:32   ` Tian, Kevin
2022-06-27  8:32     ` Tian, Kevin
2022-06-21 14:43 ` [PATCH v9 06/11] arm-smmu-v3/sva: " Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-27 11:50   ` Zhangfei Gao
2022-06-27 11:50     ` Zhangfei Gao
2022-06-28  5:46     ` Baolu Lu
2022-06-28  5:46       ` Baolu Lu
2022-06-28  6:13     ` Baolu Lu
2022-06-28  6:13       ` Baolu Lu
2022-06-28  6:17       ` Zhu, Tony
2022-06-28  6:17         ` Zhu, Tony
2022-06-21 14:43 ` [PATCH v9 07/11] iommu/sva: Refactoring iommu_sva_bind/unbind_device() Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-27 10:14   ` Tian, Kevin
2022-06-27 10:14     ` Tian, Kevin
2022-06-28  5:53     ` Baolu Lu
2022-06-28  5:53       ` Baolu Lu
2022-06-28  8:52       ` Tian, Kevin
2022-06-28  8:52         ` Tian, Kevin
2022-06-21 14:43 ` [PATCH v9 08/11] iommu: Remove SVA related callbacks from iommu ops Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-21 14:43 ` [PATCH v9 09/11] iommu: Prepare IOMMU domain for IOPF Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-28  8:29   ` Tian, Kevin
2022-06-28  8:29     ` Tian, Kevin
2022-06-28 10:49     ` Baolu Lu
2022-06-28 10:49       ` Baolu Lu
2022-06-21 14:43 ` [PATCH v9 10/11] iommu: Per-domain I/O page fault handling Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-27 13:03   ` Ethan Zhao
2022-06-27 13:03     ` Ethan Zhao
2022-06-28  6:28     ` Baolu Lu
2022-06-28  6:28       ` Baolu Lu
2022-06-28  9:10       ` Ethan Zhao
2022-06-28  9:10         ` Ethan Zhao
2022-06-28 11:53         ` Baolu Lu
2022-06-28 11:53           ` Baolu Lu
2022-06-28 14:20           ` Jean-Philippe Brucker [this message]
2022-06-28 14:20             ` Jean-Philippe Brucker
2022-06-29  0:24             ` Baolu Lu
2022-06-29  0:24               ` Baolu Lu
2022-06-29  6:15             ` Ethan Zhao
2022-06-29  6:15               ` Ethan Zhao
2022-06-28  8:39   ` Tian, Kevin
2022-06-28  8:39     ` Tian, Kevin
2022-06-28  9:44     ` Jean-Philippe Brucker
2022-06-28  9:44       ` Jean-Philippe Brucker
2022-06-28 10:02       ` Tian, Kevin
2022-06-28 10:02         ` Tian, Kevin
2022-06-28 12:18         ` Baolu Lu
2022-06-28 12:18           ` Baolu Lu
2022-06-28 11:02     ` Baolu Lu
2022-06-28 11:02       ` Baolu Lu
2022-06-21 14:43 ` [PATCH v9 11/11] iommu: Rename iommu-sva-lib.{c,h} Lu Baolu
2022-06-21 14:43   ` Lu Baolu
2022-06-28  8:40   ` Tian, Kevin
2022-06-28  8:40     ` Tian, Kevin
2022-06-26  1:15 ` [PATCH v9 00/11] iommu: SVA and IOPF refactoring Baolu Lu
2022-06-26  1:15   ` Baolu Lu

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=YrsOO9E+j+CMgKMA@myrica \
    --to=jean-philippe@linaro.org \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=haifeng.zhao@linux.intel.com \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.jun.pan@intel.com \
    --cc=jean-philippe@linaro.com \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=vkoul@kernel.org \
    --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).