-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.2 fails to build kernel modules on aarch64 #15401
Comments
Hm, I guess this is actually a dupe of #14555. 2.1.x builds for me because I was patching out the neon paths for raidz/fletcher, but it seems 2.2 brought changes that expand the usage of kernel NEON further, which resulted in that no longer being sufficient. |
I'm facing the same issue. Kernel 6.6.1 arm64 with ZFS 2.2.1 (since OpenZFS 2.2.1 Linux Kernel 6.6 series is supported).
The warning is due to using a binary Kernel built from another developer for Rock Pi 5B (on Debian Testing / GCC 13), while I'm on Debian Bookworm / GCC 12. Any solution for this ? |
a workaround is https://github.com/chimera-linux/cports/blob/master/main/zfs/patches/aarch64-disable-neon.patch - but that will of course disable all the aarch64 simd |
Do you mean SIMD as an ARM64 Instruction Set ? What consequences would that have ? Would ZFS work correctly in the end for e.g. a simple Disk / mirror VDEV ? |
everything will work, some things will miss acceleration |
Alright, at least it built now. I'll try to see if I can generate the required DEB files and see how it works. Thanks :) |
This patch adds check for `kernel_neon_*` symbols on arm and arm64 platforms to address the following issues: 1. Linux 6.2+ on arm64 has exported them with `EXPORT_SYMBOL_GPL`, so license compatibility must be checked before use. 2. On both arm and arm64, the definitions of these symbols are guarded by `CONFIG_KERNEL_MODE_NEON`, but their declarations are still present. Checking in configuration phase only leads to MODPOST errors (undefined references). Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Shengqi Chen <harry-chen@outlook.com> Closes openzfs#15711 Closes openzfs#14555 Closes: openzfs#15401
This patch adds check for `kernel_neon_*` symbols on arm and arm64 platforms to address the following issues: 1. Linux 6.2+ on arm64 has exported them with `EXPORT_SYMBOL_GPL`, so license compatibility must be checked before use. 2. On both arm and arm64, the definitions of these symbols are guarded by `CONFIG_KERNEL_MODE_NEON`, but their declarations are still present. Checking in configuration phase only leads to MODPOST errors (undefined references). Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Shengqi Chen <harry-chen@outlook.com> Closes #15711 Closes #14555 Closes: #15401
This patch adds check for `kernel_neon_*` symbols on arm and arm64 platforms to address the following issues: 1. Linux 6.2+ on arm64 has exported them with `EXPORT_SYMBOL_GPL`, so license compatibility must be checked before use. 2. On both arm and arm64, the definitions of these symbols are guarded by `CONFIG_KERNEL_MODE_NEON`, but their declarations are still present. Checking in configuration phase only leads to MODPOST errors (undefined references). Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Shengqi Chen <harry-chen@outlook.com> Closes openzfs#15711 Closes openzfs#14555 Closes: openzfs#15401
This patch adds check for `kernel_neon_*` symbols on arm and arm64 platforms to address the following issues: 1. Linux 6.2+ on arm64 has exported them with `EXPORT_SYMBOL_GPL`, so license compatibility must be checked before use. 2. On both arm and arm64, the definitions of these symbols are guarded by `CONFIG_KERNEL_MODE_NEON`, but their declarations are still present. Checking in configuration phase only leads to MODPOST errors (undefined references). Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Shengqi Chen <harry-chen@outlook.com> Closes openzfs#15711 Closes openzfs#14555 Closes: openzfs#15401
System information
Describe the problem you're observing
Does not build on aarch64:
Describe how to reproduce the problem
Build the kernel modules on aarch64.
Include any warning/errors/backtraces from the system logs
Clang 16 compiler, but should not be relevant.
The text was updated successfully, but these errors were encountered: