qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Gurchetan Singh <gurchetansingh@chromium.org>, qemu-devel@nongnu.org
Cc: philmd@linaro.org, kraxel@redhat.com,
	marcandre.lureau@redhat.com, dmitry.osipenko@collabora.com,
	ray.huang@amd.com, alex.bennee@linaro.org, shentey@gmail.com
Subject: Re: [PATCH v3 0/5] virtio-gpu cleanups and obvious definitions
Date: Fri, 5 May 2023 13:56:02 +0900	[thread overview]
Message-ID: <168d3290-1db5-6dda-1464-493c18473760@gmail.com> (raw)
In-Reply-To: <20230504191243.746-1-gurchetansingh@chromium.org>

On 2023/05/05 4:12, Gurchetan Singh wrote:
> From: Gurchetan Singh <gurchetansingh@google.com>
> 
> v3 of "virtio-gpu cleanups and obvious definitions"
> 
> https://lists.gnu.org/archive/html/qemu-devel/2023-04/msg05392.html
> 
> All patches have been reviewed, though there was a question from
> Bernhard Beschow about patch (3) and how it fits with the QOM:
> 
> https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg00057.html
> 
> I go into detail in patch 3 commit message, but I think we meet
> the requirements (which are tricky/fuzzy anyways).  Also, I think
> this is the cleanest way to add another 3D virtgpu backend.  But
> if anyone has other ideas, please do reply/review.
> 
> Antonio Caggiano (1):
>    virtio-gpu: CONTEXT_INIT feature
> 
> Dr. David Alan Gilbert (1):
>    virtio: Add shared memory capability
> 
> Gurchetan Singh (3):
>    hw/display/virtio-gpu-virgl: virtio_gpu_gl -> virtio_gpu_virgl
>    hw/display/virtio-gpu-virgl: make GL device more library agnostic
>    hw/display/virtio-gpu-virgl: define callbacks in realize function
> 
>   hw/display/virtio-gpu-base.c   |   3 +
>   hw/display/virtio-gpu-gl.c     | 114 +--------------------------
>   hw/display/virtio-gpu-virgl.c  | 137 +++++++++++++++++++++++++++++++--
>   hw/virtio/virtio-pci.c         |  18 +++++
>   include/hw/virtio/virtio-gpu.h |  11 +--
>   include/hw/virtio/virtio-pci.h |   4 +
>   6 files changed, 160 insertions(+), 127 deletions(-)
> 

For all patches:

Reviewed-by: Akihiko Odaki <akihiko.odaki@daynix.com>


  parent reply	other threads:[~2023-05-05  4:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 19:12 [PATCH v3 0/5] virtio-gpu cleanups and obvious definitions Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 1/5] hw/display/virtio-gpu-virgl: virtio_gpu_gl -> virtio_gpu_virgl Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 2/5] hw/display/virtio-gpu-virgl: make GL device more library agnostic Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 3/5] hw/display/virtio-gpu-virgl: define callbacks in realize function Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 4/5] virtio: Add shared memory capability Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 5/5] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-05-05  4:56 ` Akihiko Odaki [this message]
2023-05-09 12:43 ` [PATCH v3 0/5] virtio-gpu cleanups and obvious definitions Marc-André Lureau
2023-05-09 17:53   ` 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=168d3290-1db5-6dda-1464-493c18473760@gmail.com \
    --to=akihiko.odaki@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=dmitry.osipenko@collabora.com \
    --cc=gurchetansingh@chromium.org \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ray.huang@amd.com \
    --cc=shentey@gmail.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).