From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 3/3] drm/xe: fix range printing for debug messages
Date: Wed, 4 Oct 2023 09:18:13 -0400 [thread overview]
Message-ID: <ZR1mFbn3eVrYVoz/@intel.com> (raw)
In-Reply-To: <ZRexCZczizPkWdNm@nvishwa1-DESK>
On Fri, Sep 29, 2023 at 10:24:25PM -0700, Niranjana Vishwanathapura wrote:
> On Fri, Sep 29, 2023 at 10:31:04AM -0700, Paulo Zanoni wrote:
> > We're already using the half-open interval notation "[A, B)", that "-
> > 1" there makes it wrong. Also, getting rid of the "-1" makes it much
> > easier to grep for the logs when you're looking for an address that's
> > the end of a vma and the start of another.
> >
> > Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_pt.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> > index 4d4c6a4c305e..70a8bd3558c2 100644
> > --- a/drivers/gpu/drm/xe/xe_pt.c
> > +++ b/drivers/gpu/drm/xe/xe_pt.c
> > @@ -1265,7 +1265,7 @@ __xe_pt_bind_vma(struct xe_tile *tile, struct xe_vma *vma, struct xe_exec_queue
> >
> > vm_dbg(&xe_vma_vm(vma)->xe->drm,
> > "Preparing bind, with range [%llx...%llx) engine %p.\n",
> > - xe_vma_start(vma), xe_vma_end(vma) - 1, q);
> > + xe_vma_start(vma), xe_vma_end(vma), q);
> >
> > err = xe_pt_prepare_bind(tile, vma, entries, &num_entries, rebind);
> > if (err)
> > @@ -1618,7 +1618,7 @@ __xe_pt_unbind_vma(struct xe_tile *tile, struct xe_vma *vma, struct xe_exec_queu
> >
> > vm_dbg(&xe_vma_vm(vma)->xe->drm,
> > "Preparing unbind, with range [%llx...%llx) engine %p.\n",
> > - xe_vma_start(vma), xe_vma_end(vma) - 1, q);
> > + xe_vma_start(vma), xe_vma_end(vma), q);
>
> LGTM given it was intended to be half-open interval here and in
> xe_vm_dbg_print_entries().
>
> Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
pushed to drm-xe-next. thanks for the patches and reviews.
>
> >
> > num_entries = xe_pt_stage_unbind(tile, vma, entries);
> > xe_tile_assert(tile, num_entries <= ARRAY_SIZE(entries));
> > --
> > 2.39.2
> >
next prev parent reply other threads:[~2023-10-04 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 17:31 [Intel-xe] [PATCH 1/3] drm/xe/vm: print the correct 'keep' when printing gpuva ops Paulo Zanoni
2023-09-29 17:31 ` [Intel-xe] [PATCH 2/3] drm/xe/vm: use list_last_entry() to fetch last_op Paulo Zanoni
2023-09-30 5:22 ` Niranjana Vishwanathapura
2023-09-29 17:31 ` [Intel-xe] [PATCH 3/3] drm/xe: fix range printing for debug messages Paulo Zanoni
2023-09-30 5:24 ` Niranjana Vishwanathapura
2023-10-04 13:18 ` Rodrigo Vivi [this message]
2023-09-29 18:21 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe/vm: print the correct 'keep' when printing gpuva ops Patchwork
2023-09-29 18:21 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-29 18:22 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-29 18:29 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-29 18:29 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-29 18:31 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-29 19:03 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-09-30 5:21 ` [Intel-xe] [PATCH 1/3] " Niranjana Vishwanathapura
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=ZR1mFbn3eVrYVoz/@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@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