Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 17:15, Laszlo Ersek wrote: > --*-- > > I think we had the same discussion when Wei was working on SMBIOS 3.0 > for ARM. In > , > you asked > > "Is support for this all in the mainline kernel yet?" > > I di

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

Laszlo Ersek writes: > On 11/05/15 16:11, Peter Maydell wrote: >> On 5 November 2015 at 14:58, Gerd Hoffmann wrote: >>> On Do, 2015-11-05 at 14:45 +, Peter Maydell wrote: On 5 November 2015 at 14:42, Gerd Hoffmann wrote: > Chicken & egg issue in that case because airlied (linux ke

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 14:58, Paolo Bonzini wrote: > I think the main issue is that right now we have a very long freeze > period. It would be nice to know why (e.g. what kind of bugs are fixed? > are they release blockers only?) and whether a shorter development > period could also lead to a sho

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 11/05/15 19:13, Cornelia Huck wrote: > On Thu, 5 Nov 2015 18:15:04 +0100 > Laszlo Ersek wrote: > >> On 11/05/15 16:11, Peter Maydell wrote: >>> On 5 November 2015 at 14:58, Gerd Hoffmann wrote: On Do, 2015-11-05 at 14:45 +, Peter Maydell wrote: > On 5 November 2015 at 14:42, Gerd

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On Thu, 5 Nov 2015 18:15:04 +0100 Laszlo Ersek wrote: > On 11/05/15 16:11, Peter Maydell wrote: > > On 5 November 2015 at 14:58, Gerd Hoffmann wrote: > >> On Do, 2015-11-05 at 14:45 +, Peter Maydell wrote: > >>> On 5 November 2015 at 14:42, Gerd Hoffmann wrote: > Chicken & egg issue in

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 11/05/15 16:11, Peter Maydell wrote: > On 5 November 2015 at 14:58, Gerd Hoffmann wrote: >> On Do, 2015-11-05 at 14:45 +, Peter Maydell wrote: >>> On 5 November 2015 at 14:42, Gerd Hoffmann wrote: Chicken & egg issue in that case because airlied (linux kernel drm maintainer) aske

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 05/11/2015 18:05, Laszlo Ersek wrote: >> > Surely the kernel uapi includes is that textual format. Once stuff is >> > accepted into the master kernel tree there is your stable API. > What is uapi for? If it is for QEMU (the userspace process) to consume > the host kernel's services, then I agr

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 11/05/15 16:52, Alex Bennée wrote: > > Laszlo Ersek writes: > >> On 11/05/15 13:32, Peter Maydell wrote: >>> On 5 November 2015 at 12:13, Gerd Hoffmann wrote: > etc, because all the virtio_gpu definitions disappear from > include/standard-headers/linux/virtio_gpu.h. Updates

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

Laszlo Ersek writes: > On 11/05/15 13:32, Peter Maydell wrote: >> On 5 November 2015 at 12:13, Gerd Hoffmann wrote: etc, because all the virtio_gpu definitions disappear from include/standard-headers/linux/virtio_gpu.h. >>> >>> Updates not yet in mainline, they are sitting in drm-next

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 14:58, Gerd Hoffmann wrote: > On Do, 2015-11-05 at 14:45 +, Peter Maydell wrote: >> On 5 November 2015 at 14:42, Gerd Hoffmann wrote: >> > Chicken & egg issue in that case because airlied (linux kernel drm >> > maintainer) asked to have the qemu changes merged before tak

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 05/11/2015 15:52, Peter Maydell wrote: > ...also speaking as the person who does the wrangling of freezes and > rc candidate tags and so on, three times a year is quite enough :-) That's actually a good reason. On the other hand, we could look for a new policy that makes your work shorter du

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 05/11/2015 15:30, Peter Maydell wrote: > I suspect at least some of the other subsystems work the same way. I try not to have a for-this-release tree during hard freeze. :) > > The main issue is that shorter cycles may mean fewer and bigger pull > > requests. It also means more awareness of

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On Do, 2015-11-05 at 14:45 +, Peter Maydell wrote: > On 5 November 2015 at 14:42, Gerd Hoffmann wrote: > > Chicken & egg issue in that case because airlied (linux kernel drm > > maintainer) asked to have the qemu changes merged before taking the > > virtio-gpu pull request. So I had no other

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 14:30, Peter Maydell wrote: > On 5 November 2015 at 14:01, Paolo Bonzini wrote: >> On 05/11/2015 14:44, Peter Maydell wrote: >>> We used to have 3 month releases, but I think we found that these >>> were too short: If you have about a month hardfreeze and a month >>> softfre

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 14:42, Gerd Hoffmann wrote: > Chicken & egg issue in that case because airlied (linux kernel drm > maintainer) asked to have the qemu changes merged before taking the > virtio-gpu pull request. So I had no other chance than creating the > patches with not-yet upstream virtio

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On Do, 2015-11-05 at 12:32 +, Peter Maydell wrote: > On 5 November 2015 at 12:13, Gerd Hoffmann wrote: > >> etc, because all the virtio_gpu definitions disappear from > >> include/standard-headers/linux/virtio_gpu.h. > > > > Updates not yet in mainline, they are sitting in drm-next and should

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 14:01, Paolo Bonzini wrote: > On 05/11/2015 14:44, Peter Maydell wrote: >> We used to have 3 month releases, but I think we found that these >> were too short: If you have about a month hardfreeze and a month >> softfreeze then you only have a month of open feature developmen

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 05/11/2015 14:44, Peter Maydell wrote: > On 5 November 2015 at 13:23, Christian Borntraeger > wrote: >> Maybe we should try to aim for a 3 month cadence for QEMU to reduce the >> pain of missing soft/hard freeze. -> maybe a topic for the next QEMU >> summit? > > We used to have 3 month relea

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 11/05/15 13:32, Peter Maydell wrote: > On 5 November 2015 at 12:13, Gerd Hoffmann wrote: >>> etc, because all the virtio_gpu definitions disappear from >>> include/standard-headers/linux/virtio_gpu.h. >> >> Updates not yet in mainline, they are sitting in drm-next and should >> land during the

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

