All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <gregory.haskins@gmail.com>
To: kvm@vger.kernel.org
Cc: Mark McLoughlin <markmc@redhat.com>,
	Weidong Han <weidong.han@intel.com>, Avi Kivity <avi@redhat.com>,
	Gleb Natapov <gleb@redhat.com>
Subject: Build breakage between kvm-userspace.git HEAD and 2.6.29-rc8
Date: Fri, 13 Mar 2009 11:36:23 -0400	[thread overview]
Message-ID: <49BA7D77.1010003@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

Hi kvm-devs,
  Been away from the kvm scene for a while...hope everyone is well.

FYI: There are a few build breakages between kvm-userspace.git HEAD
(f29d402ab885d30bfa7350378cff911c9c17a226) when you compile against
Linus' linux-2.6.git HEAD
(v2.6.29-rc8-041b62374c7fedc11a8a1eeda2868612d3d1436c)

I am not sure if this is a supported configuration (e.g. perhaps you
only support building kvm-userspace HEAD against Avi's kernel tree?). 
But in case this was unintentional, read on...

First error:

libkvm.c:702: error: ‘struct kvm_irq_level’ has no member named ‘status’
make[1]: *** [libkvm.o] Error 1

Which is attributable to:

commit ea1b668e7684dc43e9d198ba0b25fe47a0b2acd2
Author: Gleb Natapov <gleb@redhat.com>
Date:   Wed Feb 4 17:30:01 2009 +0200

    kvm: qemu: handle IRQ status injection in userspace
   
Reverting this patch does allow the build to get past this error.  Then
I hit the next one:

device-assignment.o: In function `deassign_device':
/home/ghaskins/sandbox/git/fabric/kvm-userspace/qemu/hw/device-assignment.c:562:
undefined reference to `kvm_deassign_pci_device'

Reverting:

commit 1435f18213edee9fabf936f5d6be70054f1f2bd1
Author: Weidong Han <weidong.han@intel.com>
Date:   Wed Feb 18 14:33:41 2009 +0800

    kvm: qemu: fix hot remove assigned device
   
 Followed by:

commit 71ae34caaa961330f53f40090cd180a74fcda5fc
Author: Weidong Han <weidong.han@intel.com>
Date:   Wed Feb 18 14:28:30 2009 +0800

    kvm: qemu: deassign device from guest
   
Does fix the build.  I realize reversion is probably not the desirable
long term solution, but at least it points to the proper places that
need some backwards-compat love ;)

Regards,
-Greg







[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

             reply	other threads:[~2009-03-13 15:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 15:36 Gregory Haskins [this message]
2009-03-15  9:23 ` Build breakage between kvm-userspace.git HEAD and 2.6.29-rc8 Avi Kivity
2009-03-15 10:19   ` Gleb Natapov
2009-03-15 10:43     ` Avi Kivity
2009-03-15 10:42       ` Gleb Natapov
2009-03-15 12:19         ` Avi Kivity
2009-03-16  9:25 ` Han, Weidong
2009-03-16  9:48   ` Avi Kivity
2009-03-17  1:02     ` Han, Weidong
2009-03-17  9:36       ` Avi Kivity

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=49BA7D77.1010003@gmail.com \
    --to=gregory.haskins@gmail.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=weidong.han@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.