Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 706294 - sys-kernel/gentoo-kernel Application for USE=experimental
Summary: sys-kernel/gentoo-kernel Application for USE=experimental
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 2 votes (vote)
Assignee: Distribution Kernel Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-25 11:32 UTC by Tuxine
Modified: 2021-03-08 23:44 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tuxine 2020-01-25 11:32:53 UTC
The new ebuild from gentoo-kernel has generated approval and joy among many users. In this context a request:

It would be very nice if you could integrate "IUSE=experimental" from genpatches into your ebuild.

With these two flags "savedconfig" and "experimental" we have all the possibilities that gentoo-sources also offers.


Thank you
Comment 1 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2020-01-25 11:49:11 UTC
Do you actually use any of the features provided by experimental patches?  I skipped them because they didn't seem very useful for generic configs.  OTOH, I don't really understand why they are optional given that AFAICS they don't change anything by default.
Comment 2 Vladimir 2020-09-16 12:28:10 UTC
Hi all. 
I know some ppl loving CONFIG_MNATIVE. Despite it's obviously not generic feature, having ability for transparent migration to portage-management kernel updates with exactly same functionality (achieved by savedconfig) is nice, imo.
Comment 3 Vlad 2020-09-21 09:35:03 UTC
Hello,

We're using CONFIG_MNATIVE from the experimental patches and ZSTD compression. Yes, I agree that they are optional, but if you provide 'savedconfig' feature, IMHO 'experimental' would be useful as well and they're maintained for 'gentoo-sources' anyway.
Comment 4 Esteve Varela Colominas 2020-12-16 12:35:30 UTC
Chiming in since I dropped the GCC patch in my /etc/portage/patches and a snippet to set CONFIG_MZEN=y in my /etc/kernel/config.d.
The main usecase of this kernel to me is avoiding the whole kernel upgrade song and dance, and just having it upgrade overnight with everything else without intervention. I got sick of missing kernel drivers for peripherals when I need to use them, and digging through the kernel config for them, not to mention the times I've had performance issues due to some kernel config I didn't know, so running a "generic", portage-managed kernel relieves me of the duty and worry, despite only running it on one machine. I use `-march=znver` in my make.conf, so why wouldn't I apply it to the kernel as well?
Comment 5 Peter Levine 2021-03-08 23:44:27 UTC
I started using sys-kernel/gentoo-kernel a month ago.  Having manually built the kernel from gentoo-sources for the last 16 years, I think auto-building the kernel without having to deal with ugly hooks is one of this distro's greatest advancements in years.  I have always used the experimental patch.  It adds a small but measurable gain (see https://github.com/graysky2/kernel_gcc_patch) and -march=native adds cache-line heuristics, I believe.

(In reply to Michał Górny from comment #1)
> Do you actually use any of the features provided by experimental patches?  I
> skipped them because they didn't seem very useful for generic configs. 
> OTOH, I don't really understand why they are optional given that AFAICS they
> don't change anything by default.

So I'll ask naively, why not merge gentoo-sources into gentoo-kernel?  You can add "generic" USE flags for a generic build, "source" USE flag for full source installation, etc...  Why maintain the two separately when they're so logically similar?