qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: David Woodhouse <dwmw2@infradead.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Paul Durrant <paul@xen.org>,
	Joao Martins <joao.m.martins@oracle.com>,
	Ankur Arora <ankur.a.arora@oracle.com>
Subject: Re: [RFC PATCH 08/21] xen_platform: exclude vfio-pci from the PCI platform unplug
Date: Mon, 5 Dec 2022 23:03:54 +0100	[thread overview]
Message-ID: <aad78d2e-3410-687d-f086-a8e872eccdec@linaro.org> (raw)
In-Reply-To: <20221205173137.607044-9-dwmw2@infradead.org>

On 5/12/22 18:31, David Woodhouse wrote:
> From: Joao Martins <joao.m.martins@oracle.com>
> 
> Such that PCI passthrough devices work for Xen emulated guests.
> 
> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> ---
>   hw/i386/xen/xen_platform.c | 18 +++++++++++++++---
>   1 file changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/hw/i386/xen/xen_platform.c b/hw/i386/xen/xen_platform.c
> index 710039851a..ae0a21f5bf 100644
> --- a/hw/i386/xen/xen_platform.c
> +++ b/hw/i386/xen/xen_platform.c
> @@ -109,12 +109,25 @@ static void log_writeb(PCIXenPlatformState *s, char val)
>   #define _UNPLUG_NVME_DISKS 3
>   #define UNPLUG_NVME_DISKS (1u << _UNPLUG_NVME_DISKS)
>   
> +static bool pci_device_is_passthrough(PCIDevice *d)
> +{
> +    if (!strcmp(d->name, "xen-pci-passthrough")) {

The 'QOM way' to do this check is:

        if (object_dynamic_cast(OBJECT(d), TYPE_XEN_PT_DEVICE)) {

> +        return true;
> +    }
> +
> +    if (xen_mode == XEN_EMULATE && !strcmp(d->name, "vfio-pci")) {

        if (xen_mode == XEN_EMULATE
            && object_dynamic_cast(OBJECT(d), TYPE_VFIO_PCI)) {

> +        return true;
> +    }
> +
> +    return false;
> +}


  reply	other threads:[~2022-12-05 22:04 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 17:31 [RFC PATCH 00/21] Xen HVM support under KVM David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 01/21] include: import xen public headers David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 02/21] i386/xen: Add xen-version machine property and init KVM Xen support David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 03/21] i386/kvm: handle Xen HVM cpuid leaves David Woodhouse
2022-12-05 21:58   ` Philippe Mathieu-Daudé
2022-12-06  0:18     ` David Woodhouse
2022-12-06  7:58       ` Philippe Mathieu-Daudé
2022-12-06  8:05         ` David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 04/21] xen-platform-pci: allow its creation with XEN_EMULATE mode David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 05/21] hw/xen_backend: refactor xen_be_init() David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 06/21] pc_piix: handle XEN_EMULATE backend init David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 07/21] xen-platform-pci: register xen-mmio as RAM for XEN_EMULATE David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 08/21] xen_platform: exclude vfio-pci from the PCI platform unplug David Woodhouse
2022-12-05 22:03   ` Philippe Mathieu-Daudé [this message]
2022-12-05 17:31 ` [RFC PATCH 09/21] pc_piix: allow xenfv machine with XEN_EMULATE David Woodhouse
2022-12-05 22:06   ` Philippe Mathieu-Daudé
2022-12-06  0:59     ` David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 10/21] i386/xen: handle guest hypercalls David Woodhouse
2022-12-05 22:11   ` Philippe Mathieu-Daudé
2022-12-06  1:10     ` David Woodhouse
2022-12-06  8:16       ` Philippe Mathieu-Daudé
2022-12-06  9:40         ` David Woodhouse
2022-12-06 11:07           ` Philippe Mathieu-Daudé
2022-12-06 11:30             ` David Woodhouse
2022-12-06 10:41         ` Alex Bennée
2022-12-05 17:31 ` [RFC PATCH 11/21] i386/xen: implement HYPERCALL_xen_version David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 12/21] i386/xen: set shared_info page David Woodhouse
2022-12-05 22:17   ` Philippe Mathieu-Daudé
2022-12-06  2:20     ` David Woodhouse
2022-12-06  8:26       ` Philippe Mathieu-Daudé
2022-12-06 10:00         ` Dr. David Alan Gilbert
2022-12-07 11:15           ` David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 13/21] i386/xen: implement HYPERVISOR_hvm_op David Woodhouse
2022-12-05 22:13   ` Philippe Mathieu-Daudé
2022-12-06  1:18     ` David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 14/21] i386/xen: implement HYPERVISOR_vcpu_op David Woodhouse
2022-12-05 22:18   ` Philippe Mathieu-Daudé
2022-12-05 17:31 ` [RFC PATCH 15/21] i386/xen: handle register_vcpu_info David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 16/21] i386/xen: handle register_vcpu_time_memory_area David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 17/21] i386/xen: handle register_runstate_memory_area David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 18/21] kvm/ioapic: mark gsi-2 used in ioapic routing init David Woodhouse
2022-12-05 22:25   ` Philippe Mathieu-Daudé
2022-12-06  1:21     ` David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 19/21] i386/xen: handle event channel upcall related hypercalls David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 20/21] i386/xen: implement HYPERVISOR_event_channel_op David Woodhouse
2022-12-05 17:31 ` [RFC PATCH 21/21] i386/xen: implement HYPERVISOR_sched_op David Woodhouse

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=aad78d2e-3410-687d-f086-a8e872eccdec@linaro.org \
    --to=philmd@linaro.org \
    --cc=ankur.a.arora@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=joao.m.martins@oracle.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).