All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v3 4/7] drm/xe: Move vm bind bo validation to a helper function
Date: Tue, 16 Apr 2024 15:32:04 +0200	[thread overview]
Message-ID: <2f2e0bfc-d1cd-4d9e-973c-4cdaacfa89f1@linux.intel.com> (raw)
In-Reply-To: <Zh3Mfac/UZ+6K8g3@DUT025-TGLU>

Hi Matt,

On 4/16/2024 2:55 AM, Matthew Brost wrote:
> On Mon, Apr 15, 2024 at 04:52:11PM +0200, Nirmoy Das wrote:
>> Move vm bind bo validation to a helper function to make the
>> xe_vm_bind_ioctl() more readable.
>>
> Change logs are helpful for reviewers but not going to hold up this
> patch.
Cover letter contains all the changes. I can also copy within the 
patches from the next revision.
> With that:
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>

Thanks,

Nirmoy

>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_vm.c | 77 +++++++++++++++++++++-----------------
>>   1 file changed, 43 insertions(+), 34 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
>> index b1dcaa35b6cc..8380f1d23074 100644
>> --- a/drivers/gpu/drm/xe/xe_vm.c
>> +++ b/drivers/gpu/drm/xe/xe_vm.c
>> @@ -2872,6 +2872,46 @@ static int vm_bind_ioctl_signal_fences(struct xe_vm *vm,
>>   	return err;
>>   }
>>   
>> +static int xe_vm_bind_ioctl_validate_bo(struct xe_device *xe, struct xe_bo *bo,
>> +					u64 addr, u64 range, u64 obj_offset,
>> +					u16 pat_index)
>> +{
>> +	u16 coh_mode;
>> +
>> +	if (XE_IOCTL_DBG(xe, range > bo->size) ||
>> +	    XE_IOCTL_DBG(xe, obj_offset >
>> +			 bo->size - range)) {
>> +		return -EINVAL;
>> +	}
>> +
>> +	if (bo->flags & XE_BO_FLAG_INTERNAL_64K) {
>> +		if (XE_IOCTL_DBG(xe, obj_offset &
>> +				 XE_64K_PAGE_MASK) ||
>> +		    XE_IOCTL_DBG(xe, addr & XE_64K_PAGE_MASK) ||
>> +		    XE_IOCTL_DBG(xe, range & XE_64K_PAGE_MASK)) {
>> +			return  -EINVAL;
>> +		}
>> +	}
>> +
>> +	coh_mode = xe_pat_index_get_coh_mode(xe, pat_index);
>> +	if (bo->cpu_caching) {
>> +		if (XE_IOCTL_DBG(xe, coh_mode == XE_COH_NONE &&
>> +				 bo->cpu_caching == DRM_XE_GEM_CPU_CACHING_WB)) {
>> +			return  -EINVAL;
>> +		}
>> +	} else if (XE_IOCTL_DBG(xe, coh_mode == XE_COH_NONE)) {
>> +		/*
>> +		 * Imported dma-buf from a different device should
>> +		 * require 1way or 2way coherency since we don't know
>> +		 * how it was mapped on the CPU. Just assume is it
>> +		 * potentially cached on CPU side.
>> +		 */
>> +		return  -EINVAL;
>> +	}
>> +
>> +	return 0;
>> +}
>> +
>>   int xe_vm_bind_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
>>   {
>>   	struct xe_device *xe = to_xe_device(dev);
>> @@ -2955,7 +2995,6 @@ int xe_vm_bind_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
>>   		u32 obj = bind_ops[i].obj;
>>   		u64 obj_offset = bind_ops[i].obj_offset;
>>   		u16 pat_index = bind_ops[i].pat_index;
>> -		u16 coh_mode;
>>   
>>   		if (!obj)
>>   			continue;
>> @@ -2967,40 +3006,10 @@ int xe_vm_bind_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
>>   		}
>>   		bos[i] = gem_to_xe_bo(gem_obj);
>>   
>> -		if (XE_IOCTL_DBG(xe, range > bos[i]->size) ||
>> -		    XE_IOCTL_DBG(xe, obj_offset >
>> -				 bos[i]->size - range)) {
>> -			err = -EINVAL;
>> -			goto put_obj;
>> -		}
>> -
>> -		if (bos[i]->flags & XE_BO_FLAG_INTERNAL_64K) {
>> -			if (XE_IOCTL_DBG(xe, obj_offset &
>> -					 XE_64K_PAGE_MASK) ||
>> -			    XE_IOCTL_DBG(xe, addr & XE_64K_PAGE_MASK) ||
>> -			    XE_IOCTL_DBG(xe, range & XE_64K_PAGE_MASK)) {
>> -				err = -EINVAL;
>> -				goto put_obj;
>> -			}
>> -		}
>> -
>> -		coh_mode = xe_pat_index_get_coh_mode(xe, pat_index);
>> -		if (bos[i]->cpu_caching) {
>> -			if (XE_IOCTL_DBG(xe, coh_mode == XE_COH_NONE &&
>> -					 bos[i]->cpu_caching == DRM_XE_GEM_CPU_CACHING_WB)) {
>> -				err = -EINVAL;
>> -				goto put_obj;
>> -			}
>> -		} else if (XE_IOCTL_DBG(xe, coh_mode == XE_COH_NONE)) {
>> -			/*
>> -			 * Imported dma-buf from a different device should
>> -			 * require 1way or 2way coherency since we don't know
>> -			 * how it was mapped on the CPU. Just assume is it
>> -			 * potentially cached on CPU side.
>> -			 */
>> -			err = -EINVAL;
>> +		err = xe_vm_bind_ioctl_validate_bo(xe, bos[i], addr, range,
>> +						   obj_offset, pat_index);
>> +		if (err)
>>   			goto put_obj;
>> -		}
>>   	}
>>   
>>   	if (args->num_syncs) {
>> -- 
>> 2.42.0
>>

  reply	other threads:[~2024-04-16 13:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 14:52 [PATCH v3 0/7] Enable device atomics with a VM bind flag Nirmoy Das
2024-04-15 14:52 ` [PATCH v3 1/7] drm/xe: Introduce has_atomic_enable_pte_bit device info Nirmoy Das
2024-04-19 16:06   ` Zeng, Oak
2024-04-15 14:52 ` [PATCH v3 2/7] drm/xe: Consolidate setting PTE_AE into one place Nirmoy Das
2024-04-16 14:33   ` Nirmoy Das
2024-04-19 18:35   ` Zeng, Oak
2024-04-22  8:18     ` Nirmoy Das
2024-04-15 14:52 ` [PATCH v3 3/7] drm/xe: Add function to check if BO has single placement Nirmoy Das
2024-04-15 14:52 ` [PATCH v3 4/7] drm/xe: Move vm bind bo validation to a helper function Nirmoy Das
2024-04-16  0:55   ` Matthew Brost
2024-04-16 13:32     ` Nirmoy Das [this message]
2024-04-19 20:14   ` Zeng, Oak
2024-04-15 14:52 ` [PATCH v3 5/7] drm/xe: Introduce has_device_atomics_on_smem device info Nirmoy Das
2024-04-19 20:24   ` Zeng, Oak
2024-04-15 14:52 ` [PATCH v3 6/7] drm/xe/uapi: Introduce VMA bind flag for device atomics Nirmoy Das
2024-04-19  7:16   ` Lionel Landwerlin
2024-04-22  8:39     ` Nirmoy Das
2024-04-19 21:04   ` Zeng, Oak
2024-04-22 10:12     ` Nirmoy Das
2024-04-22 21:39       ` Zeng, Oak
2024-04-23 12:33         ` Nirmoy Das
2024-04-15 14:52 ` [PATCH v3 7/7] drm/xe/uapi: Add a query flag for has_device_atomics_on_smem Nirmoy Das
2024-04-19  7:08   ` Lionel Landwerlin
2024-04-22  8:53     ` Nirmoy Das
2024-04-19 21:06   ` Zeng, Oak
2024-04-15 21:19 ` ✓ CI.Patch_applied: success for Enable device atomics with a VM bind flag (rev3) Patchwork
2024-04-15 21:19 ` ✓ CI.checkpatch: " Patchwork
2024-04-15 21:21 ` ✓ CI.KUnit: " Patchwork
2024-04-15 21:37 ` ✓ CI.Build: " Patchwork
2024-04-15 21:40 ` ✓ CI.Hooks: " Patchwork
2024-04-15 21:41 ` ✓ CI.checksparse: " Patchwork
2024-04-15 22:22 ` ✗ CI.BAT: failure " Patchwork
2024-04-16 13:46 ` ✓ CI.FULL: success " Patchwork
2024-04-19  7:17 ` [PATCH v3 0/7] Enable device atomics with a VM bind flag Lionel Landwerlin
2024-04-22 10:13   ` Nirmoy Das
2024-04-22 14:50 ` Souza, Jose

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=2f2e0bfc-d1cd-4d9e-973c-4cdaacfa89f1@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=nirmoy.das@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.