From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Rahul.Singh@arm.com, Bertrand.Marquis@arm.com,
julien.grall@arm.com, jbeulich@suse.com, roger.pau@citrix.com,
sstabellini@kernel.org, xen-devel@lists.xenproject.org
Cc: iwj@xenproject.org, wl@xen.org,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: [PATCH 08/10] vpci/arm: Allow updating BAR's header for non-ECAM bridges
Date: Mon, 9 Nov 2020 14:50:29 +0200 [thread overview]
Message-ID: <20201109125031.26409-9-andr2000@gmail.com> (raw)
In-Reply-To: <20201109125031.26409-1-andr2000@gmail.com>
From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Non-ECAM host bridges in hwdom go directly to PCI config space,
not through vpci (they use their specific method for accessing PCI
configuration, e.g. dedicated registers etc.). Thus hwdom's vpci BARs are
never updated via vPCI MMIO handlers, so implement a dedicated method
for a PCI host bridge, so it has a chance to update the initial state of
the device BARs.
Note, we rely on the fact that control/hardware domain will not update
physical BAR locations for the given devices.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
---
xen/arch/arm/pci/pci-host-common.c | 13 +++++++++++++
| 9 ++++++++-
xen/include/asm-arm/pci.h | 8 ++++++++
3 files changed, 29 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/pci/pci-host-common.c b/xen/arch/arm/pci/pci-host-common.c
index b6c4d7b636b1..5f4239afa41f 100644
--- a/xen/arch/arm/pci/pci-host-common.c
+++ b/xen/arch/arm/pci/pci-host-common.c
@@ -250,6 +250,19 @@ int pci_host_bridge_update_mappings(struct domain *d)
return pci_host_iterate_bridges(d, pci_host_bridge_update_mapping);
}
+void pci_host_bridge_update_bar_header(const struct pci_dev *pdev,
+ struct vpci_header *header)
+{
+ struct pci_host_bridge *bridge;
+
+ bridge = pci_find_host_bridge(pdev->seg, pdev->bus);
+ if ( unlikely(!bridge) )
+ return;
+
+ if ( bridge->ops->update_bar_header )
+ bridge->ops->update_bar_header(pdev, header);
+}
+
/*
* Local variables:
* mode: C
--git a/xen/drivers/vpci/header.c b/xen/drivers/vpci/header.c
index 7dc7c70e24f2..1f326c894d16 100644
--- a/xen/drivers/vpci/header.c
+++ b/xen/drivers/vpci/header.c
@@ -77,7 +77,14 @@ static struct vpci_header *get_vpci_header(struct domain *d,
if ( !is_hardware_domain(d) )
{
struct vpci_header *hwdom_header = get_hwdom_vpci_header(pdev);
-
+#ifdef CONFIG_ARM
+ /*
+ * Non-ECAM host bridges in hwdom go directly to PCI
+ * config space, not through vpci. Thus hwdom's vpci BARs are
+ * never updated.
+ */
+ pci_host_bridge_update_bar_header(pdev, hwdom_header);
+#endif
/* Make a copy of the hwdom's BARs as the initial state for vBARs. */
memcpy(header, hwdom_header, sizeof(*header));
}
diff --git a/xen/include/asm-arm/pci.h b/xen/include/asm-arm/pci.h
index d94e8a6628de..723b2a99b6e1 100644
--- a/xen/include/asm-arm/pci.h
+++ b/xen/include/asm-arm/pci.h
@@ -60,6 +60,9 @@ struct pci_config_window {
/* Forward declaration as pci_host_bridge and pci_ops depend on each other. */
struct pci_host_bridge;
+struct pci_dev;
+struct vpci_header;
+
struct pci_ops {
int (*read)(struct pci_host_bridge *bridge,
uint32_t sbdf, int where, int size, u32 *val);
@@ -69,6 +72,8 @@ struct pci_ops {
int (*register_mmio_handler)(struct domain *d,
struct pci_host_bridge *bridge,
const struct mmio_handler_ops *ops);
+ void (*update_bar_header)(const struct pci_dev *pdev,
+ struct vpci_header *header);
};
/*
@@ -110,6 +115,9 @@ int pci_host_iterate_bridges(struct domain *d,
int (*clb)(struct domain *d,
struct pci_host_bridge *bridge));
int pci_host_bridge_update_mappings(struct domain *d);
+void pci_host_bridge_update_bar_header(const struct pci_dev *pdev,
+ struct vpci_header *header);
+
#else /*!CONFIG_ARM_PCI*/
struct arch_pci_dev { };
static inline void pci_init(void) { }
--
2.17.1
next prev parent reply other threads:[~2020-11-09 12:51 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 12:50 [PATCH 00/10] [RFC] ARM PCI passthrough configuration and vPCI Oleksandr Andrushchenko
2020-11-09 12:50 ` [PATCH 01/10] pci/pvh: Allow PCI toolstack code run with PVH domains on ARM Oleksandr Andrushchenko
2020-11-11 12:31 ` [SUSPECTED SPAM][PATCH " Roger Pau Monné
2020-11-11 13:10 ` Oleksandr Andrushchenko
2020-11-11 13:55 ` Roger Pau Monné
2020-11-11 14:12 ` Oleksandr Andrushchenko
2020-11-11 14:21 ` Roger Pau Monné
2020-11-09 12:50 ` [PATCH 02/10] arm/pci: Maintain PCI assignable list Oleksandr Andrushchenko
2020-11-11 13:53 ` Roger Pau Monné
2020-11-11 14:38 ` Oleksandr Andrushchenko
2020-11-11 15:03 ` Roger Pau Monné
2020-11-11 15:13 ` Oleksandr Andrushchenko
2020-11-11 15:25 ` Jan Beulich
2020-11-11 15:28 ` Oleksandr Andrushchenko
2020-11-11 14:54 ` Jan Beulich
2020-11-12 12:53 ` Oleksandr Andrushchenko
2020-11-09 12:50 ` [PATCH 03/10] xen/arm: Setup MMIO range trap handlers for hardware domain Oleksandr Andrushchenko
2020-11-11 14:39 ` Roger Pau Monné
2020-11-11 14:42 ` Oleksandr Andrushchenko
2020-11-09 12:50 ` [PATCH 04/10] [WORKAROUND] xen/arm: Update hwdom's p2m to trap ECAM space Oleksandr Andrushchenko
2020-11-11 14:44 ` Roger Pau Monné
2020-11-12 12:54 ` Oleksandr Andrushchenko
2020-11-09 12:50 ` [PATCH 05/10] xen/arm: Process pending vPCI map/unmap operations Oleksandr Andrushchenko
2020-11-09 12:50 ` [PATCH 06/10] vpci: Make every domain handle its own BARs Oleksandr Andrushchenko
2020-11-12 9:40 ` Roger Pau Monné
2020-11-12 13:16 ` Oleksandr Andrushchenko
2020-11-12 14:46 ` Roger Pau Monné
2020-11-13 6:32 ` Oleksandr Andrushchenko
2020-11-13 6:48 ` Oleksandr Andrushchenko
2020-11-13 10:25 ` Jan Beulich
2020-11-13 10:36 ` Julien Grall
2020-11-13 10:53 ` Jan Beulich
2020-11-13 11:06 ` Julien Grall
2020-11-13 11:26 ` Jan Beulich
2020-11-13 11:53 ` Julien Grall
2020-11-13 10:46 ` Oleksandr Andrushchenko
2020-11-13 10:50 ` Jan Beulich
2020-11-13 11:02 ` Oleksandr Andrushchenko
2020-11-13 11:35 ` Jan Beulich
2020-11-13 12:41 ` Oleksandr Andrushchenko
2020-11-13 14:23 ` Jan Beulich
2020-11-13 14:32 ` Oleksandr Andrushchenko
2020-11-13 14:38 ` Jan Beulich
2020-11-13 14:44 ` Oleksandr Andrushchenko
2020-11-13 14:51 ` Jan Beulich
2020-11-13 14:52 ` Oleksandr Andrushchenko
2020-12-04 14:38 ` Oleksandr Andrushchenko
2020-12-07 8:48 ` Jan Beulich
2020-12-07 9:11 ` Oleksandr Andrushchenko
2020-12-07 9:28 ` Jan Beulich
2020-12-07 9:37 ` Oleksandr Andrushchenko
2020-12-07 9:50 ` Jan Beulich
2020-11-09 12:50 ` [PATCH 07/10] xen/arm: Do not hardcode phycial PCI device addresses Oleksandr Andrushchenko
2020-11-09 12:50 ` Oleksandr Andrushchenko [this message]
2020-11-12 9:56 ` [PATCH 08/10] vpci/arm: Allow updating BAR's header for non-ECAM bridges Roger Pau Monné
2020-11-13 6:46 ` Oleksandr Andrushchenko
2020-11-13 10:29 ` Jan Beulich
2020-11-13 10:39 ` Oleksandr Andrushchenko
2020-11-13 10:47 ` Jan Beulich
2020-11-13 10:55 ` Oleksandr Andrushchenko
2020-11-09 12:50 ` [PATCH 09/10] vpci/rcar: Implement vPCI.update_bar_header callback Oleksandr Andrushchenko
2020-11-12 10:00 ` Roger Pau Monné
2020-11-13 6:50 ` Oleksandr Andrushchenko
2020-11-09 12:50 ` [PATCH 10/10] [HACK] vpci/rcar: Make vPCI know DomD is hardware domain Oleksandr Andrushchenko
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=20201109125031.26409-9-andr2000@gmail.com \
--to=andr2000@gmail.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Rahul.Singh@arm.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--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.