qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next
Date: Thu, 5 Nov 2015 12:49:11 +0100	[thread overview]
Message-ID: <563B4237.6050709@redhat.com> (raw)
In-Reply-To: <CAFEAcA_2UQhFcH+yWugVVtdptT9s8BnF_jimLX_Z_X=93gADHw@mail.gmail.com>



On 05/11/2015 12:42, Peter Maydell wrote:
> I tried to do a linux headers update against kvm/next (commit
> 197a4f4b063e4) with update-linux-headers.sh, but the result gives
> a virtio-gpu that doesn't compile:
> 
> make: Entering directory
> `/home/petmay01/linaro/qemu-from-laptop/qemu/build/all-debug'
>   CC    aarch64-softmmu/hw/display/virtio-gpu.o
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:
> In function ‘virtio_gpu_get_features’:
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:149:27:
> error: ‘VIRTIO_GPU_FEATURE_VIRGL’ undeclared (first use in this
> function)
>          features |= (1 << VIRTIO_GPU_FEATURE_VIRGL);
>                            ^
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:149:27:
> note: each undeclared identifier is reported only once for each
> function it appears in
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:
> In function ‘virtio_gpu_set_features’:
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:156:41:
> error: ‘VIRTIO_GPU_FEATURE_VIRGL’ undeclared (first use in this
> function)
>      static const uint32_t virgl = (1 << VIRTIO_GPU_FEATURE_VIRGL);
>                                          ^
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:
> In function ‘virtio_gpu_device_realize’:
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:914:25:
> error: ‘struct virtio_gpu_config’ has no member named ‘num_capsets’
>          g->virtio_config.num_capsets = 1;
>                          ^
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:
> At top level:
> /home/petmay01/linaro/qemu-from-laptop/qemu/hw/display/virtio-gpu.c:1035:46:
> error: invalid application of ‘sizeof’ to incomplete type ‘struct
> virtio_gpu_transfer_host_3d’
>  QEMU_BUILD_BUG_ON(sizeof(struct virtio_gpu_transfer_host_3d)        != 72);
>                                               ^
> 
> etc, because all the virtio_gpu definitions disappear from
> include/standard-headers/linux/virtio_gpu.h.
> 
> What's happening here?

My guess: these will get into Linus's tree in a few days, and the update
was done on a maintainer tree.

Paolo

  reply	other threads:[~2015-11-05 11:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 11:42 [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next Peter Maydell
2015-11-05 11:49 ` Paolo Bonzini [this message]
2015-11-05 12:13 ` Gerd Hoffmann
2015-11-05 12:32   ` Peter Maydell
2015-11-05 13:23     ` Christian Borntraeger
2015-11-05 13:44       ` Peter Maydell
2015-11-05 13:46         ` Christian Borntraeger
2015-11-05 14:01         ` Paolo Bonzini
2015-11-05 14:30           ` Peter Maydell
2015-11-05 14:52             ` Peter Maydell
2015-11-05 15:03               ` Paolo Bonzini
2015-11-05 14:58             ` Paolo Bonzini
2015-11-05 18:56               ` Peter Maydell
2015-11-05 13:48     ` Laszlo Ersek
2015-11-05 15:52       ` Alex Bennée
2015-11-05 17:05         ` Laszlo Ersek
2015-11-05 17:09           ` Paolo Bonzini
2015-11-05 14:42     ` Gerd Hoffmann
2015-11-05 14:45       ` Peter Maydell
2015-11-05 14:58         ` Gerd Hoffmann
2015-11-05 15:11           ` Peter Maydell
2015-11-05 17:15             ` Laszlo Ersek
2015-11-05 18:13               ` Cornelia Huck
2015-11-05 18:51                 ` Laszlo Ersek
2015-11-06 16:34               ` Alex Bennée
2015-11-06 16:43               ` Peter Maydell

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=563B4237.6050709@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).