From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: dev@mblankhorst.nl, thomas.hellstrom@intel.com,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2] drm/xe/migrate: Fix number of PT structs in docbook
Date: Wed, 08 Mar 2023 10:31:28 +0200 [thread overview]
Message-ID: <878rg7d4pr.fsf@intel.com> (raw)
In-Reply-To: <20230307214003.zwcgwgxkasm6cmzb@ldmartin-desk2.lan>
On Tue, 07 Mar 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Mon, Mar 06, 2023 at 05:34:59AM -0800, Niranjana Vishwanathapura wrote:
>>Update xe_migrate_doc.h with 32 page table structs (not 48)
>>
>>v2: minor typo fix
>>
>>Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
>>Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>
> unrelated fail in CI... it seems CI is applying series to the wrong
> head.
Unrelated to the patch, why isn't the documentation in xe_migrate.c?
Having a separate xe_migrate_doc.h with just a documentation comment
seems like a weird new pattern.
IMO the documentation should be placed either as a comment in the
relevant .c file or in an rst file under Documentation/gpu/xe.
BR,
Jani.
>
> applied, thanks
>
> Lucas De Marchi
>
>>---
>> drivers/gpu/drm/xe/xe_migrate_doc.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>>diff --git a/drivers/gpu/drm/xe/xe_migrate_doc.h b/drivers/gpu/drm/xe/xe_migrate_doc.h
>>index 6a68fdff08dc..63c7d67b5b62 100644
>>--- a/drivers/gpu/drm/xe/xe_migrate_doc.h
>>+++ b/drivers/gpu/drm/xe/xe_migrate_doc.h
>>@@ -21,7 +21,7 @@
>> * table BOs for updates, and identity map the entire device's VRAM with 1 GB
>> * pages.
>> *
>>- * Currently the page structure consists of 48 phyiscal pages with 16 being
>>+ * Currently the page structure consists of 32 physical pages with 16 being
>> * reserved for BO mapping during copies and clear, 1 reserved for kernel binds,
>> * several pages are needed to setup the identity mappings (exact number based
>> * on how many bits of address space the device has), and the rest are reserved
>>--
>>2.21.0.rc0.32.g243a4c7e27
>>
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-03-08 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 13:34 [Intel-xe] [PATCH v2] drm/xe/migrate: Fix number of PT structs in docbook Niranjana Vishwanathapura
2023-03-06 13:37 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/migrate: Fix number of PT structs in docbook (rev2) Patchwork
2023-03-06 13:38 ` [Intel-xe] ✗ CI.KUnit: failure " Patchwork
2023-03-07 21:40 ` [Intel-xe] [PATCH v2] drm/xe/migrate: Fix number of PT structs in docbook Lucas De Marchi
2023-03-08 8:31 ` Jani Nikula [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=878rg7d4pr.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dev@mblankhorst.nl \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=niranjana.vishwanathapura@intel.com \
--cc=thomas.hellstrom@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