From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-ppc@nongnu.org, agraf@suse.de, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 1/2] vfio-pci: add flag to identify vfio pci device
Date: Fri, 27 Mar 2015 14:05:03 +1100 [thread overview]
Message-ID: <5514C8DF.3040507@ozlabs.ru> (raw)
In-Reply-To: <1427352132-1762-1-git-send-email-nikunj@linux.vnet.ibm.com>
On 03/26/2015 05:42 PM, Nikunj A Dadhania wrote:
> From PCIDevice there is no way to know if the device has a backing
> vfio device.
>
> sPAPR guests inherits the "ibm,loc-code" from the pci pass through
> device in hypervisor. This helps in identifying the device if there is
> any failures using this "ibm,loc-code" for RAS capabilities.
First, you can use object_dynamic_cast(OBJECT(obj), "vfio-pci") to know if
it is a VFIO device.
Second, rather than adding this flag here, I would fix the second patch to
check if PHB is of the TYPE_SPAPR_PCI_VFIO_HOST_BRIDGE type
("spapr-pci-vfio-host-bridge"), using the same QOM mechanism.
> CC: Alex Williamson <alex.williamson@redhat.com>
> CC: Alexander Graf <agraf@suse.de>
> Signed-off-by: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
> ---
> hw/vfio/pci.c | 2 ++
> include/hw/pci/pci.h | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 6b80539..95d666e 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -3483,6 +3483,7 @@ static void vfio_instance_finalize(Object *obj)
> VFIOPCIDevice *vdev = DO_UPCAST(VFIOPCIDevice, pdev, pci_dev);
> VFIOGroup *group = vdev->vbasedev.group;
>
> + pci_dev->is_vfio = false;
> vfio_unmap_bars(vdev);
> g_free(vdev->emulated_config_bits);
> g_free(vdev->rom);
> @@ -3542,6 +3543,7 @@ static void vfio_instance_init(Object *obj)
> PCIDevice *pci_dev = PCI_DEVICE(obj);
> VFIOPCIDevice *vdev = DO_UPCAST(VFIOPCIDevice, pdev, PCI_DEVICE(obj));
>
> + pci_dev->is_vfio = true;
> device_add_bootindex_property(obj, &vdev->bootindex,
> "bootindex", NULL,
> &pci_dev->qdev, NULL);
> diff --git a/include/hw/pci/pci.h b/include/hw/pci/pci.h
> index b97c295..0ddc830 100644
> --- a/include/hw/pci/pci.h
> +++ b/include/hw/pci/pci.h
> @@ -291,6 +291,8 @@ struct PCIDevice {
> /* SHPC */
> SHPCDevice *shpc;
>
> + bool is_vfio;
> +
> /* Location of option rom */
> char *romfile;
> bool has_rom;
>
--
Alexey
next prev parent reply other threads:[~2015-03-27 3:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 6:42 [Qemu-devel] [PATCH 1/2] vfio-pci: add flag to identify vfio pci device Nikunj A Dadhania
2015-03-26 6:42 ` [Qemu-devel] [PATCH 2/2] spapr: populate ibm,loc-code Nikunj A Dadhania
2015-03-27 3:16 ` Alexey Kardashevskiy
2015-03-27 4:29 ` Nikunj A Dadhania
2015-03-27 6:21 ` Nikunj A Dadhania
2015-03-27 6:38 ` Alexey Kardashevskiy
2015-03-27 3:28 ` David Gibson
2015-03-27 3:58 ` Alexey Kardashevskiy
2015-03-27 4:34 ` Nikunj A Dadhania
2015-03-27 4:57 ` David Gibson
2015-03-27 6:24 ` Nikunj A Dadhania
2015-03-27 3:05 ` Alexey Kardashevskiy [this message]
2015-03-31 18:17 ` [Qemu-devel] [PATCH 1/2] vfio-pci: add flag to identify vfio pci device Alex Williamson
2015-04-01 5:05 ` Nikunj A Dadhania
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=5514C8DF.3040507@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=nikunj@linux.vnet.ibm.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 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).