From: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org >>
\"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.15-rc1
Date: Mon, 21 Apr 2014 21:53:04 -0700 [thread overview]
Message-ID: <5355F5B0.6060703@nvidia.com> (raw)
Here are some basic Tegra test results for Linux v3.15-rc1.
Logs and other details at:
http://nvt.pwsan.com/pub/linux/testlogs/test_v3.15-rc1/20140413153108/
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.14 (455c6fdbd219161bd09b1165f11699d6d73de11c)):
text data bss total kernel
+330455 +103624 +6112 +440191 multi_v7_defconfig
+191148 +13528 +4472 +209148 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v3.14 (455c6fdbd219161bd09b1165f11699d6d73de11c))
avail rsrvd high freed board kconfig dtb
-49720k 49720k . 36k tegra114-dalmore-a04 multi_v7_defconfig tegra114-dalmore
-49500k 49500k . 12k tegra114-dalmore-a04 tegra_defconfig tegra114-dalmore
-49700k 49700k . 36k tegra30-beaver multi_v7_defconfig tegra30-beaver
-49480k 49480k . 12k tegra30-beaver tegra_defconfig tegra30-beaver
48 MiB of additional reserved memory? Ouch. I had to rub my eyes and doublecheck. It's the CMA allocation.
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.15-rc1
Date: Mon, 21 Apr 2014 21:53:04 -0700 [thread overview]
Message-ID: <5355F5B0.6060703@nvidia.com> (raw)
Here are some basic Tegra test results for Linux v3.15-rc1.
Logs and other details at:
http://nvt.pwsan.com/pub/linux/testlogs/test_v3.15-rc1/20140413153108/
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.14 (455c6fdbd219161bd09b1165f11699d6d73de11c)):
text data bss total kernel
+330455 +103624 +6112 +440191 multi_v7_defconfig
+191148 +13528 +4472 +209148 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v3.14 (455c6fdbd219161bd09b1165f11699d6d73de11c))
avail rsrvd high freed board kconfig dtb
-49720k 49720k . 36k tegra114-dalmore-a04 multi_v7_defconfig tegra114-dalmore
-49500k 49500k . 12k tegra114-dalmore-a04 tegra_defconfig tegra114-dalmore
-49700k 49700k . 36k tegra30-beaver multi_v7_defconfig tegra30-beaver
-49480k 49480k . 12k tegra30-beaver tegra_defconfig tegra30-beaver
48 MiB of additional reserved memory? Ouch. I had to rub my eyes and doublecheck. It's the CMA allocation.
next reply other threads:[~2014-04-22 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 4:53 Paul Walmsley [this message]
2014-04-22 4:53 ` Tegra baseline test results for v3.15-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=5355F5B0.6060703@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.