From: Jason Gunthorpe <jgg@nvidia.com>
To: Steven Sistare <steven.sistare@oracle.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
iommu@lists.linux.dev
Subject: Re: [PATCH V2 2/4] iommufd: Lock all objects
Date: Mon, 7 Oct 2024 13:43:44 -0300 [thread overview]
Message-ID: <20241007164344.GV1365916@nvidia.com> (raw)
In-Reply-To: <62312948-e733-408a-a42e-7235dcfcb0a6@oracle.com>
On Mon, Oct 07, 2024 at 12:18:37PM -0400, Steven Sistare wrote:
> Hi Jason,
> Any comment on this patch before I sent V3?
> There will be only a few changes in V3 in iommufd_take_all_iova_rwsem:
> * delete lockdep_on/off
> * replace
> down_write(&ioas->iopt.iova_rwsem);
> with
> down_write_nest_lock(&ioas->iopt.iova_rwsem,
> &ictx->ioas_creation_lock);
That seems Ok
Jason
next prev parent reply other threads:[~2024-10-07 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 13:53 [PATCH V2 0/4] iommufd live update Steve Sistare
2024-09-26 13:53 ` [PATCH V2 1/4] iommufd: Export do_update_pinned Steve Sistare
2024-10-02 17:34 ` Jason Gunthorpe
2024-09-26 13:53 ` [PATCH V2 2/4] iommufd: Lock all objects Steve Sistare
2024-10-07 16:18 ` Steven Sistare
2024-10-07 16:43 ` Jason Gunthorpe [this message]
2024-09-26 13:53 ` [PATCH V2 3/4] iommufd: Add IOMMU_IOAS_CHANGE_PROCESS Steve Sistare
2024-10-02 17:51 ` Jason Gunthorpe
2024-10-04 19:43 ` Steven Sistare
2024-10-04 20:20 ` Jason Gunthorpe
2024-09-26 13:53 ` [PATCH V2 4/4] iommufd: IOMMU_IOAS_CHANGE_PROCESS selftest Steve Sistare
2024-10-07 16:05 ` Steven Sistare
2024-10-07 16:56 ` Jason Gunthorpe
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=20241007164344.GV1365916@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=steven.sistare@oracle.com \
/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.