From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-stable@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, alex.williamson@redhat.com,
Anthony Liguori <anthony@codemonkey.ws>,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PULL] pci,virtio
Date: Tue, 15 Jan 2013 18:32:37 +0200 [thread overview]
Message-ID: <20130115163237.GA7997@redhat.com> (raw)
In-Reply-To: <50F52AD2.6080400@suse.de>
On Tue, Jan 15, 2013 at 11:09:22AM +0100, Andreas Färber wrote:
> Am 13.01.2013 11:47, schrieb Michael S. Tsirkin:
> > The following changes since commit 8e4a424b305e29dc0e454f52df3b35577f342975:
> >
> > Revert "virtio-pci: replace byte swap hack" (2013-01-06 18:30:17 +0000)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_anthony
> >
> > for you to fetch changes up to feb9a2ab4b0260d8d680a7ffd25063dafc7ec628:
> >
> > pci-assign: Enable MSIX on device to match guest (2013-01-09 12:11:16 +0200)
> >
> > ----------------------------------------------------------------
> > pci,virtio
> >
> > This further optimizes MSIX handling in virtio-pci.
> > Also included is pci cleanup by Paolo, and pci device
> > assignment fix by Alex.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > ----------------------------------------------------------------
> > Alex Williamson (1):
> > pci-assign: Enable MSIX on device to match guest
> >
> > Michael S. Tsirkin (8):
> > virtio: don't waste irqfds on control vqs
> > msix: add api to access msix message
> > kvm: add stub for update msi route
> > virtio-pci: cache msix messages
>
> This broke the build with PowerKVM:
>
> LINK ppc64-softmmu/qemu-system-ppc64
> ../hw/virtio-pci.o: In function `kvm_virtio_pci_vq_vector_unmask':
> /home/andreas/QEMU/qemu/hw/virtio-pci.c:622: undefined reference to
> `kvm_irqchip_update_msi_route'
> collect2: error: ld returned 1 exit status
> make[1]: *** [qemu-system-ppc64] Fehler 1
> make: *** [subdir-ppc64-softmmu] Fehler 2
>
> Can you supply a fix? It's not obvious to me how.
>
> Thanks,
> Andreas
I'm not sure how to build this. Can you tell me pls?
Maybe the below helps?
kvm: add stub for kvm_irqchip_update_msi_route
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
diff --git a/kvm-all.c b/kvm-all.c
index fc0c6e7..bac67da 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -1182,6 +1182,11 @@ static int kvm_irqchip_assign_irqfd(KVMState *s, int fd, int virq, bool assign)
{
abort();
}
+
+int kvm_irqchip_update_msi_route(KVMState *s, int virq, MSIMessage msg)
+{
+ return -ENOSYS;
+}
#endif /* !KVM_CAP_IRQ_ROUTING */
int kvm_irqchip_add_irqfd_notifier(KVMState *s, EventNotifier *n, int virq)
next prev parent reply other threads:[~2013-01-15 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 10:47 [Qemu-devel] [PULL] pci,virtio Michael S. Tsirkin
2013-01-14 18:04 ` Anthony Liguori
2013-01-15 10:09 ` Andreas Färber
2013-01-15 16:32 ` Michael S. Tsirkin [this message]
2013-01-15 17:40 ` Andreas Färber
-- strict thread matches above, loose matches on Subject: below --
2012-12-26 10:36 Michael S. Tsirkin
2013-01-02 16:57 ` Anthony Liguori
2010-06-10 13:56 Michael S. Tsirkin
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=20130115163237.GA7997@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.