public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jonathanh@nvidia.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra baseline test results for v4.14-rc2
Date: Mon, 25 Sep 2017 15:29:21 +0100	[thread overview]
Message-ID: <dbdcc12f-b1fa-4160-1b96-32270a528eed@nvidia.com> (raw)

Tegra baseline test results for v4.14-rc2


Here are some basic Tegra test results for Linux v4.14-rc2.
Logs and other details at:

    https://nvtb.github.io//linux/test_v4.14-rc2/20170924170104/


Test summary
------------

Build: zImage:
    FAIL: ( 2/ 2): multi_v7_defconfig, tegra_defconfig

Build: Image:
    Pass: ( 1/ 1): defconfig

Boot to userspace: defconfig:
    Pass: ( 4/ 4): qemu-vexpress64, tegra132-norrin,
		   tegra210-p2371-0000, tegra210-smaug


vmlinux object size
(delta in bytes from test_v4.14-rc1 (2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e)):
   text     data      bss    total  kernel
  +3781    +1948        0    +5729  defconfig


Boot-time memory difference
(delta in bytes from test_v4.14-rc1 (2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e))
    avail    rsrvd     high    freed                board              kconfig                  dtb
     -64k      64k        .      64k      qemu-vexpress64            defconfig           __internal
     -64k      64k        .      64k      tegra132-norrin            defconfig      tegra132-norrin
     -64k      64k        .      64k  tegra210-p2371-0000            defconfig  tegra210-p2371-0000
     -64k      64k        .      64k       tegra210-smaug            defconfig       tegra210-smaug

--
nvpublic

             reply	other threads:[~2017-09-25 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 14:29 Jon Hunter [this message]
2017-09-25 14:41 ` Tegra baseline test results for v4.14-rc2 Jon Hunter

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=dbdcc12f-b1fa-4160-1b96-32270a528eed@nvidia.com \
    --to=jonathanh@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