Re: [opensuse-kernel] Re: [RFC] Simplifying kernel configuration for distro issues
- To: Borislav Petkov <email@example.com>
- Cc: Linus Torvalds <firstname.lastname@example.org>, Steven Rostedt <email@example.com>, Cyrill Gorcunov <firstname.lastname@example.org>, Pekka Enberg <email@example.com>, richard -rw- weinberger <firstname.lastname@example.org>, "Myklebust, Trond" <Trond.Myklebust@netapp.com>, Dave Jones <email@example.com>, Greg Kroah-Hartman <firstname.lastname@example.org>, Ubuntu Kernel Team <email@example.com>, Debian Kernel Team <firstname.lastname@example.org>, OpenSUSE Kernel Team <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, Ingo Molnar <email@example.com>, Sasha Levin <firstname.lastname@example.org>, Asias He <email@example.com>
- Subject: Re: [opensuse-kernel] Re: [RFC] Simplifying kernel configuration for distro issues
- From: Konrad Rzeszutek Wilk <firstname.lastname@example.org>
- Date: Thu, 19 Jul 2012 14:42:49 -0400
- Message-id: <[🔎] 20120719184249.GA6696@phenom.dumpdata.com>
- In-reply-to: <[🔎] 20120719175310.GF23393@aftab.osrc.amd.com>
- References: <[🔎] email@example.com> <[🔎] CAFLxGvxxWodD97=78218wc+tuigAFsNK_PdroDfb4BWTZoxxUw@mail.gmail.com> <[🔎] 20120714103716.GD26559@liondog.tnic> <CAOJsxLGHQuuXqDD-1SNhL7Ly1-heCYFLzqj3SLh4xzmP9NR5GQ@mail.gmail.com> <[🔎] 20120714124332.GA4093@moon> <[🔎] 20120714174827.GA13319@aftab.osrc.amd.com> <[🔎] 20120719144217.GC16873@home.goodmis.org> <[🔎] 20120719164807.GD23393@aftab.osrc.amd.com> <[🔎] CA+55aFxX41pGnHcc17A=VBnW+03LEwkwATiZWObbPgD9Ap37Xg@mail.gmail.com> <[🔎] 20120719175310.GF23393@aftab.osrc.amd.com>
On Thu, Jul 19, 2012 at 07:53:10PM +0200, Borislav Petkov wrote:
> On Thu, Jul 19, 2012 at 10:06:44AM -0700, Linus Torvalds wrote:
> > On Thu, Jul 19, 2012 at 9:48 AM, Borislav Petkov <firstname.lastname@example.org> wrote:
> > >
> > > Seriously, this helps only in the cases where the stuff the distro
> > > actually needs is in modules. So, there probably are obscure situations
> > > where you need to enable stuff which is bool and not M.
> > Sadly, not obscure at all.
> > Most of the *drivers* are modules, but most of the "distro config"
> > options are indeed booleans (or, if tristate, =y).
> > Even driver-wise, there are some things that are often =y, even though
> > you generally don't want them.
> Tell me about it. I'm always pissed off when someone thinks his stuff is
> very important and sets his sacred option to be =y/=m by default so the
> wider audience can at least compile-test it while the majority of the
> machines don't actually need it.
> A more coarse-grained config where most of the stuff is off by default
> could take care of that probably.
> > PCMCIA? Not even *laptops* have that shit any more, but having
> > built-in cardbus support almost certainly helps in a distro kernel for
> > booting of certain odder cases.
> Yeah, distros need the one-size-fits-all thing so they have to enable
> > Xen support? Odd partition tables? All the different AGP versions?
> > Many of us couldn't care less, but again, it makes sense in the actual
> > distro kernel, even if it does *not* necessarily make sense in a
> > personalized one.
I proposed something that would solve some of this - but not during
compile time but rather during boot-time
(interestingly enough hpa was first to propose it 10 years ago :-)
The goal is turn built-in components in well, unloadable components.
That way you won't have at least that much stuff laying around not being
used. Not the full silver bullet, but at least it gets some of this
stuff out of the way and you don't have to worry about the extra
stuff that was built-in.