Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "José Expósito" <jose.exposito89@gmail.com>
To: Karthik B S <karthik.b.s@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	Louis Chauvet <louis.chauvet@bootlin.com>,
	igt-dev@lists.freedesktop.org, zbigniew.kempczynski@intel.com,
	Jim Shargo <jshargo@chromium.org>,
	Marius Vlad <marius.vlad@collabora.com>
Subject: Re: [PATCH i-g-t v3 02/41] lib/vkms: Add minimal VKMS library and test device default files
Date: Thu, 7 Aug 2025 09:48:28 +0200	[thread overview]
Message-ID: <aJRaTBsiDcrzgA_R@fedora> (raw)
In-Reply-To: <75914ea6-0a33-4d3c-9ae7-7bd9096a7879@intel.com>

Hi everyone,

On Thu, Aug 07, 2025 at 10:10:17AM +0530, Karthik B S wrote:
> 
> On 8/5/2025 9:59 PM, Kamil Konieczny wrote:
> > Hi José,
> > On 2025-08-05 at 11:20:09 +0200, José Expósito wrote:
> > > Hi Louis,
> > > 
> > > On Wed, Jul 16, 2025 at 11:22:38AM +0200, Louis Chauvet wrote:
> > > > 
> > > > Le 15/07/2025 à 12:24, José Expósito a écrit :
> > > > > Create a library containing helpers for creating VKMS devices and
> > > > > configuring them dynamically using configfs.
> > > > > For the moment, add the minimal number of helpers to be able to start
> > > > > testing VKMS's configfs support: Create device, destroy device and
> > > > > destroy all devices.
> > > > > 
> > > > > Also, include the simplest possible test using those helpers (checking
> > > > > the device's default files) and the scaffolding required to generate
> > > > > the documentation.
> > > > > 
> > > > > Co-developed-by: Jim Shargo <jshargo@chromium.org>
> > > > > Signed-off-by: Jim Shargo <jshargo@chromium.org>
> > > > > Co-developed-by: Marius Vlad <marius.vlad@collabora.com>
> > > > > Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
> > > > > Signed-off-by: José Expósito <jose.exposito89@gmail.com>
> > > > > ---
> > > > >    docs/testplan/meson.build        |   7 +-
> > > > >    lib/igt_vkms.c                   | 207 +++++++++++++++++++++++++++++++
> > > > >    lib/igt_vkms.h                   |  27 ++++
> > > > >    lib/meson.build                  |   1 +
> > > > >    meson.build                      |   8 ++
> > > > >    tests/meson.build                |   2 +
> > > > >    tests/vkms/meson.build           |  13 ++
> > > > >    tests/vkms/vkms_configfs.c       | 132 ++++++++++++++++++++
> > > > >    tests/vkms/vkms_test_config.json |  72 +++++++++++
> > > > >    9 files changed, 467 insertions(+), 2 deletions(-)
> > > > >    create mode 100644 lib/igt_vkms.c
> > > > >    create mode 100644 lib/igt_vkms.h
> > > > >    create mode 100644 tests/vkms/meson.build
> > > > >    create mode 100644 tests/vkms/vkms_configfs.c
> > > > >    create mode 100644 tests/vkms/vkms_test_config.json
> > > > > 
> > > > > [...]
> > > > > diff --git a/lib/igt_vkms.c b/lib/igt_vkms.c
> > > > > new file mode 100644
> > > > > index 000000000..fa41f741e
> > > > > --- /dev/null
> > > > > +++ b/lib/igt_vkms.c
> > > > > [...]
> > > > > +static int detach_pipeline_items(const char *path, const struct stat *info,
> > > > > +				 const int typeflag, struct FTW *pathinfo)
> > > > As there will be a new "color pipeline" in DRM, can you rename this set of
> > > > functions to avoid confusion? I don't have preference for the name, what do
> > > > you think about "dc" for display controller?
> > Could you give a link to lore.kernel.org for this 'color pipeline'?
> > 
> > > > (ditto for the rest of the series)
> > > > 
> > > > With this modification:
> > > > Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>
> > > The "pipeline" here refers to the display pipeline as in the docs:
> > > https://docs.kernel.org/gpu/drm-kms.html#overview
> > > 
> > > Given that the VKMS driver is a display driver and that "enum vkms_pipeline_item"
> > > contains those entites, I find easy to understand what we are talking about.
> > > 
> > > What do you think about leaving the display pipeline as "pipeline" and, once we
> > > add the color pipeline, use "color_pipeline"?
> > These looks resonable. Karthik, could you comment on this?
> 
> Yes, this looks good.

Thanks for your feedback. I sent v4 with all the requested changes,
but at least for the moment, I didn't rename the pipeline:
https://lore.kernel.org/igt-dev/20250807074550.6543-1-jose.exposito89@gmail.com/

Thanks to everyone for their reviews!
Jose

> Thanks,
> Karthik.B.S
> > 
> > > I can rename all instances of "pipeline" to "display_pipeline" (with a lot of work,
> > > 100 occurences in igt_vkms.c in 41 patches), but I find it too verbose for little
> > > clarification.
> > Well, you can use sed script for this but I am afraid that there
> > are many other places in igt with 'pipeline' meaning
> > 'display pipeline', so it would be a lot more work to do.
> > 
> > Regards,
> > Kamil
> > 
> > > Jose
> > > 
> > > > > [...]
> > > > -- 
> > > > Louis Chauvet, Bootlin
> > > > Embedded Linux and Kernel engineering
> > > > https://bootlin.com

  reply	other threads:[~2025-08-07  7:48 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 10:24 [PATCH i-g-t v3 00/41] VKMS configfs tests José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 01/41] lib/drmtest: Add VKMS as a known driver type José Expósito
2025-07-16  9:22   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 02/41] lib/vkms: Add minimal VKMS library and test device default files José Expósito
2025-07-16  9:22   ` Louis Chauvet
2025-08-05  9:20     ` José Expósito
2025-08-05 16:29       ` Kamil Konieczny
2025-08-06  8:38         ` José Expósito
2025-08-07  4:40         ` Karthik B S
2025-08-07  7:48           ` José Expósito [this message]
2025-08-07  8:25             ` Louis Chauvet
2025-07-21 16:33   ` Kamil Konieczny
2025-07-23  6:40     ` Karthik B S
2025-07-15 10:24 ` [PATCH i-g-t v3 03/41] lib/vkms: Allow to enable/disable VKMS devices José Expósito
2025-07-16  9:22   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 04/41] tests/vkms_configfs: Test device invalid values José Expósito
2025-07-16  9:22   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 05/41] lib/vkms: Test plane default files José Expósito
2025-07-16  9:22   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 06/41] lib/vkms: Test plane default values José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 07/41] lib/vkms: Test plane invalid values José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 08/41] tests/vkms_configfs: Test plane valid values José Expósito
2025-07-16  9:24   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 09/41] lib/vkms: Test CRTC default files José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 10/41] lib/vkms: Test CRTC default values José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 11/41] lib/vkms: Test CRTC invalid values José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 12/41] tests/vkms_configfs: Test CRTC valid values José Expósito
2025-07-16  9:26   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 13/41] lib/vkms: Test encoder default files José Expósito
2025-07-16  9:28   ` Louis Chauvet
2025-07-21 16:35   ` Kamil Konieczny
2025-07-15 10:24 ` [PATCH i-g-t v3 14/41] lib/vkms: Test connector " José Expósito
2025-07-16  9:34   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 15/41] lib/vkms: Test connector default values José Expósito
2025-07-16  9:39   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 16/41] lib/vkms: Test connector invalid values José Expósito
2025-07-16  9:41   ` Louis Chauvet
2025-08-05 12:42     ` José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 17/41] tests/vkms_configfs: Test connector valid values José Expósito
2025-07-16  9:42   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 18/41] lib/vkms: Test attaching planes to CRTCs José Expósito
2025-07-16  9:48   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 19/41] lib/vkms: Test attaching encoders " José Expósito
2025-07-16  9:49   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 20/41] lib/vkms: Test attaching connectors to encoders José Expósito
2025-07-16  9:49   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 21/41] lib/igt_device_scan: Allow to find device by sysname José Expósito
2025-07-16  9:51   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 22/41] tests/vkms_configfs: Test enablement without pipeline items José Expósito
2025-07-16  9:53   ` Louis Chauvet
2025-07-15 10:24 ` [PATCH i-g-t v3 23/41] lib/vkms: Create VKMS device from static config José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 24/41] tests/vkms_configfs: Test adding too many planes José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 25/41] tests/vkms_configfs: Test not adding a primary plane José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 26/41] tests/vkms_configfs: Test adding multiple primary planes José Expósito
2025-07-15 10:24 ` [PATCH i-g-t v3 27/41] tests/vkms_configfs: Test adding multiple cursor planes José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 28/41] tests/vkms_configfs: Test adding a plane without possible CRTCs José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 29/41] tests/vkms_configfs: Test enabling a device without CRTCs José Expósito
2025-07-16  9:54   ` Louis Chauvet
2025-07-15 10:25 ` [PATCH i-g-t v3 30/41] tests/vkms_configfs: Test enabling a device with too many CRTCs José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 31/41] tests/vkms_configfs: Test enabling a device without encoders José Expósito
2025-07-16  9:55   ` Louis Chauvet
2025-07-15 10:25 ` [PATCH i-g-t v3 32/41] tests/vkms_configfs: Test enabling a device with too many encoders José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 33/41] tests/vkms_configfs: Test adding an encoder without possible CRTCs José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 34/41] tests/vkms_configfs: Test adding a CRTC without encoders José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 35/41] tests/vkms_configfs: Test enabling a device without connectors José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 36/41] tests/vkms_configfs: Test enabling a device with too many connectors José Expósito
2025-07-15 10:25 ` [PATCH i-g-t v3 37/41] lib/vkms: Test changing enabled device planes José Expósito
2025-07-16 12:07   ` Louis Chauvet
2025-07-15 10:25 ` [PATCH i-g-t v3 38/41] lib/vkms: Test changing enabled device CRTCs José Expósito
2025-07-16 12:07   ` Louis Chauvet
2025-07-15 10:25 ` [PATCH i-g-t v3 39/41] lib/vkms: Test changing enabled device encoders José Expósito
2025-07-16 12:08   ` Louis Chauvet
2025-07-15 10:25 ` [PATCH i-g-t v3 40/41] lib/vkms: Test changing enabled device connectors José Expósito
2025-07-16 12:08   ` Louis Chauvet
2025-07-15 10:25 ` [PATCH i-g-t v3 41/41] tests/vkms_configfs: Test connector hot-plug José Expósito
2025-07-16 12:08   ` Louis Chauvet
2025-07-15 22:34 ` ✓ Xe.CI.BAT: success for VKMS configfs tests (rev6) Patchwork
2025-07-15 22:37 ` ✓ i915.CI.BAT: " Patchwork
2025-07-16  9:14 ` ✗ Xe.CI.Full: failure " Patchwork
2025-07-16 14:20 ` ✗ i915.CI.Full: " Patchwork
2025-07-21 16:16   ` Kamil Konieczny

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=aJRaTBsiDcrzgA_R@fedora \
    --to=jose.exposito89@gmail.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jshargo@chromium.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=karthik.b.s@intel.com \
    --cc=louis.chauvet@bootlin.com \
    --cc=marius.vlad@collabora.com \
    --cc=zbigniew.kempczynski@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