From: Eric Auger <eric.auger@linaro.org>
To: Alexander Graf <agraf@suse.de>,
eric.auger@st.com, christoffer.dall@linaro.org,
qemu-devel@nongnu.org, a.rigo@virtualopensystems.com,
kim.phillips@freescale.com, marc.zyngier@arm.com,
manish.jaggi@caviumnetworks.com, joel.schopp@amd.com,
peter.maydell@linaro.org, pbonzini@redhat.com, afaerber@suse.de
Cc: patches@linaro.org, will.deacon@arm.com,
stuart.yoder@freescale.com, Bharat.Bhushan@freescale.com,
alex.williamson@redhat.com, a.motakis@virtualopensystems.com,
kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] [PATCH v6 11/16] hw/arm/dyn_sysbus_devtree: enable vfio-calxeda-xgmac dynamic instantiation
Date: Thu, 11 Sep 2014 16:20:09 +0200 [thread overview]
Message-ID: <5411AF99.5060608@linaro.org> (raw)
In-Reply-To: <54104E5A.5060505@suse.de>
On 09/10/2014 03:12 PM, Alexander Graf wrote:
>
>
> On 09.09.14 09:31, Eric Auger wrote:
>> vfio-calxeda-xgmac now can be instantiated using the -device option
>>
>> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>>
>> ---
>>
>> v2 -> v3:
>> - correct bug of reg_attr[2*i] in vfio_fdt_add_device_node
>> - fix a bug related to compat_str_len computed on original compat
>> instead of corrected compat
>> - wrap_vfio_fdt_add_node take a node creation function: this function
>> needs to be specialized for each VFIO device. wrap function must be
>> called in sysbus_device_create_devtree
>> ---
>> hw/arm/dyn_sysbus_devtree.c | 141 ++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 141 insertions(+)
>>
>> diff --git a/hw/arm/dyn_sysbus_devtree.c b/hw/arm/dyn_sysbus_devtree.c
>> index 61e5b5f..3ef9430 100644
>> --- a/hw/arm/dyn_sysbus_devtree.c
>> +++ b/hw/arm/dyn_sysbus_devtree.c
>> @@ -20,6 +20,141 @@
>> #include "hw/arm/dyn_sysbus_devtree.h"
>> #include "qemu/error-report.h"
>> #include "sysemu/device_tree.h"
>> +#include "hw/vfio/vfio-platform.h"
>> +#include "hw/vfio/vfio-calxeda-xgmac.h"
>> +
>> +typedef void (*vfio_fdt_add_device_node_t)(SysBusDevice *sbdev, void *opaque);
>> +
>> +static char *format_compat(char * compat)
>> +{
>> + char *str_ptr, *corrected_compat;
>> + /*
>> + * process compatibility property string passed by end-user
>> + * replaces / by , and ; by NUL character
>> + */
>> + corrected_compat = g_strdup(compat);
>> +
>> + str_ptr = corrected_compat;
>> + while ((str_ptr = strchr(str_ptr, '/')) != NULL) {
>> + *str_ptr = ',';
>> + }
>> +
>> + /* substitute ";" with the NUL char */
>> + str_ptr = corrected_compat;
>> + while ((str_ptr = strchr(str_ptr, ';')) != NULL) {
>> + *str_ptr = '\0';
>> + }
>> +
>> + /*
>> + * corrected compat includes a "\0" before or at the same location
>> + * as compat's one
>> + */
>> + return corrected_compat;
>> +}
>> +
>> +static void wrap_vfio_fdt_add_node(SysBusDevice *sbdev, void *opaque,
>> + vfio_fdt_add_device_node_t add_node_fn)
>> +{
>> + PlatformDevtreeData *data = opaque;
>> + VFIOPlatformDevice *vdev = VFIO_PLATFORM_DEVICE(sbdev);
>> + VFIODevice *vbasedev = &vdev->vbasedev;
>> + gchar irq_number_prop[8];
>> + Object *obj = OBJECT(sbdev);
>> + char *corrected_compat;
>> + uint64_t irq_number;
>> + int corrected_compat_str_len, i;
>> +
>> + corrected_compat = format_compat(vdev->compat);
>> + corrected_compat_str_len = strlen(corrected_compat) + 1;
>> + /* we copy the corrected_compat string + its "\0" */
>> + snprintf(vdev->compat, corrected_compat_str_len, "%s", corrected_compat);
>> + g_free(corrected_compat);
>> +
>> + add_node_fn(sbdev, opaque);
>> +
>> + for (i = 0; i < vbasedev->num_irqs; i++) {
>> + snprintf(irq_number_prop, sizeof(irq_number_prop), "irq[%d]", i);
>> + irq_number = object_property_get_int(obj, irq_number_prop, NULL)
>> + + data->irq_start;
>> + /*
>> + * for setting irqfd up we must provide the virtual IRQ number
>> + * which is the sum of irq_start and actual platform bus irq
>> + * index. At realize point we do not have this info.
>> + */
>> + vfio_start_irq_injection(sbdev, i, irq_number);
>
> Does this really have anything to do with fdt?
No it doesn't, I aknowledge ;-)
Also, don't we have
> notifiers that call IRQ holders when an IRQ gets connected?
Do we? I was not able to identify such modality. the notifier would be
triggered in qemu_allocate_irq right?
That would
> probably be the cleaner approach here.
If it is and if the functionality does not exist yet, I can it, sure.
Besides I do not get how VFIO-PCI does handle the problem of late irq
binding. If someone can share some knowledge on this, it would be much
appreciated.
Best Regards
Eric
>
>
> Alex
>
next prev parent reply other threads:[~2014-09-11 14:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 7:31 [Qemu-devel] [PATCH v6 00/16] KVM platform device passthrough Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 01/16] vfio: move hw/misc/vfio.c to hw/vfio/pci.c Move vfio.h into include/hw/vfio Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 02/16] hw/vfio/pci: Rename VFIODevice into VFIOPCIDevice Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 03/16] hw/vfio/pci: introduce VFIODevice Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 04/16] hw/vfio/pci: Introduce VFIORegion Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 05/16] hw/vfio/pci: split vfio_get_device Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 06/16] hw/vfio/pci: rename group_list into vfio_group_list Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 07/16] hw/vfio/pci: use name field in format strings Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 08/16] hw/vfio: create common module Eric Auger
2014-09-10 13:09 ` Alexander Graf
2014-09-11 12:11 ` Eric Auger
2014-09-11 12:13 ` Alexander Graf
2014-09-11 14:21 ` Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 09/16] hw/vfio/platform: add vfio-platform support Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 10/16] hw/vfio: calxeda xgmac device Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 11/16] hw/arm/dyn_sysbus_devtree: enable vfio-calxeda-xgmac dynamic instantiation Eric Auger
2014-09-10 13:12 ` Alexander Graf
2014-09-11 14:20 ` Eric Auger [this message]
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 12/16] vfio/platform: add fake injection modality Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 13/16] hw/vfio/platform: Add irqfd support Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 14/16] linux-headers: Update KVM headers from linux-next tag ToBeFilled Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 15/16] VFIO: COMMON: vfio_kvm_device_fd moved in the common header Eric Auger
2014-09-09 7:31 ` [Qemu-devel] [PATCH v6 16/16] VFIO: PLATFORM: add forwarded irq support Eric Auger
2014-09-11 22:14 ` [Qemu-devel] [PATCH v6 00/16] KVM platform device passthrough Alex Williamson
2014-09-11 22:23 ` Christoffer Dall
2014-09-11 22:51 ` Alex Williamson
2014-09-11 23:05 ` Christoffer Dall
2014-09-15 22:01 ` Eric Auger
2014-09-16 20:51 ` Alex Williamson
2014-09-16 21:19 ` Eric Auger
2014-09-16 21:23 ` Alex Williamson
2014-09-19 0:29 ` Eric Auger
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=5411AF99.5060608@linaro.org \
--to=eric.auger@linaro.org \
--cc=Bharat.Bhushan@freescale.com \
--cc=a.motakis@virtualopensystems.com \
--cc=a.rigo@virtualopensystems.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@st.com \
--cc=joel.schopp@amd.com \
--cc=kim.phillips@freescale.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=manish.jaggi@caviumnetworks.com \
--cc=marc.zyngier@arm.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stuart.yoder@freescale.com \
--cc=will.deacon@arm.com \
/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).