Package Details: linux-xanmod 5.12.10-1

Git Clone URL: https://aur.archlinux.org/linux-xanmod.git (read-only, click to copy)
Package Base: linux-xanmod
Description: The Linux kernel and modules with Xanmod patches
Upstream URL: http://www.xanmod.org/
Licenses: GPL2
Submitter: Yoshi2889
Maintainer: figue (figuepluto, jfigueras)
Last Packager: figue
Votes: 76
Popularity: 5.52
First Submitted: 2017-02-14 09:40
Last Updated: 2021-06-12 07:11

Pinned Comments

figue commented on 2021-06-10 20:47

Starting from 5.12.10, upstream moved config files to a folder, and it provides a config for gcc or clang. So I added a new variable :)

So you can set $_compiler to "gcc" or "clang" (default is gcc).

figue commented on 2018-12-14 00:50

This package have several variables to enable/disable features.

##
## The following variables can be customized at build time. Use env or export to change at your wish
##
##   Example: env _microarchitecture=98 use_numa=n use_tracers=n use_pds=n makepkg -sc
##
## Look inside 'choose-gcc-optimization.sh' to choose your microarchitecture
## Valid numbers between: 0 to 99
## Default is: 0 => generic
## Good option if your package is for one machine: 98 (Intel native) or 99 (AMD native)
if [ -z ${_microarchitecture+x} ]; then
  _microarchitecture=0
fi

## Disable NUMA since most users do not have multiple processors. Breaks CUDA/NvEnc.
## Archlinux and Xanmod enable it by default.
## Set variable "use_numa" to: n to disable (possibly increase performance)
##                             y to enable  (stock default)
if [ -z ${use_numa+x} ]; then
  use_numa=y
fi

## For performance you can disable FUNCTION_TRACER/GRAPH_TRACER. Limits debugging and analyzing of the kernel.
## Stock Archlinux and Xanmod have this enabled. 
## Set variable "use_tracers" to: n to disable (possibly increase performance)
##                                y to enable  (stock default)
if [ -z ${use_tracers+x} ]; then
  use_tracers=y
fi

## Choose between GCC and CLANG config (default is GCC)
if [ -z ${_compiler+x} ]; then
  _compiler=gcc
fi

# Compile ONLY used modules to VASTLYreduce the number of modules built
# and the build time.
#
# To keep track of which modules are needed for your specific system/hardware,
# give module_db script a try: https://aur.archlinux.org/packages/modprobed-db
# This PKGBUILD read the database kept if it exists
#
# More at this wiki page ---> https://wiki.archlinux.org/index.php/Modprobed-db
if [ -z ${_localmodcfg} ]; then
  _localmodcfg=n
fi

Personally I'm running now xanmod kernel compiled with this:

env _microarchitecture=98 use_numa=n use_tracers=n use_ns=y _localmodcfg=y makepkg -sic

Also, you can now create the file myconfig in your local repo to build this package with a custom config or use ${XDG_CONFIG_HOME}/linux-xanmod/myconfig. This file can be a full kernel config or be a script with several entries to add/remove options (you have several examples in PKGBUILD by using scripts/config):

Code involved:

  for _myconfig in "${startdir}/myconfig" "${XDG_CONFIG_HOME}/linux-xanmod/myconfig" ; do
    if [ -f "${_myconfig}" ]; then
      if grep -q 'scripts/config' "${_myconfig}"; then
        # myconfig is a partial file. Executing as a script
        msg2 "Applying myconfig..."
        bash -x "${_myconfig}"
      else
        # myconfig is a full config file. Replacing default .config
        msg2 "Using user CUSTOM config..."
        cp -f "${_myconfig}" .config
      fi
      echo
    fi
  done

Latest Comments

1 2 3 4 5 6 ... Next › Last »

figue commented on 2021-06-12 07:13

I've pushed some more fixes for clang build. Now it enables thin lto by default. I think default package with gcc is ok, and clang too, but if I made some mistake, please, report here. Thanks!

figue commented on 2021-06-10 20:47

Starting from 5.12.10, upstream moved config files to a folder, and it provides a config for gcc or clang. So I added a new variable :)

So you can set $_compiler to "gcc" or "clang" (default is gcc).

redsolja commented on 2021-05-23 11:58

@figue you were right, thanks!

figue commented on 2021-05-21 16:10

Thanks @arglebargle. Looks good. Will add it in the next release.

arglebargle commented on 2021-05-21 09:18

Here's a small patch to support the new GCC 11 x86_64 microarchitecture feature level targets. Support for these choices is already upstream in the GCC patch Xanmod is applying, this just lets you pick them with the included gcc script.

92, 93, 94 select x86-64-v2, -v3 and -v4 respectively, you need GCC >= 11 for these to do anything useful. Feel free to modify however you like if 92, 93 and 94 aren't what you'd choose for this.

commit 4a477efde9fa24138733bc6b3eca7bd468e5528b
Author: Scott B <28817345+foundObjects@users.noreply.github.com>
Date:   Mon May 17 10:02:32 2021 -0700

    add new GCC-11 feature targets; require GCC>=11

diff --git a/choose-gcc-optimization.sh b/choose-gcc-optimization.sh
index e45a210..f10eec5 100755
--- a/choose-gcc-optimization.sh
+++ b/choose-gcc-optimization.sh
@@ -59,6 +59,10 @@ cat << EOF
    46) Intel Rocket Lake
    47) Intel Alder Lake

+   92) Generic-x86-64-v2 (Nehalem and newer)
+   93) Generic-x86-64-v3 (Haswell and newer)
+   94) Generic-x86-64-v4 (AVX512 CPUs)
+
    98) Intel-Native optimizations autodetected by GCC
    99) AMD-Native optimizations autodetected by GCC

@@ -117,6 +121,9 @@ case $answer in
    45) Microarchitecture=CONFIG_MSAPPHIRERAPIDS ;;
    46) Microarchitecture=CONFIG_MROCKETLAKE ;;
    47) Microarchitecture=CONFIG_MALDERLAKE ;;
+   92) Microarchitecture=CONFIG_GENERIC_CPU2 ;;
+   93) Microarchitecture=CONFIG_GENERIC_CPU3 ;;
+   94) Microarchitecture=CONFIG_GENERIC_CPU4 ;;
    98) Microarchitecture=CONFIG_MNATIVE_INTEL ;;
    99) Microarchitecture=CONFIG_MNATIVE_AMD ;;
     *) default=CONFIG_GENERIC_CPU ;;

figue commented on 2021-05-20 22:03

@redsolja please clean your src (makepkg -C), patches are ok.

redsolja commented on 2021-05-20 21:28

Cannot build.

patching file virt/kvm/kvm_main.c
==> ERROR: A failure occurred in prepare().
    Aborting...

figue commented on 2021-05-08 11:50

@tam1m done! Thanks.

cartesius commented on 2021-05-08 08:08

I'd also vote for a non-colliding _microarchitecture value.

tam1m commented on 2021-05-08 00:30

@figue

Since 781eefb2ce30

_microarchitecture=98 sets CONFIG_MNATIVE_INTEL

and

_microarchitecture=99 sets CONFIG_MNATIVE_AMD

You should probably update the comments in the PKGBUILD since a lot of people might build for the wrong architecture by settings _microarchitecture=99 as suggested