From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/xe: Drop bogus vma NULL check
Date: Mon, 18 Mar 2024 16:44:32 -0400 [thread overview]
Message-ID: <ZfinsMiI7ptWiiqj@intel.com> (raw)
In-Reply-To: <20240318093547.16326-1-nirmoy.das@intel.com>
On Mon, Mar 18, 2024 at 10:35:47AM +0100, Nirmoy Das wrote:
> The vma pointer can't be NULL here.
indeed, otherwise it would blow up a few lines above on xe_vma_vm.
and it would had fail in other places before this function
is called.
So,
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> index 7f54bc3e389d..8d3922d2206e 100644
> --- a/drivers/gpu/drm/xe/xe_pt.c
> +++ b/drivers/gpu/drm/xe/xe_pt.c
> @@ -618,7 +618,7 @@ xe_pt_stage_bind(struct xe_tile *tile, struct xe_vma *vma,
> struct xe_pt *pt = xe_vma_vm(vma)->pt_root[tile->id];
> int ret;
>
> - if (vma && (vma->gpuva.flags & XE_VMA_ATOMIC_PTE_BIT) &&
> + if ((vma->gpuva.flags & XE_VMA_ATOMIC_PTE_BIT) &&
> (is_devmem || !IS_DGFX(xe)))
> xe_walk.default_pte |= XE_USM_PPGTT_PTE_AE;
>
> --
> 2.42.0
>
prev parent reply other threads:[~2024-03-18 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 9:35 [PATCH] drm/xe: Drop bogus vma NULL check Nirmoy Das
2024-03-18 9:51 ` Matthew Auld
2024-03-18 16:39 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-18 16:39 ` ✓ CI.checkpatch: " Patchwork
2024-03-18 16:40 ` ✓ CI.KUnit: " Patchwork
2024-03-18 16:51 ` ✓ CI.Build: " Patchwork
2024-03-18 16:54 ` ✓ CI.Hooks: " Patchwork
2024-03-18 16:55 ` ✓ CI.checksparse: " Patchwork
2024-03-18 17:16 ` ✓ CI.BAT: " Patchwork
2024-03-18 20:44 ` Rodrigo Vivi [this message]
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=ZfinsMiI7ptWiiqj@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox