From: Vignesh Raman <vignesh.raman@collabora.com>
To: Helen Koike <helen.koike@collabora.com>, dri-devel@lists.freedesktop.org
Cc: hamohammed.sa@gmail.com, daniels@collabora.com,
rodrigosiqueiramelo@gmail.com, mairacanal@riseup.net,
guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
linux-kernel@vger.kernel.org, melissa.srw@gmail.com,
david.heidelberg@collabora.com, airlied@gmail.com
Subject: Re: [PATCH v3] drm/ci: add tests on vkms
Date: Tue, 16 Jan 2024 17:13:07 +0530 [thread overview]
Message-ID: <490b1e71-d403-02f0-bfe3-04d9f3250d18@collabora.com> (raw)
In-Reply-To: <c06f3ca9-e588-4012-b864-102ad3e7ea8d@collabora.com>
Hi Helen,
On 15/01/24 20:54, Helen Koike wrote:
>> diff --git a/drivers/gpu/drm/ci/gitlab-ci.yml
>> b/drivers/gpu/drm/ci/gitlab-ci.yml
>> index 084e3ff8e3f4..4b636d39734c 100644
>> --- a/drivers/gpu/drm/ci/gitlab-ci.yml
>> +++ b/drivers/gpu/drm/ci/gitlab-ci.yml
>> @@ -108,6 +108,7 @@ stages:
>> - rockchip
>> - virtio-gpu
>> - lint
>> + - software-driver
>
> I had created this new stage with the intention to also move virtio-gpu
> to it, so we can patch all "non-real" hardware, what do you think?
Yes we can move virtio-gpu job also to software-driver stage.
>> diff --git a/drivers/gpu/drm/ci/x86_64.config
>> b/drivers/gpu/drm/ci/x86_64.config
>> index 1cbd49a5b23a..ab4dcca749cc 100644
>> --- a/drivers/gpu/drm/ci/x86_64.config
>> +++ b/drivers/gpu/drm/ci/x86_64.config
>> @@ -24,6 +24,7 @@ CONFIG_DRM=y
>> CONFIG_DRM_PANEL_SIMPLE=y
>> CONFIG_PWM_CROS_EC=y
>> CONFIG_BACKLIGHT_PWM=y
>> +CONFIG_DRM_VKMS=y
>
> I was wondering if this wouldn't get in the way of other tests, but I
> guess IGT_FORCE_DRIVER can handle, we just need to make sure it is set
> and we are testing the correct one.
Yes, we need to skip the vkms tests for other drivers. I think we can go
with your modprobe approach. We need kmod in debian/x86_64_test-gl
container to get it working. I have created a MR in mesa for this.
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27088
Once this is merged, will uprev mesa in drm-ci and send updated vkms patch.
Thanks.
Regards,
Vignesh
prev parent reply other threads:[~2024-01-16 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 9:41 Vignesh Raman
2024-01-15 15:24 ` Helen Koike
2024-01-16 11:43 ` Vignesh Raman [this message]
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=490b1e71-d403-02f0-bfe3-04d9f3250d18@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=daniels@collabora.com \
--cc=david.heidelberg@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=hamohammed.sa@gmail.com \
--cc=helen.koike@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=sergi.blanch.torne@collabora.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
all inboxes | Powered by JetHome®