Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Brost,  Matthew" <matthew.brost@intel.com>
Subject: Re: [Intel-xe] [PATCH] drm/xe: Set max pte size when skipping rebinds
Date: Fri, 4 Aug 2023 00:23:22 +0000	[thread overview]
Message-ID: <d00a45fedeb9e4a87a6ef2e0c6927be6ad4e5c58.camel@intel.com> (raw)
In-Reply-To: <20230803032317.706386-1-matthew.brost@intel.com>

On Wed, 2023-08-02 at 20:23 -0700, Matthew Brost wrote:
> When a rebind is skipped, we must set the max pte size of the newly
> created vma to value of the old vma as we do not pte walk for the new
> vma. Without this future rebinds may be incorrectly skipped due to the
> wrong max pte size. Null binds are more likely to expose this bug as
> larger ptes are more frequently used compared to normal bindings.
> 
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> Testcase: dEQP-VK.sparse_resources.buffer.ssbo.sparse_residency.buffer_size_2_24
> Reported-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Fixes: a042bb4ca894 ("drm/xe: Avoid doing rebinds")
> Reference: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23045

This patch fixes the issues I was seeing.

Tested-by: Paulo Zanoni <paulo.r.zanoni@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_vm.c | 19 ++++++++++++++++++-
>  1 file changed, 18 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index cb28dbc2bdbb..936492915ecb 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -2406,6 +2406,20 @@ static u64 xe_vma_max_pte_size(struct xe_vma *vma)
>  	return SZ_4K;
>  }
>  
> +static u64 xe_vma_set_pte_size(struct xe_vma *vma, u64 size)
> +{
> +	switch (size) {
> +	case SZ_1G:
> +		vma->gpuva.flags |= XE_VMA_PTE_1G;
> +		break;
> +	case SZ_2M:
> +		vma->gpuva.flags |= XE_VMA_PTE_2M;
> +		break;
> +	}
> +
> +	return SZ_4K;
> +}
> +
>  /*
>   * Parse operations list and create any resources needed for the operations
>   * prior to fully committing to the operations. This setup can fail.
> @@ -2516,6 +2530,7 @@ static int vm_bind_ioctl_ops_parse(struct xe_vm *vm, struct xe_exec_queue *q,
>  						IS_ALIGNED(xe_vma_end(vma),
>  							   xe_vma_max_pte_size(old));
>  					if (op->remap.skip_prev) {
> +						xe_vma_set_pte_size(vma, xe_vma_max_pte_size(old));
>  						op->remap.range -=
>  							xe_vma_end(vma) -
>  							xe_vma_start(old);
> @@ -2550,10 +2565,12 @@ static int vm_bind_ioctl_ops_parse(struct xe_vm *vm, struct xe_exec_queue *q,
>  					op->remap.skip_next = !xe_vma_is_userptr(old) &&
>  						IS_ALIGNED(xe_vma_start(vma),
>  							   xe_vma_max_pte_size(old));
> -					if (op->remap.skip_next)
> +					if (op->remap.skip_next) {
> +						xe_vma_set_pte_size(vma, xe_vma_max_pte_size(old));
>  						op->remap.range -=
>  							xe_vma_end(old) -
>  							xe_vma_start(vma);
> +					}
>  				}
>  				break;
>  			}


  parent reply	other threads:[~2023-08-04  0:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  3:23 [Intel-xe] [PATCH] drm/xe: Set max pte size when skipping rebinds Matthew Brost
2023-08-03  3:27 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-08-03  3:28 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-03  3:29 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-03  3:33 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-03  3:33 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-03  3:34 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-08-03  4:08 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-08-04  0:23 ` Zanoni, Paulo R [this message]
2023-08-04 20:45 ` [Intel-xe] [PATCH] " Rodrigo Vivi

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=d00a45fedeb9e4a87a6ef2e0c6927be6ad4e5c58.camel@intel.com \
    --to=paulo.r.zanoni@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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