From: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: "linux-tegra >>
\"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.12-rc6
Date: Sat, 19 Oct 2013 23:41:52 -0700 [thread overview]
Message-ID: <52637B30.7000203@nvidia.com> (raw)
Here are some basic Tegra test results for Linux v3.12-rc6.
Logs and other details at:
http://nvt.pwsan.com/pub/linux/testlogs/test_v3.12-rc6/20131019232523/
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-rc5 (61e6cfa80de5760bbe406f4e815b7739205754d2)):
text data bss total kernel
-168 +64 -768 -872 multi_v7_defconfig
-1781 -8 -704 -2493 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v3.12-rc5 (61e6cfa80de5760bbe406f4e815b7739205754d2))
avail rsrvd high freed board kconfig dtb
. . . . tegra114-dalmore-hea multi_v7_defconfig tegra114-dalmore
8k -8k . . tegra114-dalmore-hea tegra_defconfig tegra114-dalmore
. . . . tegra30-beaver multi_v7_defconfig tegra30-beaver
8k -8k . . tegra30-beaver tegra_defconfig tegra30-beaver
reply other threads:[~2013-10-20 6:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52637B30.7000203@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox