From: Vikram Garhwal <vikram.garhwal@amd.com>
To: xen-devel@lists.xenproject.org
Cc: michal.orzel@amd.com, sstabellini@kernel.org, julien@xen.org
Subject: Re: [XEN][PATCH v10 14/20] common/device_tree: Add rwlock for dt_host
Date: Mon, 28 Aug 2023 09:26:04 -0700 [thread overview]
Message-ID: <ZOzKnGiPPv9r8yzj@amd.com> (raw)
In-Reply-To: <20230825080222.14247-15-vikram.garhwal@amd.com>
On Fri, Aug 25, 2023 at 01:02:16AM -0700, Vikram Garhwal wrote:
> Dynamic programming ops will modify the dt_host and there might be other
> functions which are browsing the dt_host at the same time. To avoid the race
> conditions, adding rwlock for browsing the dt_host during runtime. dt_host
> writer will be added in the follow-up patch for device tree overlay
> functionalities."
>
> Reason behind adding rwlock instead of spinlock:
> For now, dynamic programming is the sole modifier of dt_host in Xen during
> run time. All other access functions like iommu_release_dt_device() are
> just reading the dt_host during run-time. So, there is a need to protect
> others from browsing the dt_host while dynamic programming is modifying
> it. rwlock is better suitable for this task as spinlock won't be able to
> differentiate between read and write access.
>
> Signed-off-by: Vikram Garhwal <vikram.garhwal@amd.com>
>
> ---
> Changes from v9:
> Update commit message and fix indentation.
> Add ASSERT() for iommu_deassign_dt_device() and iommu_remove_dt_device().
Copy-pasting Julien's comment here for keeping comments with latest version:
"We also need to add ASSERT(system_state <= SYS_STATE_active || check lock);
in iommu_add_dt_device() and iommu_assign_dt_device()."
I will make the changes in v11.
Regards,
Vikram
> Fix code styles.
> Remove rwlock_init in unflatten_device_tree() and do DEFINE_RWLOCK in
> device-tree.c
> Changes from v7:
> Keep one lock for dt_host instead of lock for each node under dt_host.
> ---
> ---
> xen/common/device_tree.c | 1 +
> xen/drivers/passthrough/device_tree.c | 24 ++++++++++++++++++++++--
> xen/include/xen/device_tree.h | 7 +++++++
> 3 files changed, 30 insertions(+), 2 deletions(-)
>
> diff --git a/xen/common/device_tree.c b/xen/common/device_tree.c
> index f38f51ec0b..b1c2952951 100644
> --- a/xen/common/device_tree.c
> +++ b/xen/common/device_tree.c
> @@ -31,6 +31,7 @@ dt_irq_xlate_func dt_irq_xlate;
> struct dt_device_node *dt_host;
> /* Interrupt controller node*/
> const struct dt_device_node *dt_interrupt_controller;
> +DEFINE_RWLOCK(dt_host_lock);
>
> /**
> * struct dt_alias_prop - Alias property in 'aliases' node
> diff --git a/xen/drivers/passthrough/device_tree.c b/xen/drivers/passthrough/device_tree.c
> index 3fad65fb69..b81dab5a48 100644
> --- a/xen/drivers/passthrough/device_tree.c
> +++ b/xen/drivers/passthrough/device_tree.c
> @@ -62,6 +62,8 @@ int iommu_deassign_dt_device(struct domain *d, struct dt_device_node *dev)
> const struct domain_iommu *hd = dom_iommu(d);
> int rc;
>
> + ASSERT(rw_is_locked(&dt_host_lock));
> +
> if ( !is_iommu_enabled(d) )
> return -EINVAL;
>
> @@ -114,6 +116,8 @@ int iommu_release_dt_devices(struct domain *d)
> if ( !is_iommu_enabled(d) )
> return 0;
>
> + read_lock(&dt_host_lock);
> +
> list_for_each_entry_safe(dev, _dev, &hd->dt_devices, domain_list)
> {
> rc = iommu_deassign_dt_device(d, dev);
> @@ -121,10 +125,14 @@ int iommu_release_dt_devices(struct domain *d)
> {
> dprintk(XENLOG_ERR, "Failed to deassign %s in domain %u\n",
> dt_node_full_name(dev), d->domain_id);
> + read_unlock(&dt_host_lock);
> +
> return rc;
> }
> }
>
> + read_unlock(&dt_host_lock);
> +
> return 0;
> }
>
> @@ -134,6 +142,8 @@ int iommu_remove_dt_device(struct dt_device_node *np)
> struct device *dev = dt_to_dev(np);
> int rc;
>
> + ASSERT(rw_is_locked(&dt_host_lock));
> +
> if ( !iommu_enabled )
> return 1;
>
> @@ -251,6 +261,8 @@ int iommu_do_dt_domctl(struct xen_domctl *domctl, struct domain *d,
> int ret;
> struct dt_device_node *dev;
>
> + read_lock(&dt_host_lock);
> +
> switch ( domctl->cmd )
> {
> case XEN_DOMCTL_assign_device:
> @@ -294,7 +306,10 @@ int iommu_do_dt_domctl(struct xen_domctl *domctl, struct domain *d,
> spin_unlock(&dtdevs_lock);
>
> if ( d == dom_io )
> - return -EINVAL;
> + {
> + ret = -EINVAL;
> + break;
> + }
>
> ret = iommu_add_dt_device(dev);
> if ( ret < 0 )
> @@ -332,7 +347,10 @@ int iommu_do_dt_domctl(struct xen_domctl *domctl, struct domain *d,
> break;
>
> if ( d == dom_io )
> - return -EINVAL;
> + {
> + ret = -EINVAL;
> + break;
> + }
>
> ret = iommu_deassign_dt_device(d, dev);
>
> @@ -347,5 +365,7 @@ int iommu_do_dt_domctl(struct xen_domctl *domctl, struct domain *d,
> break;
> }
>
> + read_unlock(&dt_host_lock);
> +
> return ret;
> }
> diff --git a/xen/include/xen/device_tree.h b/xen/include/xen/device_tree.h
> index 44d315c8ba..a262bba2ed 100644
> --- a/xen/include/xen/device_tree.h
> +++ b/xen/include/xen/device_tree.h
> @@ -18,6 +18,7 @@
> #include <xen/string.h>
> #include <xen/types.h>
> #include <xen/list.h>
> +#include <xen/rwlock.h>
>
> #define DEVICE_TREE_MAX_DEPTH 16
>
> @@ -218,6 +219,12 @@ extern struct dt_device_node *dt_host;
> */
> extern const struct dt_device_node *dt_interrupt_controller;
>
> +/*
> + * Lock that protects r/w updates to unflattened device tree i.e. dt_host during
> + * runtime. Lock may not be taken for boot only code.
> + */
> +extern rwlock_t dt_host_lock;
> +
> /**
> * Find the interrupt controller
> * For the moment we handle only one interrupt controller: the first
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2023-08-28 16:26 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 8:02 [XEN][PATCH v10 00/20] dynamic node programming using overlay dtbo Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 01/20] common/device_tree: handle memory allocation failure in __unflatten_device_tree() Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 02/20] common/device_tree.c: unflatten_device_tree() propagate errors Vikram Garhwal
2023-08-28 1:41 ` Henry Wang
2023-08-29 7:09 ` Michal Orzel
2023-08-29 22:24 ` Stefano Stabellini
2023-08-25 8:02 ` [XEN][PATCH v10 03/20] xen/arm/device: Remove __init from function type Vikram Garhwal
2023-08-28 1:53 ` Henry Wang
2023-08-28 16:21 ` Vikram Garhwal
2023-08-29 7:17 ` Michal Orzel
2023-08-30 17:16 ` Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 04/20] common/device_tree: Export __unflatten_device_tree() Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 05/20] xen/arm: Add CONFIG_OVERLAY_DTB Vikram Garhwal
2023-08-29 7:23 ` Michal Orzel
2023-08-30 17:16 ` Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 06/20] libfdt: Keep fdt functions after init for CONFIG_OVERLAY_DTB Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 07/20] libfdt: overlay: change overlay_get_target() Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 08/20] xen/device-tree: Add device_tree_find_node_by_path() to find nodes in device tree Vikram Garhwal
2023-08-28 1:59 ` Henry Wang
2023-08-29 7:41 ` Michal Orzel
2023-08-29 22:27 ` Stefano Stabellini
2023-08-25 8:02 ` [XEN][PATCH v10 09/20] xen/iommu: Move spin_lock from iommu_dt_device_is_assigned to caller Vikram Garhwal
2023-08-29 8:05 ` Michal Orzel
2023-08-30 17:20 ` Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 10/20] xen/iommu: protect iommu_add_dt_device() with dtdevs_lock Vikram Garhwal
2023-08-28 16:29 ` Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 11/20] xen/iommu: Introduce iommu_remove_dt_device() Vikram Garhwal
2023-08-29 8:23 ` Michal Orzel
2023-08-30 17:48 ` Vikram Garhwal
2023-08-31 0:35 ` Stefano Stabellini
2023-08-31 7:23 ` Michal Orzel
2023-08-31 7:32 ` Michal Orzel
2023-09-01 2:01 ` Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 12/20] xen/smmu: Add remove_device callback for smmu_iommu ops Vikram Garhwal
2023-08-29 8:51 ` Michal Orzel
2023-08-29 22:45 ` Stefano Stabellini
2023-08-30 9:17 ` Michal Orzel
2023-08-25 8:02 ` [XEN][PATCH v10 13/20] asm/smp.h: Fix circular dependency for device_tree.h and rwlock.h Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 14/20] common/device_tree: Add rwlock for dt_host Vikram Garhwal
2023-08-28 16:26 ` Vikram Garhwal [this message]
2023-08-29 9:27 ` Michal Orzel
2023-08-25 8:02 ` [XEN][PATCH v10 15/20] arm/asm/setup.h: Update struct map_range_data to add rangeset Vikram Garhwal
2023-08-29 12:16 ` Michal Orzel
2023-08-25 8:02 ` [XEN][PATCH v10 16/20] xen/arm: Implement device tree node removal functionalities Vikram Garhwal
2023-08-29 23:45 ` Stefano Stabellini
2023-08-25 8:02 ` [XEN][PATCH v10 17/20] xen/arm: Implement device tree node addition functionalities Vikram Garhwal
2023-08-29 23:45 ` Stefano Stabellini
2023-08-25 8:02 ` [XEN][PATCH v10 18/20] tools/libs/ctrl: Implement new xc interfaces for dt overlay Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 19/20] tools/libs/light: Implement new libxl functions for device tree overlay ops Vikram Garhwal
2023-08-25 8:02 ` [XEN][PATCH v10 20/20] tools/xl: Add new xl command overlay for device tree overlay support Vikram Garhwal
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=ZOzKnGiPPv9r8yzj@amd.com \
--to=vikram.garhwal@amd.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.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.