From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Kim, Dongwon" <dongwon.kim@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "kraxel@redhat.com" <kraxel@redhat.com>,
"Kasireddy, Vivek" <vivek.kasireddy@intel.com>
Subject: Re: [RFC PATCH v2 1/1] drm/virtio: new fence for every plane update
Date: Mon, 13 Nov 2023 19:15:57 +0300 [thread overview]
Message-ID: <0185fa33-b0c7-194b-d44f-3d6ac967c4b5@collabora.com> (raw)
In-Reply-To: <PH8PR11MB687986353C7E238B2298897EFAD8A@PH8PR11MB6879.namprd11.prod.outlook.com>
On 10/23/23 20:31, Kim, Dongwon wrote:
...
>> Please write a guide how to test it. Are you using spice for the multi-display
>> viewer?
>
> [DW] Yeah, let me come up with a simple test case. So we use virtio-gpu as KMS device. It is used to share the guest frame with QEMU.
> SPICE is one of client solutions we use but we primarily use QEMU GTK-UI w/ multi displays (QEMU with this params '-device virtio-vga,max_outputs=2,blob=true').
> Thanks!
I'm having trouble wit h reproducing the issue. For GTK-UI you should be
using virtio-vga-gl, shouldn't you?
I assume you meant that your simple case is reproducible using dGPU,
correct? I need a test case that is reproducing using virgl and no dGPU.
Using virtio-vga-gl+virgl+max_outputs=2 I don't see any issues. In the
same time switching to the second virtual display doesn't work with
Qemu's GTK UI, I'm getting black screen for the second display. In the
KDE settings I have two displays and it says both are active. For the
first display that works, I don't see wrong frames ordering.
Please give me a test case that is reproducing using latest version of
vanilla/upstream Qemu.
--
Best regards,
Dmitry
next prev parent reply other threads:[~2023-11-13 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 1:00 [RFC PATCH v2 0/1] fence per plane state Dongwon Kim
2023-10-03 1:00 ` [RFC PATCH v2 1/1] drm/virtio: new fence for every plane update Dongwon Kim
2023-10-23 12:24 ` Dmitry Osipenko
2023-10-23 17:31 ` Kim, Dongwon
2023-11-13 16:15 ` Dmitry Osipenko [this message]
2023-11-13 18:25 ` Kim, Dongwon
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=0185fa33-b0c7-194b-d44f-3d6ac967c4b5@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=vivek.kasireddy@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;
as well as URLs for NNTP newsgroup(s).