From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Artemy Kovalyov <artemyko@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Yishai Hadas <yishaih@mellanox.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH rdma-rc 3/3] IB/core: Fix ODP with IB_ACCESS_HUGETLB handling
Date: Wed, 8 Jan 2020 13:56:58 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2001081352560.23971@ramsan.of.borg> (raw)
In-Reply-To: <20191219134646.413164-4-leon@kernel.org>
Hi Leon,
On Thu, 19 Dec 2019, Leon Romanovsky wrote:
> From: Yishai Hadas <yishaih@mellanox.com>
>
> As VMAs for a given range might not be available as part of the
> registration phase in ODP, IB_ACCESS_HUGETLB/page_shift must be checked
> as part of the page fault flow.
>
> If the application didn't mmap the backed memory with huge pages or
> released part of that hugepage area, an error will be set as part of the
> page fault flow once be detected.
>
> Fixes: 0008b84ea9af ("IB/umem: Add support to huge ODP")
> Signed-off-by: Yishai Hadas <yishaih@mellanox.com>
> Reviewed-by: Artemy Kovalyov <artemyko@mellanox.com>
> Reviewed-by: Aviad Yehezkel <aviadye@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
Thanks for your patch!
> --- a/drivers/infiniband/core/umem_odp.c
> +++ b/drivers/infiniband/core/umem_odp.c
> @@ -241,22 +241,10 @@ struct ib_umem_odp *ib_umem_odp_get(struct ib_udata *udata, unsigned long addr,
> umem_odp->umem.owning_mm = mm = current->mm;
> umem_odp->notifier.ops = ops;
>
> - umem_odp->page_shift = PAGE_SHIFT;
> - if (access & IB_ACCESS_HUGETLB) {
> - struct vm_area_struct *vma;
> - struct hstate *h;
> -
> - down_read(&mm->mmap_sem);
> - vma = find_vma(mm, ib_umem_start(umem_odp));
> - if (!vma || !is_vm_hugetlb_page(vma)) {
> - up_read(&mm->mmap_sem);
> - ret = -EINVAL;
> - goto err_free;
> - }
> - h = hstate_vma(vma);
> - umem_odp->page_shift = huge_page_shift(h);
> - up_read(&mm->mmap_sem);
> - }
> + if (access & IB_ACCESS_HUGETLB)
> + umem_odp->page_shift = HPAGE_SHIFT;
> + else
> + umem_odp->page_shift = PAGE_SHIFT;
>
> umem_odp->tgid = get_task_pid(current->group_leader, PIDTYPE_PID);
> ret = ib_init_umem_odp(umem_odp, ops);
noreply@ellerman.id.au reports for linux-next/m68k-allmodconfig/m68k:
drivers/infiniband/core/umem_odp.c:245:26: error: 'HPAGE_SHIFT' undeclared (first use in this function); did you mean 'PAGE_SHIFT'?
Should this depend on some HUGETLBFS option?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next parent reply other threads:[~2020-01-08 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191219134646.413164-1-leon@kernel.org>
[not found] ` <20191219134646.413164-4-leon@kernel.org>
2020-01-08 12:56 ` Geert Uytterhoeven [this message]
2020-01-08 15:24 ` Yishai Hadas
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=alpine.DEB.2.21.2001081352560.23971@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=artemyko@mellanox.com \
--cc=aviadye@mellanox.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yishaih@mellanox.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