From: Jan Viktorin <viktorin@rehivetech.com>
To: "Hunt, David" <david.hunt@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK ArmV7 autotests
Date: Mon, 9 Nov 2015 18:12:24 +0100 [thread overview]
Message-ID: <20151109181224.21e5ebda@pcviktorin.fit.vutbr.cz> (raw)
In-Reply-To: <5640CB56.4080506@intel.com>
Hello David,
I am working on some auto test in QEMU. My last result for ARMv7 is
following bellow. What is strange, I could see that the read/write lock
autotest failed (wrong order) before.
I have no idea what does it mean "no prompt". I suppose that such test
could not be run for some reason...
I had to slightly modify the autotest.py to run properly.
The test was executed in qemu:
qemu-system-arm -M vexpress-a9 -kernel zImage \
-dtb vexpress-v2p-ca9.dtb -drive file=rootfs.ext2,if=sd \
-append "console=ttyAMA0 root=/dev/mmcblk0 rw" -smp 4 -m 512 -nographic
with the Linux Kernel 4.2.
Test name Test result Test Total
================================================================================
Bits 55-60 of /proc/PID/pagemap entries are about to stop being page-shift some time soon. See the linux/Documentation/vm/pagemap.txt for details.
Start group_1: Success [00m 08s]
Timer autotest: Success [00m 52s]
Debug autotest: Success [00m 01s]
Errno autotest: Success [00m 00s]
Meter autotest: Success [00m 01s]
Common autotest: Success [00m 28s]
Dump log history: Success [00m 00s]
Dump rings: Success [00m 00s]
Dump mempools: Success [00m 00s] [01m 34s]
Start group_2: Success [00m 00s]
Memory autotest: Success [00m 01s]
Read/write lock autotest: Success [00m 00s]
Logs autotest: Success [00m 00s]
CPU flags autotest: Success [00m 00s]
Version autotest: Success [00m 00s]
EAL filesystem autotest: Success [00m 00s]
EAL flags autotest: Fail [00m 00s]
Hash autotest: Fail [00m 00s] [01m 38s]
Start group_3: Fail [No prompt] [00m 00s]
LPM autotest: Fail [No prompt] [00m 00s]
IVSHMEM autotest: Fail [No prompt] [00m 00s]
Memcpy autotest: Fail [No prompt] [00m 00s]
Memzone autotest: Fail [No prompt] [00m 00s]
String autotest: Fail [No prompt] [00m 00s]
Alarm autotest: Fail [No prompt] [00m 00s] [01m 39s]
Start group_4: Success [00m 00s]
PCI autotest: Fail [00m 00s]
Malloc autotest: Success [00m 12s]
Multi-process autotest: Fail [00m 01s]
Mbuf autotest: Success [02m 18s]
Per-lcore autotest: Success [00m 05s]
Ring autotest: Success [00m 02s] [04m 19s]
Start group_5: Success [00m 00s]
Spinlock autotest: Success [00m 15s]
Byte order autotest: Success [00m 00s]
TAILQ autotest: Success [00m 00s]
Command-line autotest: Success [00m 00s]
Interrupts autotest: Success [00m 08s] [04m 45s]
Start group_6: Fail [No prompt] [00m 00s]
Function reentrancy autotest: Fail [No prompt] [00m 00s]
Mempool autotest: Fail [No prompt] [00m 00s]
Atomics autotest: Fail [No prompt] [00m 00s]
Prefetch autotest: Fail [No prompt] [00m 00s]
Red autotest: Fail [No prompt] [00m 00s] [04m 45s]
Start group_7: Success [00m 00s]
PMD ring autotest: Fail [00m 00s]
Access list control autotest: Fail [Not found] [00m 00s]
Sched autotest: Success [00m 00s] [04m 48s]
Start kni: Fail [No prompt] [00m 00s]
KNI autotest: Fail [No prompt] [00m 00s] [04m 48s]
Start mempool_perf: Success [00m 00s]
Cycles autotest: Success [00m 01s]
Mempool performance autotest: Fail [Timeout] [15m 00s] [19m 50s]
Start memcpy_perf: Fail [No prompt] [00m 00s]
Memcpy performance autotest: Fail [No prompt] [00m 00s] [19m 50s]
Start hash_perf: Fail [No prompt] [00m 00s]
Hash performance autotest: Fail [No prompt] [00m 00s] [19m 51s]
Start power: Fail [No prompt] [00m 00s]
Power autotest: Fail [No prompt] [00m 00s] [19m 51s]
Start power_acpi_cpufreq: Fail [No prompt] [00m 00s]
Power ACPI cpufreq autotest: Fail [No prompt] [00m 00s] [19m 52s]
Start power_kvm_vm: Fail [No prompt] [00m 00s]
Power KVM VM autotest: Fail [No prompt] [00m 00s] [19m 52s]
Start lpm6: Fail [No prompt] [00m 00s]
LPM6 autotest: Fail [No prompt] [00m 00s] [19m 52s]
Start timer_perf: Fail [No prompt] [00m 00s]
Timer performance autotest: Fail [No prompt] [00m 00s] [19m 53s]
Start ring_perf: Fail [No prompt] [00m 00s]
Ring performance autotest: Fail [No prompt] [00m 00s] [19m 53s]
================================================================================
Total run time: 19m 53s
Number of failed tests: 27
=============================
Regards
Jan
On Mon, 9 Nov 2015 16:35:34 +0000
"Hunt, David" <david.hunt@intel.com> wrote:
> Jan,
> I'm running some of the autotests, and I've got the following
> passes/fails. Have you run any of the failing tests on your platform? Do
> they pass?
> Dave.
>
> dpdk# make -C arm-armv7a-linuxapp-gcc fast_test
> Test name Test result Test Total
> =================================================================
> Timer autotest: Success [00m 42s]
> Debug autotest: Success [00m 00s]
> Errno autotest: Success [00m 00s]
> Meter autotest: Success [00m 00s]
> Common autotest: Success [00m 03s]
> Dump log history: Success [00m 00s]
> Dump rings: Success [00m 00s]
> Dump mempools: Success [00m 00s] [00m 50s]
> Memory autotest: Success [00m 00s]
> Read/write lock autotest: Success [00m 00s]
> Logs autotest: Success [00m 00s]
> CPU flags autotest: Success [00m 00s]
> Version autotest: Success [00m 00s]
> EAL filesystem autotest: Success [00m 00s]
> EAL flags autotest: Fail [Broken Test]
> Hash autotest: Fail [00m 00s] [00m 53s]
> LPM autotest: Fail [Not found] [00m 00s]
> IVSHMEM autotest: Fail [Not found] [00m 00s]
> Memcpy autotest: Success [00m 51s]
> Memzone autotest: Fail [00m 00s]
> String autotest: Success [00m 00s]
> Alarm autotest: Success [00m 16s] [02m 03s]
> PCI autotest: Fail [No PCI present]
> Malloc autotest: Success [00m 04s]
> Multi-process autotest: Fail [No PCI present]
> Mbuf autotest: Success [01m 00s]
> Per-lcore autotest: Success [00m 05s]
> Ring autotest: Success [00m 02s] [03m 21s]
> Spinlock autotest: Success [00m 15s]
> Byte order autotest: Success [00m 00s]
> TAILQ autotest: Success [00m 00s]
> Command-line autotest: Success [00m 00s]
> Interrupts autotest: Success [00m 08s] [03m 48s]
> Function reentrancy autotest: Success [00m 00s]
> Mempool autotest: Success (Manual Execution)
> Atomics autotest: Success [00m 00s]
> Prefetch autotest: Success [00m 00s]
> Red autotest: Success [07m 22s] [11m 13s]
> PMD ring autotest: N/A Needs port
> Sched autotest: Success [00m 00s] [11m 16s]
> Cycles autotest: Success [00m 01s] [11m 21s]
> Power autotest: Success [00m 00s] [11m 23s]
> Power ACPI cpufreq autotest: Success [00m 00s] [11m 25s]
> ====================================================================
--
Jan Viktorin E-mail: Viktorin@RehiveTech.com
System Architect Web: www.RehiveTech.com
RehiveTech
Brno, Czech Republic
next parent reply other threads:[~2015-11-09 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5640CB56.4080506@intel.com>
2015-11-09 17:12 ` Jan Viktorin [this message]
2015-11-09 17:26 ` Hunt, David
2015-11-09 17:46 ` Jan Viktorin
2015-11-10 10:22 ` Hunt, David
2015-11-10 10:30 ` Thomas Monjalon
2015-11-10 12:45 ` Jerin Jacob
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=20151109181224.21e5ebda@pcviktorin.fit.vutbr.cz \
--to=viktorin@rehivetech.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.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).