linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pwalmsley@nvidia.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra baseline test results for v3.11-rc4
Date: Tue, 6 Aug 2013 11:32:05 -0700	[thread overview]
Message-ID: <52014125.7010003@nvidia.com> (raw)

Here are some basic Tegra test results for Linux v3.11-rc4.
Logs and other details at:

     http://nvt.pwsan.com/pub/linux/testlogs/test_v3.11-rc4/20130806092219/

Special thanks to Jon Hunter for pointing out that the column order
of the boot time memory consumption report headings didn't match the
data, in previous reports.


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.11-rc3 (5ae90d8e467e625e447000cb4335c4db973b1095)):
    text     data      bss    total  kernel
   +1916       -8        0    +1908  multi_v7_defconfig
    +944      -72      +64     +936  tegra_defconfig


Boot-time memory difference
(delta in bytes from test_v3.11-rc3 (5ae90d8e467e625e447000cb4335c4db973b1095))
     avail    rsrvd     high    freed                board              kconfig                  dtb
       -4k       4k        .        . tegra114-dalmore-hea   multi_v7_defconfig     tegra114-dalmore
      -12k      12k        .        . tegra114-dalmore-hea      tegra_defconfig     tegra114-dalmore
       -4k       4k        .        .       tegra30-beaver   multi_v7_defconfig       tegra30-beaver
      -12k      12k        .        .       tegra30-beaver      tegra_defconfig       tegra30-beaver

                 reply	other threads:[~2013-08-06 18:32 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=52014125.7010003@nvidia.com \
    --to=pwalmsley@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).