Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Feedback-ID: i8771445c:Fastmail
Date:   Mon, 6 Jun 2022 16:09:17 +0200
From:   Maxime Ripard <maxime@cerno.tech>
To:     Javier Martinez Canillas <javierm@redhat.com>
Cc:     =?utf-8?B?Sm9zw6kgRXhww7NzaXRv?= <jose.exposito89@gmail.com>,
        davidgow@google.com, dlatypov@google.com, tzimmermann@suse.de,
        maarten.lankhorst@linux.intel.com, airlied@linux.ie,
        daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
        kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] drm/format-helper: Add KUnit tests for
 drm_fb_xrgb8888_to_rgb332()
Message-ID: <20220606140917.suwk3uqxzsqeiab2@houat>
References: <20220606095516.938934-1-jose.exposito89@gmail.com>
 <20220606095516.938934-2-jose.exposito89@gmail.com>
 <20220606134242.h6kuqn4zbpmc2rql@houat>
 <576ed6ef-b961-9214-2c9b-56cb5b493b4e@redhat.com>
 <20220606135219.nwhp4fdawg2qjeam@houat>
 <78c1eb65-ea78-8744-5382-ea86a56a66f4@redhat.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="hinoebkwkjhusomc"
Content-Disposition: inline
In-Reply-To: <78c1eb65-ea78-8744-5382-ea86a56a66f4@redhat.com>
Precedence: bulk


--hinoebkwkjhusomc
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 06, 2022 at 03:57:45PM +0200, Javier Martinez Canillas wrote:
> Hello Maxime,
>=20
> On 6/6/22 15:52, Maxime Ripard wrote:
> > hi,
> >=20
> > On Mon, Jun 06, 2022 at 03:49:57PM +0200, Javier Martinez Canillas wrot=
e:
> >> Hello Maxime,
> >>
> >> On 6/6/22 15:42, Maxime Ripard wrote:
> >>> Hi,
> >>>
> >>> On Mon, Jun 06, 2022 at 11:55:16AM +0200, Jos=E9 Exp=F3sito wrote:
> >>>> Test the conversion from XRGB8888 to RGB332.
> >>>>
> >>>> What is tested?
> >>>>
> >>>>  - Different values for the X in XRGB8888 to make sure it is ignored
> >>>>  - Different clip values: Single pixel and full and partial buffer
> >>>>  - Well known colors: White, black, red, green, blue, magenta, yellow
> >>>>    and cyan
> >>>>  - Other colors: Randomly picked
> >>>>  - Destination pitch
> >>>>
> >>>> How to run the tests?
> >>>>
> >>>>  $ ./tools/testing/kunit/kunit.py run --kunitconfig=3Ddrivers/gpu/dr=
m \
> >>>>          --kconfig_add CONFIG_VIRTIO_UML=3Dy \
> >>>>          --kconfig_add CONFIG_UML_PCI_OVER_VIRTIO=3Dy
> >>>
> >>> It's not clear to me why you would need VIRTIO here? The Kunit config
> >>> file should be enough to run the tests properly
> >>>
> >>
> >> It's needed or otherwise KUnit will complain with:
> >>
> >> ./tools/testing/kunit/kunit.py run --kunitconfig=3Ddrivers/gpu/drm/.ku=
nitconfig
> >> [15:47:31] Configuring KUnit Kernel ...
> >> Regenerating .config ...
> >> Populating config with:
> >> $ make ARCH=3Dum O=3D.kunit olddefconfig
> >> ERROR:root:Not all Kconfig options selected in kunitconfig were in the=
 generated .config.
> >> This is probably due to unsatisfied dependencies.
> >> Missing: CONFIG_DRM=3Dy, CONFIG_DRM_KUNIT_TEST=3Dy
> >> Note: many Kconfig options aren't available on UML. You can try runnin=
g on a different architecture with something like "--arch=3Dx86_64".
> >>
> >> The following works correctly but it won't use User Mode Linux:
> >>
> >> ./tools/testing/kunit/kunit.py run --kunitconfig=3Ddrivers/gpu/drm/.ku=
nitconfig --arch=3Dx86_64
> >=20
> > But then, can't we add them to .kunitconfig?
> >
>=20
> That's what I asked in the previous RFC too. Daniel mentioned that it sho=
uldn't
> go there because is platform specific (AFAIU, one might want to test it o=
n x86,
> aarch64, etc) but then I asked why we couldn't have a arch/um/.kunitconfi=
g.
>=20
> The answer was that's not that simple and some agreement on how to do it =
is needed:
>=20
> https://lists.freedesktop.org/archives/dri-devel/2022-June/357617.html

Thanks for pointing this out. So yeah, it's indeed not very optimal

We should probably just document it somewhere in KMS then? It doesn't
have to be in this patch series, but I have the feeling that we will end
up with that discussion a lot from people frustrated to have spent too
much time figuring it out :)

Maxime

--hinoebkwkjhusomc
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCYp4KjQAKCRDj7w1vZxhR
xcJMAP99qsO7FgUwevO9U74+Tm8BrRBDMWERHZvHOG3KcT4wrwD/QBNjSrBbIMvm
xKS0u3DrSP9u+bXKM/YCl/qgLvwRuwM=
=8VNg
-----END PGP SIGNATURE-----

--hinoebkwkjhusomc--