From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gurchetan Singh <gurchetansingh@chromium.org>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, david@redhat.com, stefanha@redhat.com,
kraxel@redhat.com, marcandre.lureau@redhat.com,
akihiko.odaki@gmail.com, dmitry.osipenko@collabora.com,
ray.huang@amd.com, alex.bennee@linaro.org
Subject: Re: [RFC PATCH 07/13] gfxstream + rutabaga prep: define callbacks in realize function
Date: Fri, 21 Apr 2023 11:53:04 +0200 [thread overview]
Message-ID: <d3021e02-5c47-b6f3-2eba-ae9808585b8f@linaro.org> (raw)
In-Reply-To: <20230421011223.718-8-gurchetansingh@chromium.org>
On 21/4/23 03:12, Gurchetan Singh wrote:
> This reduces the amount of renderer backend specific needed to
> be exposed to the GL device. We only need one realize function
> per renderer backend.
>
> Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
> ---
> hw/display/virtio-gpu-gl.c | 17 +++++++++++------
> hw/display/virtio-gpu-virgl.c | 35 ++++++++++++++++++++++++----------
> include/hw/virtio/virtio-gpu.h | 7 -------
> 3 files changed, 36 insertions(+), 23 deletions(-)
> @@ -34,13 +39,13 @@ static void virtio_gpu_gl_class_init(ObjectClass *klass, void *data)
> VirtIOGPUBaseClass *vbc = VIRTIO_GPU_BASE_CLASS(klass);
> VirtIOGPUClass *vgc = VIRTIO_GPU_CLASS(klass);
>
> - vbc->gl_flushed = virtio_gpu_virgl_flushed;
> - vgc->handle_ctrl = virtio_gpu_virgl_handle_ctrl;
> - vgc->process_cmd = virtio_gpu_virgl_process_cmd;
> - vgc->update_cursor_data = virtio_gpu_virgl_update_cursor;
> + vbc->gl_flushed = NULL;
> + vgc->handle_ctrl = NULL;
> + vgc->process_cmd = NULL;
> + vgc->update_cursor_data = NULL;
If we don't check pointers are unset before assigning it in
virtio_gpu_virgl_device_realize(), then NULL-initializing here
is not really helpful.
> - vdc->realize = virtio_gpu_virgl_device_realize;
> - vdc->reset = virtio_gpu_virgl_reset;
> + vdc->realize = virtio_gpu_gl_device_realize;
> + vdc->reset = NULL;
> device_class_set_props(dc, virtio_gpu_gl_properties);
> }
> @@ -737,9 +752,9 @@ void virtio_gpu_virgl_device_realize(DeviceState *qdev, Error **errp)
> return;
> }
>
> - g->parent_obj.conf.flags |= (1 << VIRTIO_GPU_FLAG_VIRGL_ENABLED);
> - VIRTIO_GPU_BASE(g)->virtio_config.num_capsets =
> - virtio_gpu_virgl_get_num_capsets(g);
> + gpudev->parent_obj.conf.flags |= (1 << VIRTIO_GPU_FLAG_VIRGL_ENABLED);
Or:
VIRTIO_DEVICE(gpudev)->conf.flags |= (1 <<
VIRTIO_GPU_FLAG_VIRGL_ENABLED);
> + VIRTIO_GPU_BASE(gpudev)->virtio_config.num_capsets =
> + virtio_gpu_virgl_get_num_capsets(gpudev);
>
> virtio_gpu_device_realize(qdev, errp);
> }
Removing the NULL-inits:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
PD: I'd use "hw/display/virtio-gpu-virgl" patch prefix instead
of "gfxstream + rutabaga prep". You only start mentioning rutabaga
in the next patch. And the patches up to here could be applied
as virtio-gpu cleanup patches.
next prev parent reply other threads:[~2023-04-21 9:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 1:12 [RFC PATCH 00/13] gfxstream + rutabaga_gfx: a surprising delight or startling epiphany? Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 01/13] virtio: Add shared memory capability Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 02/13] virtio-gpu: hostmem Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 03/13] virtio-gpu blob prep: improve decoding and add memory region Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 04/13] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 05/13] gfxstream + rutabaga prep: virtio_gpu_gl -> virtio_gpu_virgl Gurchetan Singh
2023-04-21 9:40 ` Philippe Mathieu-Daudé
2023-04-21 1:12 ` [RFC PATCH 06/13] gfxstream + rutabaga prep: make GL device more library agnostic Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 07/13] gfxstream + rutabaga prep: define callbacks in realize function Gurchetan Singh
2023-04-21 9:53 ` Philippe Mathieu-Daudé [this message]
2023-04-21 1:12 ` [RFC PATCH 08/13] gfxstream + rutabaga prep: added need defintions, fields, and options Gurchetan Singh
2023-04-22 14:54 ` Akihiko Odaki
2023-04-21 1:12 ` [RFC PATCH 09/13] gfxstream + rutabaga: add required meson changes Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 10/13] gfxstream + rutabaga: add initial support for gfxstream Gurchetan Singh
2023-04-22 15:37 ` Akihiko Odaki
2023-04-21 1:12 ` [RFC PATCH 11/13] gfxstream + rutabaga: enable rutabaga Gurchetan Singh
2023-04-21 1:12 ` [RFC PATCH 12/13] HACK: use memory region API to inject memory to guest Gurchetan Singh
2023-04-22 15:46 ` Akihiko Odaki
2023-04-25 0:08 ` Gurchetan Singh
2023-04-22 19:22 ` Peter Maydell
2023-04-21 1:12 ` [RFC PATCH 13/13] HACK: schedule fence return on main AIO context Gurchetan Singh
2023-04-21 15:59 ` Stefan Hajnoczi
2023-04-21 23:20 ` Gurchetan Singh
2023-04-25 12:04 ` Stefan Hajnoczi
2023-04-21 16:02 ` [RFC PATCH 00/13] gfxstream + rutabaga_gfx: a surprising delight or startling epiphany? Stefan Hajnoczi
2023-04-21 23:54 ` Gurchetan Singh
2023-04-22 16:41 ` Akihiko Odaki
2023-04-25 0:16 ` Gurchetan Singh
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=d3021e02-5c47-b6f3-2eba-ae9808585b8f@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=david@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=stefanha@redhat.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).