From: jordan <triplesquarednine@gmail.com>
To: John Kacur <jkacur@redhat.com>
Cc: Gautam Thaker <gautam.h.thaker@lmco.com>, linux-rt-users@vger.kernel.org
Subject: Re: "yum install ...." based instruction on building a RT kernel.
Date: Sat, 18 Sep 2010 15:15:54 -0400 [thread overview]
Message-ID: <AANLkTikv7cmA_F==TKa1m0o_N1OHxp3RgXXMErhcgGM0@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=GbDU7fKh9LvCEpjhSSMFF0syCqJVuqUERVBEJ@mail.gmail.com>
Hey John,
> You think that optimizing it is easy?
Yes, i do. :)
1. Patching the kernel is simple (as long as you are using the right
patch with the right version). Most of the time it is as simple as
putting the patch in the kernel's directory and running:
patch -p1 < "whatever the patch is called"
Then it will show you if it patched correctly, if it didn't hit a
linux forum and ask for help. It isn't rocket science...
2. To strip away all modules that you don't require, you only need to
run a simple command from a terminal before you compile:
"make localmodconfig".
Then you can use "make menuconfig or mkae xconfig", and look through
the configuration, then disable features that you don't need or want.
Alot of the time it is common sense, as some things will be obvious to
most people, that they are features your hardware/setup doesn't
require. other times, google will be your bestfriend.
3. After that, you can hit the gentoo documentation and/or the GCC
documentation, and read about CFLAGS...once, you figure out what you
may like to use, and what isn't dangerous (too harsh of optimizations
can break things).
Then, you can run the necessary commands when you go to compile.
my example (these are for my machine, and i use strict optimizations,
so don't assume you should use them!)
'make CFLAGS="-O3 -march=native -pipe -fomit-frame-pointer -DPIC -fPIC
-s" LDFLAGS="-z combreloc" rpm'
(in my case this will make my optimized kernel into RPMs to use with Fedora)
4. Let it compile, if that goes okay, install it. then, depending on
your distro/method used by the distro, you may have to use "dracut" or
some other tool that make your initrd and you might manually have to
edit grub.
After this is all completed reboot!
if there are any problems booting into your new kernel, google the
error message and fix the problem.
if you need help hit a forum.
I don't think that is difficult. I taught myself how to do this, and
im not a genius! (it's like 5 terminal commands, some reading and
following instructions, easily found on the interweb)
jordan
next prev parent reply other threads:[~2010-09-18 19:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 22:54 "yum install ...." based instruction on building a RT kernel Gautam Thaker
2010-09-17 6:08 ` jordan
2010-09-17 7:08 ` John Kacur
2010-09-17 12:38 ` Daniel James
2010-09-17 13:06 ` Bernardo Barros
2010-09-17 15:25 ` EXTERNAL: " Gautam Thaker
2010-09-18 19:34 ` jordan
2010-09-17 13:10 ` John Kacur
2010-09-18 19:24 ` jordan
2010-09-19 15:49 ` Clark Williams
2010-09-19 17:23 ` jordan
2010-09-19 19:20 ` Bernardo Barros
2010-09-19 20:00 ` jordan
2010-10-17 15:20 ` jordan
2010-10-18 6:16 ` John Kacur
2010-10-18 7:12 ` jordan
2010-09-18 19:15 ` jordan [this message]
2010-09-18 20:06 ` jordan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikv7cmA_F==TKa1m0o_N1OHxp3RgXXMErhcgGM0@mail.gmail.com' \
--to=triplesquarednine@gmail.com \
--cc=gautam.h.thaker@lmco.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).