From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org, Jason Gunthorpe <jgg@nvidia.com>,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-rdma@vger.kernel.org, linux-um@lists.infradead.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH 2/2] IB/rdmavt: modify rdmavt/qp.c for UML
Date: Sat, 1 Jan 2022 23:06:23 -0800 [thread overview]
Message-ID: <20220102070623.24009-1-rdunlap@infradead.org> (raw)
When building rdmavt for ARCH=um, qp.c has a build error on a reference
to the x86-specific cpuinfo field 'x86_cache_size'. This value is then
used to determine whether to use cacheless_memcpy() or not.
Provide a fake value to LLC for CONFIG_UML. Then provide a separate
verison of cacheless_memcpy() for CONFIG_UML that is just a plain
memcpy(), like the calling code uses.
Prevents these build errors:
../drivers/infiniband/sw/rdmavt/qp.c: In function ‘rvt_wss_llc_size’:
../drivers/infiniband/sw/rdmavt/qp.c:88:23: error: ‘struct cpuinfo_um’ has no member named ‘x86_cache_size’; did you mean ‘x86_capability’?
return boot_cpu_data.x86_cache_size;
../drivers/infiniband/sw/rdmavt/qp.c: In function ‘cacheless_memcpy’:
../drivers/infiniband/sw/rdmavt/qp.c:100:2: error: implicit declaration of function ‘__copy_user_nocache’; did you mean ‘copy_user_page’? [-Werror=implicit-function-declaration]
__copy_user_nocache(dst, (void __user *)src, n, 0);
Fixes: 68f5d3f3b654 ("um: add PCI over virtio emulation driver")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
drivers/infiniband/sw/rdmavt/qp.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
--- linux-next-20211224.orig/drivers/infiniband/sw/rdmavt/qp.c
+++ linux-next-20211224/drivers/infiniband/sw/rdmavt/qp.c
@@ -84,10 +84,15 @@ EXPORT_SYMBOL(ib_rvt_state_ops);
/* platform specific: return the last level cache (llc) size, in KiB */
static int rvt_wss_llc_size(void)
{
+#if !defined(CONFIG_UML)
/* assume that the boot CPU value is universal for all CPUs */
return boot_cpu_data.x86_cache_size;
+#else /* CONFIG_UML */
+ return 1024; /* fake 1 MB LLC size */
+#endif
}
+#if !defined(CONFIG_UML)
/* platform specific: cacheless copy */
static void cacheless_memcpy(void *dst, void *src, size_t n)
{
@@ -99,6 +104,13 @@ static void cacheless_memcpy(void *dst,
*/
__copy_user_nocache(dst, (void __user *)src, n, 0);
}
+#else
+/* for CONFIG_UML, this is just a plain memcpy() */
+static void cacheless_memcpy(void *dst, void *src, size_t n)
+{
+ memcpy(dst, src, n);
+}
+#endif
void rvt_wss_exit(struct rvt_dev_info *rdi)
{
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next reply other threads:[~2022-01-02 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 7:06 Randy Dunlap [this message]
2022-01-03 23:04 ` [PATCH 2/2] IB/rdmavt: modify rdmavt/qp.c for UML Jason Gunthorpe
2022-01-04 1:00 ` Randy Dunlap
2022-01-04 8:03 ` Anton Ivanov
2022-01-04 8:43 ` Johannes Berg
2022-01-04 7:43 ` Christoph Hellwig
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=20220102070623.24009-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=jdike@addtoit.com \
--cc=jgg@nvidia.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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