From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Alexander Graf <agraf@suse.de>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 0/2] RFC: powerpc-vfio: adding support
Date: Wed, 11 Jul 2012 12:25:39 +1000 [thread overview]
Message-ID: <4FFCE423.1020505@ozlabs.ru> (raw)
In-Reply-To: <1341939458.2428.107.camel@bling.home>
On 11/07/12 02:57, Alex Williamson wrote:
> On Tue, 2012-07-10 at 15:51 +1000, Alexey Kardashevskiy wrote:
>> The two patches in this set are supposed to add VFIO support for POWER.
>>
>> The first one adds one more step in the initalizaion sequence which I am not
>> sure is correct.
>>
>> The second patch adds actual VFIO support. It is not ready to submit but
>> ready to discuss. I would like to get rid of all #ifdef TARGET_PPC64 in patch #2
>> and I wonder if there is any plan to implement some generic EOI support code, etc.
>
> A generic EOI notifier is on my todo list, but I have no idea what it's
> going to look like. As you know, I've got an ioapic specific notifier
> in my tree, you add a spapr specific one. I welcome ideas on how to
> create something generic that has a chance of being accepted. Thanks,
So far the only platform specific call is xxxx_add_gsi_eoi_notifier. The
xxxx_remove_gsi_eoi_notifier only calls notifier_remove, you've got to fix yours
ioapic_remove_gsi_eoi_notifier() as it does too much :)
The only place for placing "add_eoi" callback I can see right now is QEMUMachine as there is no
unified machine interrupt controller - IOAPIC has its own type TYPE_IOAPIC_COMMON and XICS is not
even a SysBusDevice. And the callback is not specific for any kind of bus so it cannot go to PCIBus.
Does it sound reasonable?
>
> Alex
>
>> Alexey Kardashevskiy (2):
>> pseries pci: spapr_finalize_pci_setup introduced
>> vfio-powerpc: added VFIO support
>>
>> hw/ppc/Makefile.objs | 3 ++
>> hw/spapr.c | 7 ++++
>> hw/spapr.h | 4 +++
>> hw/spapr_iommu.c | 87 ++++++++++++++++++++++++++++++++++++++++++++++++++
>> hw/spapr_pci.c | 36 ++++++++++++++++++---
>> hw/spapr_pci.h | 4 +++
>> hw/vfio_pci.c | 76 +++++++++++++++++++++++++++++++++++++++++--
>> hw/vfio_pci.h | 2 ++
>> 8 files changed, 212 insertions(+), 7 deletions(-)
>>
>
>
>
--
Alexey
next prev parent reply other threads:[~2012-07-11 2:25 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 5:51 [Qemu-devel] [PATCH 0/2] RFC: powerpc-vfio: adding support Alexey Kardashevskiy
2012-07-10 5:51 ` [Qemu-devel] [PATCH 1/2] pseries pci: spapr_finalize_pci_setup introduced Alexey Kardashevskiy
2012-07-10 5:51 ` [Qemu-devel] [PATCH 2/2] vfio-powerpc: added VFIO support Alexey Kardashevskiy
2012-07-10 16:55 ` Alex Williamson
2012-07-10 21:32 ` Benjamin Herrenschmidt
2012-07-10 21:48 ` Alex Williamson
2012-07-10 21:53 ` Benjamin Herrenschmidt
2012-07-11 2:54 ` Alexey Kardashevskiy
2012-07-11 3:10 ` Benjamin Herrenschmidt
2012-07-12 3:11 ` Alex Williamson
2012-07-12 8:47 ` Alexey Kardashevskiy
2012-07-10 22:26 ` Scott Wood
2012-07-10 23:55 ` Alexey Kardashevskiy
2012-07-11 0:04 ` Benjamin Herrenschmidt
2012-07-11 0:17 ` Alexey Kardashevskiy
2012-07-11 0:26 ` Benjamin Herrenschmidt
2012-07-10 16:57 ` [Qemu-devel] [PATCH 0/2] RFC: powerpc-vfio: adding support Alex Williamson
2012-07-11 2:25 ` Alexey Kardashevskiy [this message]
2012-07-12 2:54 ` Alex Williamson
2012-07-12 4:16 ` Alexey Kardashevskiy
2012-07-12 4:31 ` Alex Williamson
2012-07-12 4:38 ` Alexey Kardashevskiy
2012-07-12 4:43 ` Alex Williamson
2012-07-12 4:58 ` Alexey Kardashevskiy
2012-07-12 5:29 ` Alex Williamson
2012-07-12 5:47 ` Alexey Kardashevskiy
2012-07-16 3:51 ` Alexey Kardashevskiy
2012-07-23 5:32 ` [Qemu-devel] [PATCH 0/3] vfio-pci: reworking end-of-interrupt Alexey Kardashevskiy
2012-07-23 5:32 ` [Qemu-devel] [PATCH 1/3] xics: added end-of-interrupt (EOI) handlers Alexey Kardashevskiy
2012-07-23 5:32 ` [Qemu-devel] [PATCH 2/3] ioapic: removed obsolete ioapic_remove_gsi_eoi_notifier Alexey Kardashevskiy
2012-07-23 5:32 ` [Qemu-devel] [PATCH 3/3] vfio-pci: rework of EOI Alexey Kardashevskiy
2012-07-12 8:52 ` [Qemu-devel] [PATCH] RFC: vfio-powerpc: added VFIO support (v2) Alexey Kardashevskiy
2012-07-12 20:54 ` [Qemu-devel] [Qemu-ppc] " Blue Swirl
2012-07-12 21:37 ` Alex Williamson
2012-07-13 5:24 ` Alexey Kardashevskiy
2012-07-13 14:33 ` Blue Swirl
2012-07-12 22:35 ` Scott Wood
2012-07-13 5:31 ` Alexey Kardashevskiy
2012-07-13 3:47 ` [Qemu-devel] " Alex Williamson
2012-07-13 5:03 ` Alexey Kardashevskiy
2012-07-13 7:26 ` [Qemu-devel] [PATCH] RFC: vfio-powerpc: added VFIO support (v3) Alexey Kardashevskiy
2012-07-13 14:38 ` Blue Swirl
2012-07-13 15:07 ` Alex Williamson
2012-07-14 2:34 ` Alexey Kardashevskiy
2012-07-16 14:21 ` Alex Williamson
2012-07-16 21:17 ` Alex Williamson
2012-07-17 7:53 ` Alexey Kardashevskiy
2012-07-17 14:11 ` Alex Williamson
2012-07-18 11:09 ` [Qemu-devel] [PATCH] vfio-powerpc: added VFIO support (v4) Alexey Kardashevskiy
2012-07-18 14:14 ` Alex Williamson
2012-07-19 4:01 ` Alexey Kardashevskiy
2012-07-19 4:04 ` [Qemu-devel] [PATCH] vfio-powerpc: added VFIO support (v5) 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=4FFCE423.1020505@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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 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).