Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.199022
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 308 Next › Last »

graysky commented on 2021-04-02 10:05 (UTC)

@Zalgo - 5.11.11-3 should fix this. See the forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1965531

graysky commented on 2021-04-02 10:05 (UTC)

@artafinde - with some help, the native option now works with Intel and AMD. You will have to select the correct option though:

...
  33. Intel-Native optimizations autodetected by GCC (MNATIVE_INTEL) (NEW)
  34. AMD-Native optimizations autodetected by GCC (MNATIVE_AMD) (NEW)

Zalgo commented on 2021-04-02 07:20 (UTC)

Thanks for the tip :) If i figure out a way to fix the PKGBUILD that doesn't require manual untarring I'll pose it here

graysky commented on 2021-04-01 20:20 (UTC)

That's odd. Makepkg doesn't seem to be untarring the patch. If you do it manually and add that to the source array, it works as expected.

Zalgo commented on 2021-04-01 17:26 (UTC)

This currently fails on my system with

Setting config...
sed: can't read ../patch-5.11-ck1: No such file or directory
==> ERROR: A failure occurred in prepare().
    Aborting...

can anyone else reproduce? I'll test in a clean chroot

graysky commented on 2021-03-07 19:38 (UTC)

@artafinde - I need to dig deeper, but I think it will be difficult to assign a native CPU out of some configs.

For example, X86_INTEL_USERCOPY config. I do that now but no other AMD chips are listed by upstream[1].

Further, I believe AMD chips should not be in the X86_P6_NOP config[2] or X86_CMOV config[3].

  1. https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L407

  2. https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L421

  3. https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L438

artafinde commented on 2021-03-07 18:50 (UTC) (edited on 2021-03-07 18:50 (UTC) by artafinde)

@graysky checksum for the gcc kernel patch is failing - needs an update.

I noticed the changes in the patch repo and it mentions one should not use native on AMD chips. What's the reasoning behind this since the gcc 10 (and clang for what matters) can detect the cpu arch just fine:

$ gcc -march=native -E -v - </dev/null 2>&1 | grep cc1
 /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/cc1 -E -quiet -v - -march=znver2 -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -msse4a -mcx16 -msahf -mmovbe -maes -msha -mpclmul -mpopcnt -mabm -mno-lwp -mfma -mno-fma4 -mno-xop -mbmi -mno-sgx -mbmi2 -mno-pconfig -mwbnoinvd -mno-tbm -mavx -mavx2 -msse4.2 -msse4.1 -mlzcnt -mno-rtm -mno-hle -mrdrnd -mf16c -mfsgsbase -mrdseed -mprfchw -madx -mfxsr -mxsave -mxsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mclflushopt -mxsavec -mxsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-avx5124fmaps -mno-avx5124vnniw -mclwb -mmwaitx -mclzero -mno-pku -mrdpid -mno-gfni -mno-shstk -mno-avx512vbmi2 -mno-avx512vnni -mno-vaes -mno-vpclmulqdq -mno-avx512bitalg -mno-avx512vpopcntdq -mno-movdiri -mno-movdir64b -mno-waitpkg -mno-cldemote -mno-ptwrite -mno-avx512bf16 -mno-enqcmd -mno-avx512vp2intersect --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=512 -mtune=znver2

vp1981 commented on 2021-02-23 23:59 (UTC)

@simona, AFAIU, graysky keeps config sync with linux package and these two are in linux-zen but not yet in linux.

simona commented on 2021-02-21 23:19 (UTC)

ashmem_linux and binder_linux missing?