From: guoren@kernel.org
To: guoren@kernel.org, greentime.hu@sifive.com,
vincent.chen@sifive.com, andy.chiu@sifive.com,
paul.walmsley@sifive.com, palmer@rivosinc.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Guo Ren <guoren@linux.alibaba.com>
Subject: [PATCH] riscv: vector: Fixup modules compile error
Date: Mon, 29 May 2023 03:38:45 -0400 [thread overview]
Message-ID: <20230529073845.2859178-1-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
Some .ko also need the riscv_v_user_allowed symbol.
ERROR: modpost: "riscv_v_user_allowed" [arch/riscv/kvm/kvm.ko]
undefined!
make[3]: ***
[/home/guoren/source/kernel/linux/scripts/Makefile.modpost:136:
Module.symvers] Error 1
Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
Signed-off-by: Guo Ren <guoren@kernel.org>
---
arch/riscv/kernel/vector.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/kernel/vector.c b/arch/riscv/kernel/vector.c
index 1c4ac821e008..3ae08816d608 100644
--- a/arch/riscv/kernel/vector.c
+++ b/arch/riscv/kernel/vector.c
@@ -129,6 +129,7 @@ bool riscv_v_user_allowed(void)
{
return riscv_v_get_cur_ctrl(current) == PR_RISCV_V_VSTATE_CTRL_ON;
}
+EXPORT_SYMBOL(riscv_v_user_allowed);
bool riscv_v_first_use_handler(struct pt_regs *regs)
{
--
2.36.1
next reply other threads:[~2023-05-29 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 7:38 guoren [this message]
2023-05-29 13:42 ` [PATCH] riscv: vector: Fixup modules compile error Conor Dooley
2023-05-30 2:59 ` Guo Ren
2023-05-30 6:52 ` Guo Ren
2023-05-30 9:48 ` Andy Chiu
2023-05-30 15:37 ` Guo Ren
2023-05-30 16:04 ` Conor Dooley
2023-05-30 16:14 ` Guo Ren
2023-05-30 16:22 ` Guo Ren
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=20230529073845.2859178-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=vincent.chen@sifive.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