On 2/6/25 18:17, Sasha Finkelstein wrote:
> On Wed, 29 Jan 2025 at 15:40, Dmitry Osipenko
> wrote:
>> Otherwise, the proper solution would be to pass info about host's page
>> size to guest using extended virtio protocol.
>
> It is not fully clear to me, as to what exactly is meant by that.
> IIU
On Wed, 29 Jan 2025 at 15:40, Dmitry Osipenko
wrote:
> Otherwise, the proper solution would be to pass info about host's page
> size to guest using extended virtio protocol.
It is not fully clear to me, as to what exactly is meant by that.
IIUC, virtio is a spec managed externally, so does that m
On 1/26/25 00:08, Sasha Finkelstein via B4 Relay wrote:
> --- a/drivers/gpu/drm/virtio/virtgpu_vram.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_vram.c
> @@ -150,8 +150,8 @@ static int virtio_gpu_vram_map(struct virtio_gpu_object
> *bo)
> return -EINVAL;
>
> spin_lock(&vgdev->hos
On Mon, 27 Jan 2025 at 08:31, Thomas Zimmermann wrote:
> This is per-architecture code and does not belong in a DRM driver.
I agree that this is not quite the place, and ideally i'd use MAX_PAGE_SIZE
from https://lore.kernel.org/all/20241014105514.3206191-1-ryan.robe...@arm.com/
however that seri
Hi
Am 25.01.25 um 22:08 schrieb Sasha Finkelstein via B4 Relay:
From: Sasha Finkelstein
This allows running different page sizes between host and guest on
platforms that support mixed page sizes.
Signed-off-by: Sasha Finkelstein
---
Changes in v2:
- Aligned all object sizes to MAX_PAGE_SIZE
From: Sasha Finkelstein
This allows running different page sizes between host and guest on
platforms that support mixed page sizes.
Signed-off-by: Sasha Finkelstein
---
Changes in v2:
- Aligned all object sizes to MAX_PAGE_SIZE too.
- Link to v1:
https://lore.kernel.org/r/20250109-virtgpu-mixe
