From: Jan Beulich <jbeulich@suse.com>
To: Stewart Hildebrand <stewart.hildebrand@amd.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Paul Durrant" <paul@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 4/5] [FUTURE] xen/arm: enable vPCI for domUs
Date: Tue, 31 Oct 2023 12:03:45 +0100 [thread overview]
Message-ID: <2f828bd2-e6f8-15b5-b226-33e2b33ebba8@suse.com> (raw)
In-Reply-To: <20231030235240.106998-5-stewart.hildebrand@amd.com>
On 31.10.2023 00:52, Stewart Hildebrand wrote:
> --- a/xen/drivers/passthrough/pci.c
> +++ b/xen/drivers/passthrough/pci.c
> @@ -1618,6 +1618,16 @@ int iommu_do_pci_domctl(
> bus = PCI_BUS(machine_sbdf);
> devfn = PCI_DEVFN(machine_sbdf);
>
> + if ( IS_ENABLED(CONFIG_ARM) &&
> + !is_hardware_domain(d) &&
> + !is_system_domain(d) &&
> + (!IS_ENABLED(CONFIG_HAS_VPCI_GUEST_SUPPORT) || !has_vpci(d)) )
I don't think you need the explicit ARM check; that's redundant with
checking !HAS_VPCI_GUEST_SUPPORT. It's also not really clear why you
need to check for the system domain here.
> + {
> + printk(XENLOG_G_WARNING "Cannot assign %pp to %pd: vPCI support not enabled\n",
> + &PCI_SBDF(seg, bus, devfn), d);
ret = -EPERM;
(or some other suitable error indicator)
Jan
> + break;
> + }
> +
> pcidevs_lock();
> ret = device_assigned(seg, bus, devfn);
> if ( domctl->cmd == XEN_DOMCTL_test_assign_device )
next prev parent reply other threads:[~2023-10-31 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 23:52 [PATCH v4 0/5] Kconfig for PCI passthrough on ARM Stewart Hildebrand
2023-10-30 23:52 ` [PATCH v4 1/5] xen/arm: pci: introduce PCI_PASSTHROUGH Kconfig option Stewart Hildebrand
2023-10-30 23:52 ` [PATCH v4 2/5] xen/vpci: move xen_domctl_createdomain vPCI flag to common Stewart Hildebrand
2023-10-31 10:56 ` Jan Beulich
2023-10-31 17:27 ` Stewart Hildebrand
2023-10-30 23:52 ` [PATCH v4 3/5] xen/arm: enable vPCI for dom0 Stewart Hildebrand
2023-10-30 23:52 ` [PATCH v4 4/5] [FUTURE] xen/arm: enable vPCI for domUs Stewart Hildebrand
2023-10-31 11:03 ` Jan Beulich [this message]
2023-10-31 13:17 ` Julien Grall
2023-10-31 14:15 ` Stewart Hildebrand
2023-10-31 16:17 ` Jan Beulich
2023-10-30 23:52 ` [PATCH v4 5/5] [FUTURE] tools/arm: " Stewart Hildebrand
2023-11-01 9:25 ` [PATCH v4 0/5] Kconfig for PCI passthrough on ARM Christian Lindig
2023-11-02 17:53 ` Stewart Hildebrand
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=2f828bd2-e6f8-15b5-b226-33e2b33ebba8@suse.com \
--to=jbeulich@suse.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stewart.hildebrand@amd.com \
--cc=xen-devel@lists.xenproject.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.