From: Adam Zerella <adam.zerella@gmail.com>
To: CRISTIAN ANDRES VARGAS GONZALEZ <vargascristian@americana.edu.co>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Test the kernel code
Date: Sat, 5 Oct 2019 13:52:12 +1000 [thread overview]
Message-ID: <20191005035212.GA4397@gmail.com> (raw)
In-Reply-To: <CABfRCzh5=ah=JKZYXFdVGzpfWsJagodVKLNm4wKrDij-ocPgyw@mail.gmail.com>
On Fri, Oct 04, 2019 at 10:07:21PM -0500, CRISTIAN ANDRES VARGAS GONZALEZ wrote:
> Hello
>
> I am starting to develop the kernel and I have been compiling the kernel,
> now it has been compiling for some time now. When a patch is added, should
> everything be compiled again? Or is there a different way to test the code
> that has been written?
From what I understand you'll only have to build the _entire_ kernel
once and subsequent builds should be faster. The build process should
rebuild modules that have a detected change in them.
You may be able to build the kernel a bit faster by running the process
in parallel. make has an argument of `-j` where you can specify the number
of CPU cores to utilise, for example `make -j4` would build with 4 CPUs
in parallel.
To build an individual kernel module you can specify something like `make
M=drivers/staging/android/`.
Checkout (no pun intended) https://kernelnewbies.org/KernelBuild for more info.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-10-05 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 3:07 Test the kernel code CRISTIAN ANDRES VARGAS GONZALEZ
2019-10-05 3:52 ` Adam Zerella [this message]
2019-10-05 4:18 ` Valdis Klētnieks
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=20191005035212.GA4397@gmail.com \
--to=adam.zerella@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=vargascristian@americana.edu.co \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.