From: Jason Gunthorpe <jgg@ziepe.ca>
To: Cheng Xu <chengyou@linux.alibaba.com>
Cc: dledford@redhat.com, leon@kernel.org, linux-rdma@vger.kernel.org,
KaiShen@linux.alibaba.com, tonylu@linux.alibaba.com
Subject: Re: [PATCH rdma-next v2 07/11] RDMA/erdma: Add verbs implementation
Date: Mon, 17 Jan 2022 11:15:10 -0400 [thread overview]
Message-ID: <20220117151510.GC8034@ziepe.ca> (raw)
In-Reply-To: <20220117084828.80638-8-chengyou@linux.alibaba.com>
On Mon, Jan 17, 2022 at 04:48:24PM +0800, Cheng Xu wrote:
> + entry = to_emmap(rdma_entry);
> +
> + switch (entry->mmap_flag) {
> + case ERDMA_MMAP_IO_NC:
> + /* map doorbell. */
> + vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
This should be pgprot_device()
> + err = io_remap_pfn_range(vma, vma->vm_start, PFN_DOWN(entry->address),
> + PAGE_SIZE, vma->vm_page_prot);
> + break;
> + default:
> + pr_err("mmap failed, mmap_flag = %d\n", entry->mmap_flag);
Audit this whole driver for prints:
1) Do not ever print on user spcae triggered paths, like this
2) Always use ibdev_dbg/err/etc
> +void erdma_disassociate_ucontext(struct ib_ucontext *ibcontext)
> +{
> +}
Does the driver really fully support device disassociation, including
support to recover from itin rdma-core? Don't define this function otherwise.
Jason
next prev parent reply other threads:[~2022-01-17 15:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 8:48 [PATCH rdma-next v2 00/11] Elastic RDMA Adapter (ERDMA) driver Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 01/11] RDMA: Add ERDMA to rdma_driver_id definition Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 02/11] RDMA/erdma: Add the hardware related definitions Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 03/11] RDMA/erdma: Add main include file Cheng Xu
2022-01-17 14:58 ` Jason Gunthorpe
2022-01-18 2:57 ` Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 04/11] RDMA/erdma: Add cmdq implementation Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 05/11] RDMA/erdma: Add event queue implementation Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 06/11] RDMA/erdma: Add verbs header file Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 07/11] RDMA/erdma: Add verbs implementation Cheng Xu
2022-01-17 15:15 ` Jason Gunthorpe [this message]
2022-01-18 3:00 ` Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 08/11] RDMA/erdma: Add connection management (CM) support Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 09/11] RDMA/erdma: Add the erdma module Cheng Xu
2022-01-17 15:22 ` Jason Gunthorpe
2022-01-18 3:29 ` Cheng Xu
2022-01-18 8:28 ` Leon Romanovsky
2022-01-18 11:47 ` Cheng Xu
2022-01-18 12:37 ` Jason Gunthorpe
2022-01-18 13:03 ` Cheng Xu
2022-01-18 14:13 ` Jason Gunthorpe
2022-01-19 1:57 ` Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 10/11] RDMA/erdma: Add the ABI definitions Cheng Xu
2022-01-17 8:48 ` [PATCH rdma-next v2 11/11] RDMA/erdma: Add driver to kernel build environment Cheng Xu
-- strict thread matches above, loose matches on Subject: below --
2022-01-18 14:06 [PATCH rdma-next v2 07/11] RDMA/erdma: Add verbs implementation Bernard Metzler
2022-01-19 3:26 ` Cheng Xu
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=20220117151510.GC8034@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=KaiShen@linux.alibaba.com \
--cc=chengyou@linux.alibaba.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tonylu@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).