Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Matt Roper <matthew.d.roper@intel.com>,
	Violet Monti <violet.monti@intel.com>
Subject: Re: [PATCH v3 0/7] drm/xe/rtp: Miscellaneous improvements to rule matching
Date: Fri, 22 May 2026 11:31:45 -0300	[thread overview]
Message-ID: <87zf1r1pny.fsf@intel.com> (raw)
In-Reply-To: <20260522-rtp-rule-parser-v3-0-0c51039899f4@intel.com>

Gustavo Sousa <gustavo.sousa@intel.com> writes:

> This series adds several improvements to RTP code around rule matching
> logic.
>
> It first starts with making sure there is a cleaner separation of
> responsibilities when it comes to the generic kunit testing for RTP.
> Then it goes on to improve rule matching code by making the parsing
> logic more robust and restructuring the code to resemble a formal
> grammar and make it easier to add future extensions.
>
> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>

Pushed to drm-xe-next. Thanks Matt and Violet for the reviews!

--
Gustavo Sousa

> ---
> Changes in v3:
> - Added eBNF grammar for the rules to the kernel-doc.
> - Fully reviewed now. Sent for fresh CI results.
> - Link to v2: https://patch.msgid.link/20260430-rtp-rule-parser-v2-0-157e98b4ab51@intel.com
>
> Changes in v2:
> - Incorporated review feedback. See individual patches for the
>   changelog.
> - Incorporated the addition of the match type XE_RTP_MATCH_PLATFORM_STEP
>   after rebasing on latest drm-tip, which is reflected in some of the
>   patches.
> - Link to v1: https://patch.msgid.link/20260114-rtp-rule-parser-v1-0-fa9029586bff@intel.com
>
> ---
> Gustavo Sousa (7):
>       drm/xe/rtp: Write kunit test cases specific for rule matching
>       drm/xe/rtp: Drop rule matching cases from rtp_to_sr_cases and rtp_cases
>       drm/xe/rtp: Don't short-circuit to false in or-yes case
>       drm/xe/rtp: Do not break parsing when missing context
>       drm/xe/rtp: Extract rule_match_item()
>       drm/xe/rtp: Fully parse the ruleset
>       drm/xe/rtp: Implement a structured parser for rule matching
>
>  drivers/gpu/drm/xe/tests/xe_rtp.c      |  38 ++++
>  drivers/gpu/drm/xe/tests/xe_rtp_test.c | 327 +++++++++++++++++++++------------
>  drivers/gpu/drm/xe/tests/xe_rtp_test.h |  23 +++
>  drivers/gpu/drm/xe/xe_rtp.c            | 321 +++++++++++++++++++-------------
>  drivers/gpu/drm/xe/xe_rtp.h            |  29 ++-
>  5 files changed, 486 insertions(+), 252 deletions(-)
> ---
> base-commit: 7e25390024f8a4a9fdd6ec50f000ee25c006c02f
> change-id: 20260114-rtp-rule-parser-ac01472acdeb
>
> Best regards,
> --  
> Gustavo Sousa <gustavo.sousa@intel.com>

      parent reply	other threads:[~2026-05-22 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22  8:45 [PATCH v3 0/7] drm/xe/rtp: Miscellaneous improvements to rule matching Gustavo Sousa
2026-05-22  8:45 ` [PATCH v3 1/7] drm/xe/rtp: Write kunit test cases specific for " Gustavo Sousa
2026-05-22  8:45 ` [PATCH v3 2/7] drm/xe/rtp: Drop rule matching cases from rtp_to_sr_cases and rtp_cases Gustavo Sousa
2026-05-22  8:45 ` [PATCH v3 3/7] drm/xe/rtp: Don't short-circuit to false in or-yes case Gustavo Sousa
2026-05-22  8:45 ` [PATCH v3 4/7] drm/xe/rtp: Do not break parsing when missing context Gustavo Sousa
2026-05-22  8:45 ` [PATCH v3 5/7] drm/xe/rtp: Extract rule_match_item() Gustavo Sousa
2026-05-22  8:45 ` [PATCH v3 6/7] drm/xe/rtp: Fully parse the ruleset Gustavo Sousa
2026-05-22  8:45 ` [PATCH v3 7/7] drm/xe/rtp: Implement a structured parser for rule matching Gustavo Sousa
2026-05-22  8:51 ` ✗ CI.checkpatch: warning for drm/xe/rtp: Miscellaneous improvements to rule matching (rev3) Patchwork
2026-05-22  8:53 ` ✓ CI.KUnit: success " Patchwork
2026-05-22  9:31 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-22 13:31 ` ✓ Xe.CI.FULL: " Patchwork
2026-05-22 14:31 ` Gustavo Sousa [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=87zf1r1pny.fsf@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=violet.monti@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