From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Matt Roper <matthew.d.roper@intel.com>,
Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: Re: [PATCH v2 1/2] drm/xe/tests/pci: Convert GT count check to general device check
Date: Wed, 22 Oct 2025 10:31:14 -0300 [thread overview]
Message-ID: <176113987409.3231.6079039608938116945@intel.com> (raw)
In-Reply-To: <iy5fneu7goe5dzqmawkkep5pdtkbr5xn5s6oyqklzm22gdsul7@25wccgtulxgk>
Quoting Lucas De Marchi (2025-10-20 23:07:47-03:00)
>On Mon, Oct 20, 2025 at 08:57:44PM -0300, Gustavo Sousa wrote:
>>Quoting Gustavo Sousa (2025-10-20 20:45:56-03:00)
>>>We already have check_graphics_ip() and check_media_ip() as general
>>>functions to check the IP descriptors. The check in
>>>check_platform_gt_count() is simple enough such that we can convert the
>>>function to a more general device check. In an upcoming change, we will
>>>also add some checks for other members of struct xe_device_desc. As
>>>such, rename check_platform_gt_count() to check_platform_desc().
>>>
>>>While at it, use inline (unsigned int) casting of max_gt_per_tile to
>>>keep checks for each member localized; and use KUNIT_EXPECT_*() variants
>>>of the macros to allow multiple issues to be reported.
>>>
>>>v2:
>>> - Use (int) instead of (unsigned int) casting. (Michal)
>>
>>Whoops. It's actually the other way around. I'll fix it when applying.
>
>or just follow the kernel docs[1] and don't add changelogs to the patch
>themselves.
Okay. Removed them.
By the way, do we have instructions documented somewhere about the
general policy for drm (or maybe also i915 and i915/display)?
By doing calling the following git log on drm-tip
git log --no-merges -- drivers/gpu/drm/drm_'*'
I see a mixture of styles: some commits include the changelog and others
don't. For some of the latter, we can see the the changelog is in the
patch email, below the "---" line.
If there is some documentation on the subject on the DRM-level, then
perhaps we would need to list xe as one of the drivers that opted out.
>
>>
>>> - Use KUNIT_EXPECT_*() instead of UNIT_ASSERT_*() macros. (Michal)
>>>
>>>Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
>Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
Thanks!
--
Gustavo Sousa
>
>Lucas De Marchi
>
>[1] https://docs.kernel.org/process/submitting-patches.html#commentary
next prev parent reply other threads:[~2025-10-22 13:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 23:45 [PATCH v2 0/2] drm/xe: Add kunit checks for dma_mask_size, va_bits and vm_max_level Gustavo Sousa
2025-10-20 23:45 ` [PATCH v2 1/2] drm/xe/tests/pci: Convert GT count check to general device check Gustavo Sousa
2025-10-20 23:57 ` Gustavo Sousa
2025-10-21 2:07 ` Lucas De Marchi
2025-10-22 13:31 ` Gustavo Sousa [this message]
2025-10-20 23:45 ` [PATCH v2 2/2] drm/xe/tests/pci: Check dma_mask_size, va_bits and vm_max_level Gustavo Sousa
2025-10-21 2:09 ` Lucas De Marchi
2025-10-21 12:52 ` ✓ CI.KUnit: success for drm/xe: Add kunit checks for dma_mask_size, va_bits and vm_max_level (rev2) Patchwork
2025-10-21 13:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-21 14:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-22 12:42 ` Gustavo Sousa
2025-10-22 13:32 ` [PATCH v2 0/2] drm/xe: Add kunit checks for dma_mask_size, va_bits and vm_max_level Gustavo Sousa
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=176113987409.3231.6079039608938116945@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@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