From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
Matthew Brost <matthew.brost@intel.com>,
himal.prasad.ghimiray@intel.com,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH v4 5/5] drm/xe: Make the PT code handle placement per PTE rather than per vma / range
Date: Tue, 01 Apr 2025 13:55:39 +0200 [thread overview]
Message-ID: <5bf94f57b3d2bed5af7585b95b0bb67480cdbb3f.camel@linux.intel.com> (raw)
In-Reply-To: <x53tcs5bjldw6lcorjemuheklxcmepdvr2u7lvt3hpqrzqoc4h@nsu6hs25taqj>
Hi, Lucas, Thanks for noticing. See inline.
On Mon, 2025-03-31 at 10:55 -0500, Lucas De Marchi wrote:
> On Wed, Mar 26, 2025 at 09:05:51AM +0100, Thomas Hellström wrote:
> > diff --git a/drivers/gpu/drm/xe/xe_pt.c
> > b/drivers/gpu/drm/xe/xe_pt.c
> > index 9e719535a3bb..82ae159feed1 100644
> > --- a/drivers/gpu/drm/xe/xe_pt.c
> > +++ b/drivers/gpu/drm/xe/xe_pt.c
> > @@ -278,13 +278,15 @@ struct xe_pt_stage_bind_walk {
> > struct xe_vm *vm;
> > /** @tile: The tile we're building for. */
> > struct xe_tile *tile;
> > - /** @default_pte: PTE flag only template. No address is
> > associated */
> > - u64 default_pte;
> > + /** @default_pte: PTE flag only template for VRAM. No
> > address is associated */
>
> ^
> > + u64 default_vram_pte;
>
> ^
>
> doc is wrong here. This would fix that for this patch:
>
> // diff --git a/drivers/gpu/drm/xe/xe_pt.c
> b/drivers/gpu/drm/xe/xe_pt.c
> // index 82ae159feed12..91ad347c8c7bf 100644
> // --- a/drivers/gpu/drm/xe/xe_pt.c
> // +++ b/drivers/gpu/drm/xe/xe_pt.c
> // @@ -278,9 +278,9 @@ struct xe_pt_stage_bind_walk {
> // struct xe_vm *vm;
> // /** @tile: The tile we're building for. */
> // struct xe_tile *tile;
> // - /** @default_pte: PTE flag only template for VRAM. No
> address is associated */
> // + /** @default_vram_pte: PTE flag only template for VRAM. No
> address is associated */
> // u64 default_vram_pte;
> // - /** @default_pte: PTE flag only template for VRAM. No
> address is associated */
> // + /** @default_system_pte: PTE flag only template for
> system. No address is associated */
> // u64 default_system_pte;
> // /** @dma_offset: DMA offset to add to the PTE. */
> // u64 dma_offset;
>
>
> However I was surprised that we didn't get any error in our CI.Hooks.
>
>
> It looks like this entire struct is not in our docs at all:
> https://docs.kernel.org/gpu/xe/xe_mm.html#pagetable-building
>
> Should we add a
>
> /**
> * struct xe_pt_stage_bind_walk - ...
> */
>
> so it's visible? Or if it's internal detail from
> drivers/gpu/drm/xe/xe_pt.c maybe we could drop the kernel-doc,
> leaving
> them as "/*" comments instead?
I think it's worth having it kerneldoc'ed. I'll submit a patch for that
+ the fixes above unless you have it already in the pipe.
Thanks,
Thomas
>
> Lucas De Marchi
next prev parent reply other threads:[~2025-04-01 11:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 8:05 [PATCH v4 0/5] drm/xe: xe-only patches from the multi-device GPUSVM series Thomas Hellström
2025-03-26 8:05 ` [PATCH v4 1/5] drm/xe: Introduce CONFIG_DRM_XE_GPUSVM Thomas Hellström
2025-03-26 8:05 ` [PATCH v4 2/5] drm/xe/svm: Fix a potential bo UAF Thomas Hellström
2025-03-26 9:31 ` Ghimiray, Himal Prasad
2025-03-26 9:42 ` Thomas Hellström
2025-03-26 8:05 ` [PATCH v4 3/5] drm/xe/bo: Add a bo remove callback Thomas Hellström
2025-03-26 9:07 ` Matthew Auld
2025-03-26 8:05 ` [PATCH v4 4/5] drm/xe/migrate: Allow xe_migrate_vram() also on non-pagefault capable devices Thomas Hellström
2025-03-26 8:05 ` [PATCH v4 5/5] drm/xe: Make the PT code handle placement per PTE rather than per vma / range Thomas Hellström
2025-03-26 9:48 ` Ghimiray, Himal Prasad
2025-03-31 15:55 ` Lucas De Marchi
2025-04-01 11:55 ` Thomas Hellström [this message]
2025-04-01 14:04 ` Lucas De Marchi
2025-03-26 8:12 ` ✓ CI.Patch_applied: success for drm/xe: xe-only patches from the multi-device GPUSVM series (rev6) Patchwork
2025-03-26 8:12 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-26 8:14 ` ✓ CI.KUnit: success " Patchwork
2025-03-26 8:30 ` ✓ CI.Build: " Patchwork
2025-03-26 8:32 ` ✓ CI.Hooks: " Patchwork
2025-03-26 8:34 ` ✓ CI.checksparse: " Patchwork
2025-03-26 8:55 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-26 22:32 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-27 9:00 ` Patchwork
2025-03-27 9:41 ` Patchwork
2025-03-27 10:38 ` Thomas Hellström
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=5bf94f57b3d2bed5af7585b95b0bb67480cdbb3f.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--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