From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-ppc@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Paolo Bonzini <pbonzini@redhat.com>,
Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] RFCv3 kvm irqfd: support msimessage to irq translation in PHB
Date: Sun, 30 Jun 2013 16:32:09 +1000 [thread overview]
Message-ID: <1372573929.18612.118.camel@pasglop> (raw)
In-Reply-To: <51CF82D6.4000106@ozlabs.ru>
On Sun, 2013-06-30 at 10:59 +1000, Alexey Kardashevskiy wrote:
> > 1) A PCI bus function to do the MSI -> virq mapping
> > 2) On x86 (and e500), this is implemented by calling kvm_irqchip_add_msi_route()
> > 3) On pseries, this just returns msi->data
> >
> > Perhaps (2) can just be the default PCI bus implementation to simplify things.
>
>
> hw/pci/pci.c does not have any kvm code yet and I would like not to be the
> first person who tries adding this there :)
> But ok, I'll do it.
Unless I'm confused (which is very possible) I seem to remember that there was
duplication of that MSI / KVM mapping between virtio-pci and vfio as well,
so it makes sense to move it to the PCI code.
Cheers,
Ben.
next prev parent reply other threads:[~2013-06-30 6:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 13:45 [Qemu-devel] [PATCH] RFCv3 kvm irqfd: support msimessage to irq translation in PHB Alexey Kardashevskiy
2013-06-29 14:06 ` Andreas Färber
2013-06-29 14:28 ` Anthony Liguori
2013-06-30 0:59 ` Alexey Kardashevskiy
2013-06-30 6:32 ` Benjamin Herrenschmidt [this message]
2013-06-30 7:09 ` [Qemu-devel] [Qemu-ppc] " Alexey Kardashevskiy
2013-06-30 14:23 ` [Qemu-devel] " Anthony Liguori
2013-06-30 7:37 ` Alexey Kardashevskiy
2013-06-30 14:20 ` Anthony Liguori
2013-08-19 8:10 ` Alexey Kardashevskiy
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=1372573929.18612.118.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=david@gibson.dropbear.id.au \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.