qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Dave Airlie <airlied@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] virtio-gpu/2d: add virtio gpu core code
Date: Fri, 05 Jun 2015 19:16:54 +0200	[thread overview]
Message-ID: <5571D986.2090802@redhat.com> (raw)
In-Reply-To: <1432899918-18513-3-git-send-email-kraxel@redhat.com>

On 29.05.2015 13:45, Gerd Hoffmann wrote:
> This patch adds the core code for virtio gpu emulation,
> covering 2d support.
>
> Written by Dave Airlie and Gerd Hoffmann.
>
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>   hw/display/Makefile.objs       |   2 +
>   hw/display/virtio-gpu.c        | 918 +++++++++++++++++++++++++++++++++++++++++
>   include/hw/virtio/virtio-gpu.h | 147 +++++++
>   trace-events                   |  14 +
>   4 files changed, 1081 insertions(+)
>   create mode 100644 hw/display/virtio-gpu.c
>   create mode 100644 include/hw/virtio/virtio-gpu.h

[snip]

> diff --git a/hw/display/virtio-gpu.c b/hw/display/virtio-gpu.c
> new file mode 100644
> index 0000000..f4c00a8
> --- /dev/null
> +++ b/hw/display/virtio-gpu.c
[snip]

> +static uint32_t virtio_gpu_get_features(VirtIODevice *vdev, uint32_t features)
> +{
> +    return features;
> +}

Does this series rely on some other patches? Because in master, 
VirtioDeviceClass::get_features() is still uint64_t (*)(VirtioDevice *, 
uint64_t) (which results in "hw/display/virtio-gpu.c:886:23: error: 
assignment from incompatible pointer type" for me).

(in an earlier series, this function was uint64_t ()(VirtIODevice *, 
uint64_t))

[snip]

> +int virtio_gpu_create_mapping_iov(struct virtio_gpu_resource_attach_backing *ab,
> +                                  struct virtio_gpu_ctrl_command *cmd,
> +                                  struct iovec **iov)
> +{
> +    struct virtio_gpu_mem_entry *ents;
> +    size_t esize, s;
> +    int i;
> +
> +    if (ab->nr_entries > 1024) {
> +        qemu_log_mask(LOG_GUEST_ERROR,
> +                      "%s: nr_entries is too big (%d > 1024)\n",
> +                      __func__, ab->nr_entries);
> +        return -1;
> +    }

Same question I had in said earlier series: Do you want to change this 
to 16384, because 1024 may be too small?

[snip]

> diff --git a/include/hw/virtio/virtio-gpu.h b/include/hw/virtio/virtio-gpu.h
> new file mode 100644
> index 0000000..8015beb
> --- /dev/null
> +++ b/include/hw/virtio/virtio-gpu.h
> @@ -0,0 +1,147 @@
> +/*
> + * Virtio GPU Device
> + *
> + * Copyright Red Hat, Inc. 2013-2014
> + *
> + * Authors:
> + *     Dave Airlie <airlied@redhat.com>
> + *     Gerd Hoffmann <kraxel@redhat.com>
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2.
> + * See the COPYING file in the top-level directory.
> + */
> +
> +#ifndef _QEMU_VIRTIO_VGA_H
> +#define _QEMU_VIRTIO_VGA_H
> +
> +#include "qemu/queue.h"
> +#include "ui/qemu-pixman.h"
> +#include "ui/console.h"
> +#include "hw/virtio/virtio.h"
> +#include "hw/pci/pci.h"
> +
> +#include "standard-headers/linux/virtio_gpu.h"
> +#define TYPE_VIRTIO_GPU "virtio-gpu-device"
> +#define VIRTIO_GPU(obj)                                        \
> +        OBJECT_CHECK(VirtIOGPU, (obj), TYPE_VIRTIO_GPU)
> +
> +#define VIRTIO_ID_GPU 16
> +
> +#define VIRTIO_GPU_MAX_RES 16

Still unused. Still intentional? :-)

Max

  reply	other threads:[~2015-06-05 17:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 11:45 [Qemu-devel] [PATCH 0/2] virtio-gpu/2d: add virtio gpu Gerd Hoffmann
2015-05-29 11:45 ` [Qemu-devel] [PATCH 1/2] virtio: update headers, add virtio-gpu (2d) Gerd Hoffmann
2015-06-05 17:06   ` Max Reitz
2015-05-29 11:45 ` [Qemu-devel] [PATCH 2/2] virtio-gpu/2d: add virtio gpu core code Gerd Hoffmann
2015-06-05 17:16   ` Max Reitz [this message]
2015-06-08  7:52     ` Gerd Hoffmann

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=5571D986.2090802@redhat.com \
    --to=mreitz@redhat.com \
    --cc=airlied@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).