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"
<kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org>
Subject: Tegra baseline test results for v3.14-rc1
Date: Thu, 27 Feb 2014 02:37:40 -0800 [thread overview]
Message-ID: <530F1574.3020006@nvidia.com> (raw)
Here are some basic Tegra test results for Linux v3.14-rc1.
Logs and other details at:
http://nvt.pwsan.com/pub/linux/testlogs/test_v3.14-rc1/20140227022109/
Test summary
------------
Build: zImage:
Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
Boot to userspace: multi_v7_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-a04, tegra30-beaver
Boot to userspace: tegra_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-a04, tegra30-beaver
vmlinux object size
(delta in bytes from test_v3.13 (d8ec26d7f8287f5788a494f56e8814210f0e64be)):
text data bss total kernel
+1833734 +109664 -460 +1942938 multi_v7_defconfig
+170871 +23512 -6616 +187767 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v3.13 (d8ec26d7f8287f5788a494f56e8814210f0e64be))
avail rsrvd high freed board kconfig dtb
. . . . tegra114-dalmore-a04 multi_v7_defconfig tegra114-dalmore
. . . . tegra114-dalmore-a04 tegra_defconfig tegra114-dalmore
-2070932k -25196k -1317888k -472k tegra114-dalmore-hea multi_v7_defconfig tegra114-dalmore
-2053808k -42320k -1317888k -244k tegra114-dalmore-hea tegra_defconfig tegra114-dalmore
-18320k 18320k . 36k tegra30-beaver multi_v7_defconfig tegra30-beaver
-168k 168k . 4k tegra30-beaver tegra_defconfig tegra30-beaver
The tegra114-dalmore-headless board, an A03 Dalmore, was dropped out of the testbed
since apparently NVIDIA folks don't maintain upstream support for any Dalmore revision
other than A04. That's the cause of the large boot-time memory deltas above.
It's been replaced by an A04 Dalmore. There should have been large boot-time memory
deltas on the A04 lines too, but the current set of scripts don't handle that condition well.
I double-checked the +1.9MB size increase for the multi_v7_defconfig kernel, and it appears
to be accurate :-(
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.14-rc1
Date: Thu, 27 Feb 2014 02:37:40 -0800 [thread overview]
Message-ID: <530F1574.3020006@nvidia.com> (raw)
Here are some basic Tegra test results for Linux v3.14-rc1.
Logs and other details at:
http://nvt.pwsan.com/pub/linux/testlogs/test_v3.14-rc1/20140227022109/
Test summary
------------
Build: zImage:
Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
Boot to userspace: multi_v7_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-a04, tegra30-beaver
Boot to userspace: tegra_defconfig:
Pass: ( 2/ 2): tegra114-dalmore-a04, tegra30-beaver
vmlinux object size
(delta in bytes from test_v3.13 (d8ec26d7f8287f5788a494f56e8814210f0e64be)):
text data bss total kernel
+1833734 +109664 -460 +1942938 multi_v7_defconfig
+170871 +23512 -6616 +187767 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v3.13 (d8ec26d7f8287f5788a494f56e8814210f0e64be))
avail rsrvd high freed board kconfig dtb
. . . . tegra114-dalmore-a04 multi_v7_defconfig tegra114-dalmore
. . . . tegra114-dalmore-a04 tegra_defconfig tegra114-dalmore
-2070932k -25196k -1317888k -472k tegra114-dalmore-hea multi_v7_defconfig tegra114-dalmore
-2053808k -42320k -1317888k -244k tegra114-dalmore-hea tegra_defconfig tegra114-dalmore
-18320k 18320k . 36k tegra30-beaver multi_v7_defconfig tegra30-beaver
-168k 168k . 4k tegra30-beaver tegra_defconfig tegra30-beaver
The tegra114-dalmore-headless board, an A03 Dalmore, was dropped out of the testbed
since apparently NVIDIA folks don't maintain upstream support for any Dalmore revision
other than A04. That's the cause of the large boot-time memory deltas above.
It's been replaced by an A04 Dalmore. There should have been large boot-time memory
deltas on the A04 lines too, but the current set of scripts don't handle that condition well.
I double-checked the +1.9MB size increase for the multi_v7_defconfig kernel, and it appears
to be accurate :-(
next reply other threads:[~2014-02-27 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 10:37 Paul Walmsley [this message]
2014-02-27 10:37 ` Tegra baseline test results for v3.14-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=530F1574.3020006@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.