From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Torrente <igor.torrente@collabora.com>
Cc: samimdko <sami.md.ko@gmail.com>,
virtualization <virtualization@lists.linux.dev>,
linux-kernel <linux-kernel@vger.kernel.org>,
eperezma <eperezma@redhat.com>,
xuanzhuo <xuanzhuo@linux.alibaba.com>,
jasowang <jasowang@redhat.com>,
Dmitrii Osipenko <dmitry.osipenko@collabora.com>
Subject: Re: `virtio: reject shm region if length is zero` breaks virtio-gpu host_visible feature
Date: Wed, 6 Aug 2025 16:47:27 -0400 [thread overview]
Message-ID: <20250806164708-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <19880aa3804.3aa8c0311540629.5527706858754550702@collabora.com>
On Wed, Aug 06, 2025 at 03:34:55PM -0300, Igor Torrente wrote:
> Hello,
>
> The commit `206cc44588f7 virtio: reject shm region if length is zero` breaks the Virtio-gpu `host_visible` feature.
>
> As you can see in the snippet below, host_visible_region is zero because of the `kzalloc`.
> It's using the `vm_get_shm_region` (drivers/virtio/virtio_mmio.c:536) to read the `addr` and `len` from qemu/crosvm.
>
> ```
> drivers/gpu/drm/virtio/virtgpu_kms.c
> 132 vgdev = drmm_kzalloc(dev, sizeof(struct virtio_gpu_device), GFP_KERNEL);
> [...]
> 177 if (virtio_get_shm_region(vgdev->vdev, &vgdev->host_visible_region,
> 178 VIRTIO_GPU_SHM_ID_HOST_VISIBLE)) {
> ```
> Now it always fails.
>
> I don't know exactly what issue this patch is trying to solve, but right now Virtio-gpu relies upon the previous behavior.
> Can we just revert it?
>
> BR,
> ----
> Igor Torrente
Pls go ahead and post the revert. We'll see what happens.
--
MST
prev parent reply other threads:[~2025-08-06 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 18:34 `virtio: reject shm region if length is zero` breaks virtio-gpu host_visible feature Igor Torrente
2025-08-06 20:47 ` Michael S. Tsirkin [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=20250806164708-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=eperezma@redhat.com \
--cc=igor.torrente@collabora.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sami.md.ko@gmail.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.