qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
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, Daniel Gollub <gollub@b1-systems.de>
Subject: Re: [Qemu-devel] [PULL] pci,virtio
Date: Tue, 15 Jan 2013 18:40:21 +0100	[thread overview]
Message-ID: <50F59485.5000100@suse.de> (raw)
In-Reply-To: <20130115163237.GA7997@redhat.com>

Am 15.01.2013 17:32, schrieb Michael S. Tsirkin:
> On Tue, Jan 15, 2013 at 11:09:22AM +0100, Andreas Färber wrote:
>> Am 13.01.2013 11:47, schrieb Michael S. Tsirkin:
>>>       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.
> 
> I'm not sure how to build this. Can you tell me pls?

Ideally Daniel would set up your pci branch to build on the revived ppc
buildbot (and on s390, thinking of virtio).

When on a Linux/ppc host the KVM headers are detected, nothing special
needs to be configured to build that code. Cross-compilation should work
as well but obviously needs the right environment; same for a ppc chroot
with linux-user+binfmt.

> Maybe the below helps?
> 
> kvm: add stub for kvm_irqchip_update_msi_route
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

Tested-by: Andreas Färber <afaerber@suse.de>

Great, together with Blue's bswap patch this fixes the build for me.
Thanks for the quick response!

Regards,
Andreas

> 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)

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-01-15 17:40 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
2013-01-15 17:40     ` Andreas Färber [this message]
  -- 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=50F59485.5000100@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=gollub@b1-systems.de \
    --cc=mst@redhat.com \
    --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 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).