kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: linux@manojrajarao.com (Manoj)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What is the fastest way to build and boot a kernel
Date: Tue, 25 Apr 2017 06:15:30 -0700	[thread overview]
Message-ID: <878tmoljbh.fsf@manojrajarao.com> (raw)
In-Reply-To: <CAHz_S75OZY2YK_skspJkCW4A8RvxWFK3mbZNu2jOe824gPY2Sg@mail.gmail.com>


Code Soldier1 writes:

> Hi,
>
> Can someone suggest what is the fastest way to build a minimal kernel
> and boot. For example if I am working on TCP and would like to make a
> small change and reboot, what is the fastest way, I rather not build
> the whole kernel.
>
> Thanks

FWIW, check this out if you want to have a setup to make
incremental changes to your kernel and test them out quickly.
It describes a quick and easy setup to test kernel changes on an
emulator without acutally rebooting your machine (helps with initial
testing)

http://www.mycpu.org/kernel-n00b-howto/

I use this setup for testing out small/quick changes. As mentioned
earlier in this thread, compilation for incremental changes should not
take long.

HTH.

-- 
Manoj

  reply	other threads:[~2017-04-25 13:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 15:59 What is the fastest way to build and boot a kernel Code Soldier1
2017-04-18 16:07 ` Greg KH
2017-04-18 17:38   ` Code Soldier1
2017-04-18 17:42     ` Peter Senna Tschudin
2017-04-18 17:44     ` Greg KH
2017-04-18 18:04       ` Code Soldier1
2017-04-18 18:15         ` Guru Das S
2017-04-25 13:15           ` Manoj [this message]
2017-04-19 10:32 ` Tobin C. Harding
2017-04-19 10:49   ` valdis.kletnieks at vt.edu
2017-04-19 12:43     ` Aruna Hewapathirane
2017-04-19 18:26   ` Code Soldier1
2017-04-20  8:21     ` Sébastien Masson
2017-04-20 16:20       ` Code Soldier1
2017-04-20 16:31         ` Alexander Kapshuk
2017-04-20 16:54           ` Joe Smith
2017-04-20 17:50             ` Bjørn Mork
2017-04-20 19:27               ` Joe Smith
2017-04-21  8:43                 ` Bjørn Mork
2017-04-19 11:24 ` Aruna Hewapathirane
2017-04-19 17:10 ` Stephen Brennan

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=878tmoljbh.fsf@manojrajarao.com \
    --to=linux@manojrajarao.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).