From: Jason Gunthorpe <jgg@ziepe.ca>
To: Junxian Huang <huangjunxian6@hisilicon.com>
Cc: Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 for-next 2/2] RDMA/hns: Disassociate mmap pages for all uctx when HW is being reset
Date: Fri, 20 Sep 2024 09:47:57 -0300 [thread overview]
Message-ID: <Zu1u/aiOAooVUeq2@ziepe.ca> (raw)
In-Reply-To: <595ec9f3-c3cd-66b3-c523-452f88e079ac@hisilicon.com>
On Fri, Sep 20, 2024 at 05:18:14PM +0800, Junxian Huang wrote:
> >> diff --git a/drivers/infiniband/hw/hns/hns_roce_main.c b/drivers/infiniband/hw/hns/hns_roce_main.c
> >> index 4cb0af733587..49315f39361d 100644
> >> --- a/drivers/infiniband/hw/hns/hns_roce_main.c
> >> +++ b/drivers/infiniband/hw/hns/hns_roce_main.c
> >> @@ -466,6 +466,11 @@ static int hns_roce_mmap(struct ib_ucontext *uctx, struct vm_area_struct *vma)
> >> pgprot_t prot;
> >> int ret;
> >>
> >> + if (hr_dev->dis_db) {
> >
> > How do you clear dis_db after calling to hns_roce_hw_v2_reset_notify_down()? Does it have any locking protection?
> >
>
> Sorry for the late response, I just came back from vacation.
>
> After calling hns_roce_hw_v2_reset_notify_down(), we will call ib_unregister_device()
> and destory all HW resources eventually, so there is no need to clear dis_db.
Why can't you do the unregister device sooner then and avoid all this
special stuff?
I assumed you'd bring the same device back after completing the reset??
Jason
next prev parent reply other threads:[~2024-09-20 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 12:29 [PATCH v5 for-next 0/2] RDMA: Provide an API for drivers to disassociate mmap pages Junxian Huang
2024-09-13 12:29 ` [PATCH v5 for-next 1/2] RDMA/core: Provide rdma_user_mmap_disassociate() " Junxian Huang
2024-09-13 12:29 ` [PATCH v5 for-next 2/2] RDMA/hns: Disassociate mmap pages for all uctx when HW is being reset Junxian Huang
2024-09-16 9:13 ` Leon Romanovsky
2024-09-20 9:18 ` Junxian Huang
2024-09-20 12:47 ` Jason Gunthorpe [this message]
2024-09-23 6:17 ` Junxian Huang
2024-09-23 9:02 ` Leon Romanovsky
2024-09-23 14:15 ` Junxian Huang
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=Zu1u/aiOAooVUeq2@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=huangjunxian6@hisilicon.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox