mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Nicolin Chen <nicolinc@nvidia.com>, Yi Liu <yi.l.liu@intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	iommu@lists.linux.dev, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/12] iommu: Make dev->fault_param static
Date: Fri, 11 Aug 2023 09:43:08 +0800	[thread overview]
Message-ID: <621683c0-ad01-22ff-dbf9-4edb27f42640@linux.intel.com> (raw)
In-Reply-To: <ZNUwgjJ+2GHf2MOW@ziepe.ca>

On 2023/8/11 2:46, Jason Gunthorpe wrote:
> On Thu, Aug 10, 2023 at 03:20:07PM -0300, Jason Gunthorpe wrote:
>> On Thu, Jul 27, 2023 at 01:48:31PM +0800, Lu Baolu wrote:
>>> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
>>> index 4ba3bb692993..3e4ff984aa85 100644
>>> --- a/drivers/iommu/iommu.c
>>> +++ b/drivers/iommu/iommu.c
>>> @@ -302,7 +302,15 @@ static int dev_iommu_get(struct device *dev)
>>>   		return -ENOMEM;
>>>   
>>>   	mutex_init(&param->lock);
>>> +	param->fault_param = kzalloc(sizeof(*param->fault_param), GFP_KERNEL);
>>> +	if (!param->fault_param) {
>>> +		kfree(param);
>>> +		return -ENOMEM;
>>> +	}
>>> +	mutex_init(&param->fault_param->lock);
>>> +	INIT_LIST_HEAD(&param->fault_param->faults);
>>>   	dev->iommu = param;
>> This allocation seems pointless?
>>
>> If we always allocate the fault param then just don't make it a
>> pointer in the first place.
>>
>> The appeal of allocation would be to save a few bytes in the common
>> case that the driver doesn't support faulting.
>>
>> Which means the driver needs to make some call to enable faulting for
>> a device. In this case I'd continue to lazy free on release like this
>> patch does.
> For instance allocate the fault_param in iopf_queue_add_device() which
> is the only thing that needs it.
> 
> Actually probably just merge struct iopf_device_param and
> iommu_fault_param ?
> 
> When you call iopf_queue_add_device() it enables page faulting mode,
> does 1 additional allocation for all additional required per-device
> memory and thats it.

Agreed.

I originally kept the iommu_fault_param structure because I thought it
could also be used to store temporary data for unrecoverable faults,
just like the iopf_device_param structure is used for iopf. However, I
am not sure whether we actually need any temporary data for
unrecoverable fault forwarding, which doesn't require any response.

So, it's better to do like you suggested. It's cleaner and simpler.

Best regards,
baolu


  reply	other threads:[~2023-08-11  1:43 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  5:48 [PATCH v2 00/12] iommu: Prepare to deliver page faults to user space Lu Baolu
2023-07-27  5:48 ` [PATCH v2 01/12] iommu: Move iommu fault data to linux/iommu.h Lu Baolu
2023-08-03  7:53   ` Tian, Kevin
2023-08-04  2:51     ` Baolu Lu
2023-08-09 16:58   ` Jason Gunthorpe
2023-07-27  5:48 ` [PATCH v2 02/12] iommu/arm-smmu-v3: Remove unrecoverable faults reporting Lu Baolu
2023-07-27  5:48 ` [PATCH v2 03/12] iommu: Remove unrecoverable fault data Lu Baolu
2023-08-03  7:54   ` Tian, Kevin
2023-08-04  2:58     ` Baolu Lu
2023-08-04  3:51       ` Tian, Kevin
2023-08-04  5:34         ` Baolu Lu
2023-08-08 18:39         ` Jason Gunthorpe
2023-08-09  0:01           ` Tian, Kevin
2023-08-09 14:05             ` Jason Gunthorpe
2023-08-09 16:59   ` Jason Gunthorpe
2023-08-10  2:27     ` Baolu Lu
2023-08-10 16:46       ` Jason Gunthorpe
2023-08-11  1:15         ` Baolu Lu
2023-08-11  4:17           ` Tian, Kevin
2023-07-27  5:48 ` [PATCH v2 04/12] iommu: Replace device fault handler with iommu_queue_iopf() Lu Baolu
2023-08-03  7:55   ` Tian, Kevin
2023-08-10 18:22   ` Jason Gunthorpe
2023-08-11  1:23     ` Baolu Lu
2023-08-10 18:33   ` Jason Gunthorpe
2023-08-11  1:25     ` Baolu Lu
2023-07-27  5:48 ` [PATCH v2 05/12] iommu: Change the return value of dev_iommu_get() Lu Baolu
2023-08-03  7:59   ` Tian, Kevin
2023-08-04  3:10     ` Baolu Lu
2023-08-04  3:55       ` Tian, Kevin
2023-08-04  5:33         ` Baolu Lu
2023-08-09 16:58   ` Jason Gunthorpe
2023-08-10  2:30     ` Baolu Lu
2023-07-27  5:48 ` [PATCH v2 06/12] iommu: Make dev->fault_param static Lu Baolu
2023-08-03  8:08   ` Tian, Kevin
2023-08-04  3:16     ` Baolu Lu
2023-08-04  3:56       ` Tian, Kevin
2023-08-04  5:34         ` Baolu Lu
2023-08-10 18:20   ` Jason Gunthorpe
2023-08-10 18:46     ` Jason Gunthorpe
2023-08-11  1:43       ` Baolu Lu [this message]
2023-07-27  5:48 ` [PATCH v2 07/12] iommu: Remove iommu_[un]register_device_fault_handler() Lu Baolu
2023-08-03  8:09   ` Tian, Kevin
2023-08-10 18:59   ` Jason Gunthorpe
2023-07-27  5:48 ` [PATCH v2 08/12] iommu: Prepare for separating SVA and IOPF Lu Baolu
2023-08-03  8:16   ` Tian, Kevin
2023-08-04  3:26     ` Baolu Lu
2023-08-08 18:43     ` Jason Gunthorpe
2023-08-09  0:02       ` Tian, Kevin
2023-08-09 10:40         ` Baolu Lu
2023-08-10  2:35           ` Tian, Kevin
2023-08-10 16:47             ` Jason Gunthorpe
2023-08-11  1:53               ` Baolu Lu
2023-08-11 13:27                 ` Jason Gunthorpe
2023-08-13 11:19                   ` Baolu Lu
2023-07-27  5:48 ` [PATCH v2 09/12] iommu: Move iopf_handler() to iommu-sva.c Lu Baolu
2023-08-03  8:21   ` Tian, Kevin
2023-08-04  3:28     ` Baolu Lu
2023-08-10 19:02   ` Jason Gunthorpe
2023-08-11  1:55     ` Baolu Lu
2023-07-27  5:48 ` [PATCH v2 10/12] iommu: Make iommu_queue_iopf() more generic Lu Baolu
2023-08-10 19:07   ` Jason Gunthorpe
2023-08-11  2:21     ` Baolu Lu
2023-08-11 13:29       ` Jason Gunthorpe
2023-08-12 23:18         ` Baolu Lu
2023-07-27  5:48 ` [PATCH v2 11/12] iommu: Separate SVA and IOPF in Makefile and Kconfig Lu Baolu
2023-08-10 19:09   ` Jason Gunthorpe
2023-07-27  5:48 ` [PATCH v2 12/12] iommu: Add helper to set iopf handler for domain Lu Baolu
2023-08-10 19:18   ` Jason Gunthorpe
2023-08-11  2:40     ` Baolu Lu
2023-08-11 17:14       ` Jason Gunthorpe

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=621683c0-ad01-22ff-dbf9-4edb27f42640@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@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

Powered by JetHome