From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "Hart, Darren" <darren.hart@intel.com>
Subject: [PATCH] kernel: Use hardlinks for do_populate_sysroot for speed
Date: Fri, 08 Nov 2013 15:18:00 +0000 [thread overview]
Message-ID: <1383923880.2345.4.camel@ted> (raw)
The kernel tree is large and doesn't need to be copied. Override
the default sysroot handling function to use a hardlink copying
function in python.
This commit also drops the copying of the /lib directory which
just contains the kernel modules. We never use those in the sysroot
so there is little point in carrying those around.
For linux-yocto this takes the do_populate_sysroot time 24s -> 14s.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 0b6360f..e793ccb 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -308,8 +308,8 @@ kernelscripts_sstate_postinst () {
fi
}
-sysroot_stage_all_append() {
- sysroot_stage_dir ${D}${KERNEL_SRC_PATH} ${SYSROOT_DESTDIR}${KERNEL_SRC_PATH}
+python sysroot_stage_all () {
+ oe.path.copyhardlinktree(d.expand("${D}${KERNEL_SRC_PATH}"), d.expand("${SYSROOT_DESTDIR}${KERNEL_SRC_PATH}"))
}
kernel_do_configure() {
next reply other threads:[~2013-11-08 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 15:18 Richard Purdie [this message]
2013-11-08 15:41 ` [PATCH] kernel: Use hardlinks for do_populate_sysroot for speed Bruce Ashfield
2013-11-08 15:54 ` Hans Beckérus
2013-11-08 15:55 ` Richard Purdie
2013-11-08 15:59 ` Bruce Ashfield
2013-11-08 16:50 ` Richard Purdie
2013-11-08 17:23 ` Hart, Darren
2013-11-09 20:38 ` Andrea Adami
2013-11-09 22:58 ` Richard Purdie
2013-11-11 8:06 ` Hans Beckérus
2013-11-11 9:35 ` Richard Purdie
2013-11-11 9:45 ` Richard Purdie
2013-11-11 9:47 ` Hans Beckérus
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=1383923880.2345.4.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=darren.hart@intel.com \
--cc=openembedded-core@lists.openembedded.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