From: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org
Subject: Tegra baseline test results for v3.13-rc1
Date: Mon, 25 Nov 2013 11:19:03 -0800 [thread overview]
Message-ID: <5293A2A7.6060100@nvidia.com> (raw)
Here are some basic Tegra test results for Linux v3.13-rc1.
Logs and other details at:
http://nvt.pwsan.com/pub/linux/testlogs/test_v3.13-rc1/20131125105015/
Test summary
------------
Build: zImage:
Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
Boot to userspace: multi_v7_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-headless, tegra30-beaver
Boot to userspace: tegra_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-headless, tegra30-beaver
vmlinux object size
(delta in bytes from test_v3.12 (test_v3.12)):
text data bss total kernel
-458712 +3432 +5624 -449656 multi_v7_defconfig
-420983 +856 +4564 -415563 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v3.12 (test_v3.12))
avail rsrvd high freed board kconfig dtb
416k -416k . -4k tegra114-dalmore-hea multi_v7_defconfig tegra114-dalmore
392k -392k . 8k tegra114-dalmore-hea tegra_defconfig tegra114-dalmore
428k -428k . -4k tegra30-beaver multi_v7_defconfig tegra30-beaver
404k -404k . 8k tegra30-beaver tegra_defconfig tegra30-beaver
The large size deltas are due to a toolchain switchover from CodeSourcery 2010.09 to Ubuntu/Linaro 4.6.3-1ubuntu5.
I'd expect that if the toolchain remained the same, the size deltas would be similar to the OMAP deltas:
http://www.pwsan.com/omap/testlogs/test_v3.13-rc1/20131124223225/README.txt
This toolchain probably won't stay in use for very long here.
(Since this is a mainline kernel test, in my view, the primary test toolchain should also be mainline gcc/binutils.)
WARNING: multiple messages have this Message-ID (diff)
From: pwalmsley@nvidia.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra baseline test results for v3.13-rc1
Date: Mon, 25 Nov 2013 11:19:03 -0800 [thread overview]
Message-ID: <5293A2A7.6060100@nvidia.com> (raw)
Here are some basic Tegra test results for Linux v3.13-rc1.
Logs and other details at:
http://nvt.pwsan.com/pub/linux/testlogs/test_v3.13-rc1/20131125105015/
Test summary
------------
Build: zImage:
Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
Boot to userspace: multi_v7_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-headless, tegra30-beaver
Boot to userspace: tegra_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-headless, tegra30-beaver
vmlinux object size
(delta in bytes from test_v3.12 (test_v3.12)):
text data bss total kernel
-458712 +3432 +5624 -449656 multi_v7_defconfig
-420983 +856 +4564 -415563 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v3.12 (test_v3.12))
avail rsrvd high freed board kconfig dtb
416k -416k . -4k tegra114-dalmore-hea multi_v7_defconfig tegra114-dalmore
392k -392k . 8k tegra114-dalmore-hea tegra_defconfig tegra114-dalmore
428k -428k . -4k tegra30-beaver multi_v7_defconfig tegra30-beaver
404k -404k . 8k tegra30-beaver tegra_defconfig tegra30-beaver
The large size deltas are due to a toolchain switchover from CodeSourcery 2010.09 to Ubuntu/Linaro 4.6.3-1ubuntu5.
I'd expect that if the toolchain remained the same, the size deltas would be similar to the OMAP deltas:
http://www.pwsan.com/omap/testlogs/test_v3.13-rc1/20131124223225/README.txt
This toolchain probably won't stay in use for very long here.
(Since this is a mainline kernel test, in my view, the primary test toolchain should also be mainline gcc/binutils.)
next reply other threads:[~2013-11-25 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:19 Paul Walmsley [this message]
2013-11-25 19:19 ` Tegra baseline test results for v3.13-rc1 Paul Walmsley
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=5293A2A7.6060100@nvidia.com \
--to=pwalmsley-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.