From: Javier Martinez Canillas <javierm@redhat.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: "José Expósito" <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()
Date: Mon, 6 Jun 2022 15:57:45 +0200 [thread overview]
Message-ID: <78c1eb65-ea78-8744-5382-ea86a56a66f4@redhat.com> (raw)
In-Reply-To: <20220606135219.nwhp4fdawg2qjeam@houat>
Hello Maxime,
On 6/6/22 15:52, Maxime Ripard wrote:
> 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?
>
That's what I asked in the previous RFC too. Daniel mentioned that it shouldn't
go there because is platform specific (AFAIU, one might want to test it on x86,
aarch64, etc) but then I asked why we couldn't have a arch/um/.kunitconfig.
The answer was that's not that simple and some agreement on how to do it is needed:
https://lists.freedesktop.org/archives/dri-devel/2022-June/357617.html
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-06-06 13:58 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
2022-06-06 13:57 ` Javier Martinez Canillas [this message]
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=78c1eb65-ea78-8744-5382-ea86a56a66f4@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jose.exposito89@gmail.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime@cerno.tech \
--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
all inboxes | Powered by JetHome®