From: Vikram Garhwal <vikram.garhwal@amd.com>
To: Michal Orzel <michal.orzel@amd.com>
Cc: xen-devel@lists.xenproject.org, sstabellini@kernel.org, julien@xen.org
Subject: Re: [XEN][PATCH v10 09/20] xen/iommu: Move spin_lock from iommu_dt_device_is_assigned to caller
Date: Wed, 30 Aug 2023 10:20:59 -0700 [thread overview]
Message-ID: <ZO96e6stC178o3eo@amd.com> (raw)
In-Reply-To: <301f4799-ff57-c697-94ab-62eb39397c44@amd.com>
Hi Michal,
On Tue, Aug 29, 2023 at 10:05:55AM +0200, Michal Orzel wrote:
>
>
> On 25/08/2023 10:02, Vikram Garhwal wrote:
> > Rename iommu_dt_device_is_assigned() to iommu_dt_device_is_assigned_locked().
> >
> > Moving spin_lock to caller was done to prevent the concurrent access to
> > iommu_dt_device_is_assigned while doing add/remove/assign/deassign. Follow-up
> > patches in this series introduces node add/remove feature.
> >
> > Signed-off-by: Vikram Garhwal <vikram.garhwal@amd.com>
> >
> > ---
> > Changes from v9:
> > Make iommu_dt_device_is_assigned_locked() static and delete header.
> > Move dtdevs_lock before iommu_dt_device_is_assigned_locked().
> > Changes from v7:
> > Update commit message.
> > Add ASSERT().
> > ---
> > ---
> > xen/drivers/passthrough/device_tree.c | 16 ++++++++++++----
> > 1 file changed, 12 insertions(+), 4 deletions(-)
> >
> > diff --git a/xen/drivers/passthrough/device_tree.c b/xen/drivers/passthrough/device_tree.c
> > index 1c32d7b50c..5d84c07b50 100644
> > --- a/xen/drivers/passthrough/device_tree.c
> > +++ b/xen/drivers/passthrough/device_tree.c
> > @@ -83,16 +83,17 @@ fail:
> > return rc;
> > }
> >
> > -static bool_t iommu_dt_device_is_assigned(const struct dt_device_node *dev)
> > +static bool_t
> > +iommu_dt_device_is_assigned_locked(const struct dt_device_node *dev)
> This does not apply cleanly due to recent change from bool_t to bool. Please rebase for v11 (the function
> should then fit in a single line I think).
Fixed the changes here and made it one-line.
>
> > {
> > bool_t assigned = 0;
> >
> > + ASSERT(spin_is_locked(&dtdevs_lock));
> > +
> > if ( !dt_device_is_protected(dev) )
> > return 0;
> >
> > - spin_lock(&dtdevs_lock);
> > assigned = !list_empty(&dev->domain_list);
> > - spin_unlock(&dtdevs_lock);
> >
> > return assigned;
> > }
> > @@ -223,17 +224,24 @@ int iommu_do_dt_domctl(struct xen_domctl *domctl, struct domain *d,
> > if ( ret )
> > break;
> >
> > + spin_lock(&dtdevs_lock);
> Why is this lock placed here instead of ...
> > +
> > if ( domctl->cmd == XEN_DOMCTL_test_assign_device )
> > {
> > - if ( iommu_dt_device_is_assigned(dev) )
> > +
> ... here, right before iommu_dt_device_is_assigned_locked()?
Moved the lock before iommu_dt_device_is_assigned_locked().
> > + if ( iommu_dt_device_is_assigned_locked(dev) )
> > {
> > printk(XENLOG_G_ERR "%s already assigned.\n",
> > dt_node_full_name(dev));
> > ret = -EINVAL;
> > }
> > +
> > + spin_unlock(&dtdevs_lock);
> > break;
> > }
> >
> > + spin_unlock(&dtdevs_lock);
> You could then remove this one.
Ok!
>
> With the remarks addressed:
> Reviewed-by: Michal Orzel <michal.orzel@amd.com>
>
> ~Michal
next prev parent reply other threads:[~2023-08-30 17:21 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 [this message]
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
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=ZO96e6stC178o3eo@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.