From: Maxime Ripard <maxime@cerno.tech>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: davidgow@google.com, airlied@linux.ie, dlatypov@google.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
tzimmermann@suse.de, "José Expósito" <jose.exposito89@gmail.com>,
kunit-dev@googlegroups.com
Subject: Re: [PATCH 1/1] drm/format-helper: Add KUnit tests for drm_fb_xrgb8888_to_rgb332()
Date: Mon, 6 Jun 2022 15:52:19 +0200 [thread overview]
Message-ID: <20220606135219.nwhp4fdawg2qjeam@houat> (raw)
In-Reply-To: <576ed6ef-b961-9214-2c9b-56cb5b493b4e@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]
hi,
On Mon, Jun 06, 2022 at 03:49:57PM +0200, Javier Martinez Canillas wrote:
> Hello Maxime,
>
> On 6/6/22 15:42, Maxime Ripard wrote:
> > Hi,
> >
> > On Mon, Jun 06, 2022 at 11:55:16AM +0200, José Expósito 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=drivers/gpu/drm \
> >> --kconfig_add CONFIG_VIRTIO_UML=y \
> >> --kconfig_add CONFIG_UML_PCI_OVER_VIRTIO=y
> >
> > 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=drivers/gpu/drm/.kunitconfig
> [15:47:31] Configuring KUnit Kernel ...
> Regenerating .config ...
> Populating config with:
> $ make ARCH=um O=.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=y, CONFIG_DRM_KUNIT_TEST=y
> Note: many Kconfig options aren't available on UML. You can try running on a different architecture with something like "--arch=x86_64".
>
> The following works correctly but it won't use User Mode Linux:
>
> ./tools/testing/kunit/kunit.py run --kunitconfig=drivers/gpu/drm/.kunitconfig --arch=x86_64
But then, can't we add them to .kunitconfig?
We should avoid that gotcha entirely
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-06-06 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 9:55 [PATCH 0/1] KUnit tests for drm_format_helper José Expósito
2022-06-06 9:55 ` [PATCH 1/1] drm/format-helper: Add KUnit tests for drm_fb_xrgb8888_to_rgb332() José Expósito
2022-06-06 13:40 ` Javier Martinez Canillas
2022-06-06 16:30 ` José Expósito
2022-06-06 13:42 ` Maxime Ripard
2022-06-06 13:49 ` Javier Martinez Canillas
2022-06-06 13:52 ` Maxime Ripard [this message]
2022-06-06 13:57 ` Javier Martinez Canillas
2022-06-06 14:09 ` Maxime Ripard
2022-06-06 14:19 ` Daniel Latypov
2022-06-06 14:44 ` Javier Martinez Canillas
2022-06-07 7:22 ` Thomas Zimmermann
2022-06-07 17:54 ` José Expósito
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=20220606135219.nwhp4fdawg2qjeam@houat \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jose.exposito89@gmail.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).