From: Adam Borowski <kilobyte@angband.pl>
To: Anup Patel <anup.patel@wdc.com>,
kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org
Subject: ERROR: modpost: "boot_cpu_hartid" [arch/riscv/kvm/kvm.ko] undefined!
Date: Mon, 22 Nov 2021 18:14:04 +0100 [thread overview]
Message-ID: <YZvP3AuTdEdje/IY@angband.pl> (raw)
Hi!
With CONFIG_KVM=m and CONFIG_SMP=n, the build fails with:
ERROR: modpost: "boot_cpu_hartid" [arch/riscv/kvm/kvm.ko] undefined!
An obvious fix would be to change riscv_cpuid_to_hartid_mask() from a
static inline function to a real exported symbol, but I wonder: is there
a point in allowing such combinations that no one will test?
Meow.
--
⢀⣴⠾⠻⢶⣦⠀ .--[ Makefile ]
⣾⠁⢠⠒⠀⣿⡁ # beware of races
⢿⡄⠘⠷⠚⠋⠀ all: pillage burn
⠈⠳⣄⠀⠀⠀⠀ `----
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2021-11-22 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 17:14 Adam Borowski [this message]
2021-11-22 18:34 ` ERROR: modpost: "boot_cpu_hartid" [arch/riscv/kvm/kvm.ko] undefined! Sean Christopherson
2021-11-23 5:33 ` Anup Patel
2021-11-23 15:07 ` Atish Patra
2021-11-29 21:23 ` Sean Christopherson
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=YZvP3AuTdEdje/IY@angband.pl \
--to=kilobyte@angband.pl \
--cc=anup.patel@wdc.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
/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