From: Jan Kiszka <jan.kiszka@siemens.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] buildsys: Move msi[x] and virtio-pci from Makefile.objs to Makefile.target
Date: Thu, 05 Jul 2012 16:50:22 +0200 [thread overview]
Message-ID: <4FF5A9AE.3060501@siemens.com> (raw)
In-Reply-To: <1341495312-1263-1-git-send-email-hdegoede@redhat.com>
On 2012-07-05 15:35, Hans de Goede wrote:
> Building non-kvm versions of qemu from qemu-kvm.git results in a linker error
> with undefined references to kvm_kernel_irqchip, expanded from the
> kvm_irqchip_in_kernel macro in kvm.h:
>
> This patch fixes this.
>
> Note maybe a better fix would be to drop the test for !defined NEED_CPU_H
> in the above macro ?
The best solution is to push device assignment upstream and celebrate
the funeral of qemu-kvm. ;)
Until then, qemu-kvm-1.1 (not master) just has to pick "kvm: Enable use
of kvm_irqchip_in_kernel in hwlib code" (bbf3b80401) from upstream.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2012-07-05 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 13:35 [PATCH] buildsys: Move msi[x] and virtio-pci from Makefile.objs to Makefile.target Hans de Goede
2012-07-05 14:50 ` Jan Kiszka [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=4FF5A9AE.3060501@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=hdegoede@redhat.com \
--cc=kvm@vger.kernel.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).