Mirokhodets

joined 2 days ago
sorted by: new top controversial old
Linux 6.16 adds the “X86_NATIVE_CPU” option to optimize your kernel build for your processorThe X86_NATIVE_CPU Kconfig build time parameter has been merged for the Linux 6.16 merge window as an easy w in c/linux@lemmy.ml
[–] Mirokhodets@lemmy.ml 1 points 38 minutes ago

Any achievement requires sacrifice

Linux 6.16 adds the “X86_NATIVE_CPU” option to optimize your kernel build for your processorThe X86_NATIVE_CPU Kconfig build time parameter has been merged for the Linux 6.16 merge window as an easy w in c/linux@lemmy.ml
[–] Mirokhodets@lemmy.ml 1 points 41 minutes ago (1 children)

Yes, to use the CONFIG_X86_NATIVE_CPU option, you will need to compile the kernel yourself with this option enabled. This is a compile-time setting that affects how the compiler optimizes the build specifically for your system. Prebuilt kernels from distro repositories usually do not have this enabled, since they are built for broad compatibility with many different processors.

Linux 6.16 adds the “X86_NATIVE_CPU” option to optimize your kernel build for your processorThe X86_NATIVE_CPU Kconfig build time parameter has been merged for the Linux 6.16 merge window as an easy w in c/linux@lemmy.ml
31
Linux 6.16 adds the “X86_NATIVE_CPU” option to optimize your kernel build for your processorThe X86_NATIVE_CPU Kconfig build time parameter has been merged for the Linux 6.16 merge window as an easy w (lemmy.ml)
 

The X86_NATIVE_CPU Kconfig build time parameter has been merged for the Linux 6.16 merge window as an easy way to enforce the “-march=native” compiler behavior on AMD and Intel processors to optimize kernel builds for your system's local CPU architecture/family. For those who want “-march=native” for Linux kernel builds on AMD/Intel x86_64 processors, you can easily include a new CONFIG_X86_NATIVE_CPU parameter to set this compiler behavior in local kernel builds. The CONFIG_X86_NATIVE_CPU parameter is considered when compiling the Linux x86_64 kernel with GCC or LLVM Clang when using Clang 19 or later due to a compiler bug in the Linux kernel in older compiler versions. In addition to setting the compiler parameter “-march=native” for Linux kernel C code, enabling this new Kconfig build parameter also sets “-Ctarget-cpu=native” for Rust kernel code.

Looking for a theme that looks like this in c/linux@lemmy.ml
Looking for a theme that looks like this in c/linux@lemmy.ml
Looking for a theme that looks like this in c/linux@lemmy.ml
Does Windows virtual machine crash due to low RAM? in c/linux@lemmy.ml
If i encrypt Linux partition, will it break Windows? in c/linux@lemmy.ml
[–] Mirokhodets@lemmy.ml 2 points 1 day ago

When you install Debian with encryption (usually LUKS — Linux Unified Key Setup), only the partition where Debian is installed is encrypted. Windows will remain on a separate partition and will not be touched. Debian encryption does not break Windows, provided that: The partitions for Windows and Debian are clearly separated. You do not change or delete the Windows partition. The bootloader (GRUB) is correctly configured and not damaged. Usually, Debian will install GRUB, which will recognize Windows and add it to the boot menu. If something goes wrong during the bootloader (GRUB) installation, Windows boot may temporarily break. But this can be fixed — you can restore the Windows bootloader using a bootable USB stick. It is always better to back up important data before installation. When installing Debian, choose manual disk partitioning to accurately specify the partitions. Use encryption only for the Linux partition, leaving the Windows partition alone. Save a backup copy of the boot partition (for example, EFI) or make a full backup.

Looking for a theme that looks like this in c/linux@lemmy.ml
Are my DVD/VOB files broken? in c/linux@lemmy.ml
Are my DVD/VOB files broken? in c/linux@lemmy.ml
Looking for a theme that looks like this in c/linux@lemmy.ml