From: Lucas De Marchi <lucas.demarchi@intel.com>
To: "Michał Winiarski" <michal@hardline.pl>
Cc: intel-xe@lists.freedesktop.org, maarten.lankhorst@intel.com
Subject: Re: [Intel-xe] [PATCH 1/7] drm/xe: Add basic unit tests for rtp
Date: Fri, 31 Mar 2023 08:34:21 -0600 [thread overview]
Message-ID: <20230331143337.vtlyhttwwqfv2tad@ldmartin-desk2> (raw)
In-Reply-To: <adnojpupaqnivif7aqblxkuiwyiexskk4h3b36bsktbpifoip3@b7xazecr7exv>
On Mon, Mar 27, 2023 at 07:56:01PM +0200, Michał Winiarski wrote:
>On Tue, Mar 21, 2023 at 03:05:21PM -0700, Lucas De Marchi wrote:
>> +EXPORT_SYMBOL(xe_rtp_process_incompat_types);
>> diff --git a/drivers/gpu/drm/xe/tests/xe_rtp_test.c b/drivers/gpu/drm/xe/tests/xe_rtp_test.c
>> new file mode 100644
>> index 000000000000..4a12aad3f759
>> --- /dev/null
>> +++ b/drivers/gpu/drm/xe/tests/xe_rtp_test.c
>
>There's no need to have this as a separate file.
>We can move the contents of tests/xe_rtp.c into tests/xe_rtp_test.c and
>include tests/xe_rtp_test.c directly in xe_rtp.c
this is not how the tests are currently structured.
xe_rtp.c includes tests/xe_rtp.c. The latter can be seen as "an
extension of the that file, exporting whatever entrypoint is needed
for the real test". They are then part of the xe.ko module.
tests/xe_rtp_test.c is the one in the separate test module, and contains
the integration with kunit.
For some of the tests, when they don't export the required interface,
this unfortunately means writing most of the test inside tests/xe_rtp.c,
which ends up bloating xe.ko. This is not true for all, however. See
the xe_wa tests where we don't even have tests/xe_wa.c.
Lucas De Marchi
next prev parent reply other threads:[~2023-03-31 14:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 22:05 [Intel-xe] [PATCH 0/7] Unit tests for rtp and GT wa/tuning Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 1/7] drm/xe: Add basic unit tests for rtp Lucas De Marchi
2023-03-27 17:56 ` Michał Winiarski
2023-03-31 13:43 ` Lucas De Marchi
2023-04-01 8:59 ` Lucas De Marchi
2023-04-01 18:54 ` Michał Winiarski
2023-04-02 1:24 ` Lucas De Marchi
2023-04-02 10:51 ` Michal Wajdeczko
2023-03-31 14:34 ` Lucas De Marchi [this message]
2023-04-01 8:54 ` Lucas De Marchi
2023-04-01 18:26 ` Michał Winiarski
2023-04-02 1:34 ` Lucas De Marchi
2023-04-02 11:17 ` Michal Wajdeczko
2023-04-02 21:54 ` Lucas De Marchi
2023-04-03 7:38 ` Michal Wajdeczko
2023-04-03 13:02 ` Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 2/7] drm/xe: Extract function to initialize xe->info Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 3/7] drm/xe: Move test infra out of xe_pci.[ch] Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 4/7] drm/xe: Use XE_KUNIT for symbol namespace Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 5/7] drm/xe: Generalize fake device creation Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 6/7] drm/xe/reg_sr: Save errors for kunit integration Lucas De Marchi
2023-03-27 18:29 ` Michał Winiarski
2023-03-31 14:43 ` Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 7/7] drm/xe: Add test for GT workarounds and tunings Lucas De Marchi
2023-03-21 22:08 ` [Intel-xe] ✓ CI.Patch_applied: success for Unit tests for rtp and GT wa/tuning Patchwork
2023-03-31 15:14 ` Lucas De Marchi
2023-04-03 6:08 ` Mauro Carvalho Chehab
2023-03-21 22:09 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-21 22:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-21 22:25 ` [Intel-xe] ○ CI.BAT: info " 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=20230331143337.vtlyhttwwqfv2tad@ldmartin-desk2 \
--to=lucas.demarchi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=michal@hardline.pl \
/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