Linux IOMMU Development
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: iommu@lists.linux.dev, joro@8bytes.org,
	suravee.suthikulpanit@amd.com, wei.huang2@amd.com,
	jsnitsel@redhat.com
Subject: Re: [PATCH v6 09/17] iommu: Introduce iommu_group_mutex_assert()
Date: Mon, 5 Feb 2024 15:52:21 +0530	[thread overview]
Message-ID: <12340fba-e9c2-abff-6349-a4aaf64737e5@amd.com> (raw)
In-Reply-To: <20240201172611.GJ50608@ziepe.ca>



On 2/1/2024 10:56 PM, Jason Gunthorpe wrote:
> On Thu, Jan 25, 2024 at 12:11:27PM +0000, Vasant Hegde wrote:
>> Add function to check iommu group mutex lock. So that device drivers can
>> rely on group mutex lock instead of adding another driver level lock
>> before modifying driver specific device data structure.
>>
>> Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
>> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
>> ---
>>  drivers/iommu/iommu.c | 19 +++++++++++++++++++
>>  include/linux/iommu.h |  8 ++++++++
>>  2 files changed, 27 insertions(+)
> 
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> 
>> +#if IS_ENABLED(CONFIG_LOCKDEP) && IS_ENABLED(CONFIG_IOMMU_API)
>> +extern void iommu_group_mutex_assert(struct device *dev);
> 
> The extern is not necessary, there is a general shift away from using
> it, not a reason for a v7, but FYI

Right. Fixed in v7.

-Vasant

  reply	other threads:[~2024-02-05 10:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 12:11 [PATCH v6 00/17] iommu/amd: SVA Support (part 3) - refactor support for GCR3 table Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 01/17] iommu/amd: Pass struct iommu_dev_data to set_dte_entry() Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 02/17] iommu/amd: Enable Guest Translation before registering devices Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 03/17] iommu/amd: Introduce get_amd_iommu_from_dev() Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 04/17] iommu/amd: Introduce struct protection_domain.pd_mode Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 05/17] iommu/amd: Introduce per-device GCR3 table Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 06/17] iommu/amd: Use protection_domain.flags to check page table mode Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 07/17] iommu/amd: Add support for device based TLB invalidation Vasant Hegde
2024-02-01 17:38   ` Jason Gunthorpe
2024-01-25 12:11 ` [PATCH v6 08/17] iommu/amd: Rearrange GCR3 table setup code Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 09/17] iommu: Introduce iommu_group_mutex_assert() Vasant Hegde
2024-02-01 17:26   ` Jason Gunthorpe
2024-02-05 10:22     ` Vasant Hegde [this message]
2024-01-25 12:11 ` [PATCH v6 10/17] iommu/amd: Refactor helper function for setting / clearing GCR3 Vasant Hegde
2024-02-01 17:35   ` Jason Gunthorpe
2024-02-05 10:22     ` Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 11/17] iommu/amd: Refactor attaching / detaching device functions Vasant Hegde
2024-02-01 17:43   ` Jason Gunthorpe
2024-01-25 12:11 ` [PATCH v6 12/17] iommu/amd: Refactor protection_domain helper functions Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 13/17] iommu/amd: Refactor GCR3 table " Vasant Hegde
2024-02-01 18:02   ` Jason Gunthorpe
2024-01-25 12:11 ` [PATCH v6 14/17] iommu/amd: Remove unused flush pasid functions Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 15/17] iommu/amd: Rearrange device flush code Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 16/17] iommu/amd: Remove unused GCR3 table parameters from struct protection_domain Vasant Hegde
2024-01-25 12:11 ` [PATCH v6 17/17] iommu/amd: Introduce per-device domain ID to workaround potential TLB aliasing issue Vasant Hegde
2024-02-01 18:51   ` Jason Gunthorpe
2024-02-05 10:18     ` Vasant Hegde

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=12340fba-e9c2-abff-6349-a4aaf64737e5@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=wei.huang2@amd.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