Package Details: linux-ck 6.12.1-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: The Linux kernel and modules with ck's hrtimer patches
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.24
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-23 13:58 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 89 90 91 92 93 94 95 96 97 98 99 .. 308 Next › Last »

blitz commented on 2016-12-18 23:07 (UTC)

@graysky - Kernel config allows for menu driven cpu arch selection with minimal interaction and pre-selected MNATIVE. (taken from own PKGBUILD) _CPU_NATIVE=y ... ### Optionally set processor type for kernel if [ -n "${_CPU_NATIVE}" ]; then msg "Setting cpu arch to gcc native..." if [ "${CARCH}" = "x86_64" ]; then sed -i -e 's/^CONFIG_GENERIC_CPU=y/# CONFIG_GENERIC_CPU is not set/' \ -i -e 's/^# CONFIG_MNATIVE is not set/CONFIG_MNATIVE=y/' ./.config else sed -i -e 's/^CONFIG_M686=y/# CONFIG_M686 is not set/' \ -i -e 's/^# CONFIG_MNATIVE is not set/CONFIG_MNATIVE=y/' ./.config fi fi

graysky commented on 2016-12-18 19:38 (UTC)

@mrkline - Update the checksum (again without bumping the pkgver). No real easy way to automate the selection of native.

mrkline commented on 2016-12-18 19:29 (UTC)

@graysky - The menu is quite nice! Hopefully I can stop messing around in nconfig soon. On that note, is it possible to automate the selection? I tried adding a `CONFIG_MNATIVE=y` line to config.x86_64, but I was still prompted when I ran makepkg. Also, enable_additional_cpu_optimizations_for_gcc_v4.9+_kernel_v3.15+.patch.gz needs its SHA updated.

graysky commented on 2016-12-18 17:36 (UTC)

OK, just updated without bumping the pkgver with this change. Feedback is welcomed.

graysky commented on 2016-12-18 13:42 (UTC)

@artafinde - see my comment from 2016-12-18 10:44 for the example.

artafinde commented on 2016-12-18 12:37 (UTC)

@graysky Can you provide a PKGBUILD (maybe through gist) to see how much interaction will be needed? I personally have to edit PKGBUILD anyway since I'm building with modprobed and BFS enabled by default (and using "-march=native")

nTia89 commented on 2016-12-18 11:43 (UTC) (edited on 2016-12-18 11:45 (UTC) by nTia89)

yes, missing of optimizations without -march=native is my worry! (I know, this seems false but it is true... https://bbs.archlinux.org/viewtopic.php?id=210740) hence, any modification is welcome, even if this mean to press some key my doubt is another: who builds this package from AUR, I imagine, wants the best optimizations overall, so, why "-march=native" is not the default choice?

zerophase commented on 2016-12-18 10:59 (UTC)

@graysky depends on how it's implemented. But, in general if a config file has new additions in a package bump it interrupts kernel compilation till I resolve the issue. I imagine whatever you implement will work with yaourt as well.

graysky commented on 2016-12-18 10:44 (UTC)

A modification I am considering is to have the AUR package provide unmodified config files for x86_64 and for i686 with respect to the gcc patch. What this means is that whenever you build linux-ck yourself, makepkg (or am I assuming your AUR helper) will pause and wait for you to select from the list of CPU optimizations (with default being a simple enter key). This will circumvent the need to modify the PKGBUILD enabled the nconfig option, and subsequent poking around in the nconfig itself. Potentially way faster and easier for the user. 1) How do people feel about this? 2) Will the added interactivity break AUR helpers (I am a pure makepkg person myself)? Example output: % makepkg -src ==> Making package: linux-ck 4.8.15-2 (Sun Dec 18 05:42:02 EST 2016) ... Processor family 1. AMD Opteron/Athlon64/Hammer/K8 (MK8) 2. AMD Opteron/Athlon64/Hammer/K8 with SSE3 (MK8SSE3) (NEW) 3. AMD 61xx/7x50/PhenomX3/X4/II/K10 (MK10) (NEW) 4. AMD Barcelona (MBARCELONA) (NEW) 5. AMD Bobcat (MBOBCAT) (NEW) 6. AMD Bulldozer (MBULLDOZER) (NEW) 7. AMD Piledriver (MPILEDRIVER) (NEW) 8. AMD Steamroller (MSTEAMROLLER) (NEW) 9. AMD Jaguar (MJAGUAR) (NEW) 10. Intel P4 / older Netburst based Xeon (MPSC) 11. Intel Atom (MATOM) 12. Intel Core 2 (MCORE2) 13. Intel Nehalem (MNEHALEM) (NEW) 14. Intel Westmere (MWESTMERE) (NEW) 15. Intel Silvermont (MSILVERMONT) (NEW) 16. Intel Sandy Bridge (MSANDYBRIDGE) (NEW) 17. Intel Ivy Bridge (MIVYBRIDGE) (NEW) 18. Intel Haswell (MHASWELL) (NEW) 19. Intel Broadwell (MBROADWELL) (NEW) 20. Intel Skylake (MSKYLAKE) (NEW) > 21. Generic-x86-64 (GENERIC_CPU) 22. Native optimizations autodetected by GCC (MNATIVE) (NEW) choice[1-22?]:

graysky commented on 2016-12-18 10:07 (UTC)

@SuperIce97 @mrkline - Good points about usability and about niche population with aged hardware. I reverted the commit removing native updating 4.8.15-2 without bumping the pkgver since I don't want to rebuild for [repo-ck] since this change has 0 impact to the repo packages.

« First ‹ Previous 1 .. 89 90 91 92 93 94 95 96 97 98 99 .. 308 Next › Last »