From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Gustavo Sousa <gustavo.sousa@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH v2 0/7] drm/xe/rtp: Miscellaneous improvements to rule matching
Date: Thu, 30 Apr 2026 17:20:01 -0300 [thread overview]
Message-ID: <20260430-rtp-rule-parser-v2-0-157e98b4ab51@intel.com> (raw)
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>
---
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 +++++++++++++++++++-------------
4 files changed, 461 insertions(+), 248 deletions(-)
---
base-commit: f3b0eacc6be937779388c8412909b66717926980
change-id: 20260114-rtp-rule-parser-ac01472acdeb
Best regards,
--
Gustavo Sousa <gustavo.sousa@intel.com>
next reply other threads:[~2026-04-30 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 20:20 Gustavo Sousa [this message]
2026-04-30 20:20 ` [PATCH v2 1/7] drm/xe/rtp: Write kunit test cases specific for rule matching Gustavo Sousa
2026-04-30 20:20 ` [PATCH v2 2/7] drm/xe/rtp: Drop rule matching cases from rtp_to_sr_cases and rtp_cases Gustavo Sousa
2026-04-30 20:20 ` [PATCH v2 3/7] drm/xe/rtp: Don't short-circuit to false in or-yes case Gustavo Sousa
2026-04-30 20:20 ` [PATCH v2 4/7] drm/xe/rtp: Do not break parsing when missing context Gustavo Sousa
2026-04-30 20:20 ` [PATCH v2 5/7] drm/xe/rtp: Extract rule_match_item() Gustavo Sousa
2026-04-30 20:20 ` [PATCH v2 6/7] drm/xe/rtp: Fully parse the ruleset Gustavo Sousa
2026-04-30 20:20 ` [PATCH v2 7/7] drm/xe/rtp: Implement a structured parser for rule matching Gustavo Sousa
2026-04-30 21:02 ` ✗ CI.checkpatch: warning for drm/xe/rtp: Miscellaneous improvements to rule matching (rev2) Patchwork
2026-04-30 21:03 ` ✓ CI.KUnit: success " Patchwork
2026-04-30 21:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-01 9:25 ` ✗ Xe.CI.FULL: failure " Patchwork
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=20260430-rtp-rule-parser-v2-0-157e98b4ab51@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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