Am 05.11.2015 um 14:44 schrieb Peter Maydell: > On 5 November 2015 at 13:23, Christian Borntraeger > wrote: >> Maybe we should try to aim for a 3 month cadence for QEMU to reduce the >> pain of missing soft/hard freeze. -> maybe a topic for the next QEMU >> summit? > > We used to have 3 month rel

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 13:23, Christian Borntraeger wrote: > Maybe we should try to aim for a 3 month cadence for QEMU to reduce the > pain of missing soft/hard freeze. -> maybe a topic for the next QEMU > summit? We used to have 3 month releases, but I think we found that these were too short: If

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

Am 05.11.2015 um 13:32 schrieb Peter Maydell: > On 5 November 2015 at 12:13, Gerd Hoffmann wrote: >>> etc, because all the virtio_gpu definitions disappear from >>> include/standard-headers/linux/virtio_gpu.h. >> >> Updates not yet in mainline, they are sitting in drm-next and should >> land durin

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

On 5 November 2015 at 12:13, Gerd Hoffmann wrote: >> etc, because all the virtio_gpu definitions disappear from >> include/standard-headers/linux/virtio_gpu.h. > > Updates not yet in mainline, they are sitting in drm-next and should > land during the merge window (i.e. 4.4-rc1 should have them). >

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

Hi, > etc, because all the virtio_gpu definitions disappear from > include/standard-headers/linux/virtio_gpu.h. Updates not yet in mainline, they are sitting in drm-next and should land during the merge window (i.e. 4.4-rc1 should have them). I'd suggest to exclude virtio_gpu.h changes when up

Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

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

[Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next

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' CCaarch64-softmmu/hw/display/virtio-gpu.o