From: Gerd Hoffmann <kraxel@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Dave Airlie <airlied@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] virtio-gpu/2d: add virtio gpu core code
Date: Mon, 08 Jun 2015 09:52:31 +0200 [thread overview]
Message-ID: <1433749951.5046.27.camel@redhat.com> (raw)
In-Reply-To: <5571D986.2090802@redhat.com>
Hi,
> > +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).
master was 32bit until recently (a few days back), now 64bit features
are finally merged and this mess should come to an end ;)
> (in an earlier series, this function was uint64_t ()(VirtIODevice *,
> uint64_t))
Earlier versions used to depend on unmerged virtio patches, this one was
for master ...
> > + 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?
Oops, fixed.
> > +#define VIRTIO_GPU_MAX_RES 16
>
> Still unused. Still intentional? :-)
Fixed too.
cheers,
Gerd
prev parent reply other threads:[~2015-06-08 7:52 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
2015-06-08 7:52 ` Gerd Hoffmann [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=1433749951.5046.27.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=mreitz@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).