* Re: [dpdk-dev] DPDK ArmV7 autotests
[not found] <5640CB56.4080506@intel.com>
@ 2015-11-09 17:12 ` Jan Viktorin
2015-11-09 17:26 ` Hunt, David
0 siblings, 1 reply; 6+ messages in thread
From: Jan Viktorin @ 2015-11-09 17:12 UTC (permalink / raw)
To: Hunt, David; +Cc: dev
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] DPDK ArmV7 autotests
2015-11-09 17:12 ` [dpdk-dev] DPDK ArmV7 autotests Jan Viktorin
@ 2015-11-09 17:26 ` Hunt, David
2015-11-09 17:46 ` Jan Viktorin
0 siblings, 1 reply; 6+ messages in thread
From: Hunt, David @ 2015-11-09 17:26 UTC (permalink / raw)
To: Jan Viktorin; +Cc: dev
On 09/11/2015 17:12, Jan Viktorin wrote:
> 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...
The no prompt occurs when the 'test' binary (which is used to run each
autotest in turn) exits before it gets to the prompt, so the test cannot
be run. Usually this is because of lack of resources such as memory, PCI
or similar. I had to reduce the memory requirements from 1024M to 512M
to get one section of tests to pass (in autotest_data.py).
For more information on why the autotests are failing, you can check the
log file in the directory for that autotest run -
arm-armv7a-linux-app-gcc/autotest-date/arm-armv7a-linuxapp-gcc.log
>
> 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]
>> ====================================================================
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] DPDK ArmV7 autotests
2015-11-09 17:26 ` Hunt, David
@ 2015-11-09 17:46 ` Jan Viktorin
2015-11-10 10:22 ` Hunt, David
0 siblings, 1 reply; 6+ messages in thread
From: Jan Viktorin @ 2015-11-09 17:46 UTC (permalink / raw)
To: Hunt, David; +Cc: dev
Here is the log. You an see, that many tests fail just because
of the missing hugetlb support. This is strange as I modified the
autotest_runner.py to inject "--no-huge --no-pci" options when it
detects armv7 architecture.
Moreover, the mempool performance test does not say OK. It is marked as
Timeout in the CSV.
Summary
Target: armv7l-unknown-4.2.0
Tests: 52
Failed tests: 27
==================== group_1
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: TSC frequency is ~999784 KHz
EAL: Master lcore 0 is ready (tid=76f89000;cpuset=[0])
EAL: lcore 1 is ready (tid=75bc82c0;cpuset=[1])
EAL: lcore 3 is ready (tid=74bc82c0;cpuset=[3])
EAL: lcore 2 is ready (tid=753c82c0;cpuset=[2])
APP: HPET is not enabled, using TSC as default timer
-------------------- Timer autotest
Test OK
Test OK
-------------------- Debug autotest
Test OK
-------------------- Errno autotest
Test OK
-------------------- Meter autotest
Test OK
-------------------- Common autotest
Test OK
-------------------- Dump log history
dump_log_history
-------------------- Dump rings
dump_ring
-------------------- Dump mempools
dump_mempool
==================== group_2
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: TSC frequency is ~999984 KHz
EAL: Master lcore 0 is ready (tid=76f23000;cpuset=[0])
EAL: lcore 1 is ready (tid=723622c0;cpuset=[1])
EAL: lcore 2 is ready (tid=71b622c0;cpuset=[2])
EAL: lcore 3 is ready (tid=713622c0;cpuset=[3])
APP: HPET is not enabled, using TSC as default timer
-------------------- Memory autotest
Test OK
-------------------- Read/write lock autotest
Test OK
-------------------- Logs autotest
Test OK
-------------------- CPU flags autotest
Test OK
-------------------- Version autotest
Test OK
-------------------- EAL filesystem autotest
Test OK
-------------------- EAL flags autotest
eal_flags_autotest
eal_flags_autotest
Running binary with argv[]:'/usr/dpdk/test' '--file-prefix=uxv' '--proc-type=secondary' '-n' '3'
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
PANIC in rte_eal_config_attach():
Cannot open '/var/run/.uxv_config' for rte_mem_config
Error - process did not run ok when missing -c flag
Error in test_missing_c_flag()
Test Failed
-------------------- Hash autotest
hash_autotest
hash_autotest
# Testing hash creation with invalid parameters - expect error msgs
ERROR line 795: fbk hash creation should have failed
Test Failed
==================== group_3
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== group_4
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: TSC frequency is ~999942 KHz
EAL: Master lcore 0 is ready (tid=76f18000;cpuset=[0])
EAL: lcore 1 is ready (tid=6e3572c0;cpuset=[1])
EAL: lcore 2 is ready (tid=6db572c0;cpuset=[2])
EAL: lcore 3 is ready (tid=6d3572c0;cpuset=[3])
APP: HPET is not enabled, using TSC as default timer
-------------------- PCI autotest
pci_autotest
pci_autotest
Dump all devices
Scan bus
no device detected
Test Failed
-------------------- Malloc autotest
Test OK
-------------------- Multi-process autotest
multiprocess_autotest
multiprocess_autotest
=== Running pre-requisite test of test_pci
Dump all devices
Scan bus
no device detected
=== Requisite test done
Running binary with argv[]:'/usr/dpdk/test' '-c' '1' '--proc-type=secondary' '--file-prefix=uxv'
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
PANIC in rte_eal_config_attach():
Cannot open '/var/run/.uxv_config' for rte_mem_config
Running binary with argv[]:'/usr/dpdk/test' '-c' '1' '--proc-type=auto' '--file-prefix=uxv'
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Auto-detected process type: PRIMARY
PANIC in eal_hugepage_info_init():
Cannot open directory /sys/kernel/mm/hugepages to read system hugepage info
Running binary with argv[]:'/usr/dpdk/test' '-c' '1' '--proc-type=ERROR' '--file-prefix=uxv'
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Invalid process type specified
Usage: /usr/dpdk/test [options]
EAL common options:
-c COREMASK Hexadecimal bitmask of cores to run on
-l CORELIST List of cores to run on
The argument format is <c1>[-c2][,c3[-c4],...]
where c1, c2, etc are core indexes between 0 and 128
--lcores COREMAP Map lcore set to physical cpu set
The argument format is
'<lcores[@cpus]>[<,lcores[@cpus]>...]'
lcores and cpus list are grouped by '(' and ')'
Within the group, '-' is used for range separator,
',' is used for single number separator.
'( )' can be omitted for single element group,
'@' can be omitted if cpus and lcores have the same value
--master-lcore ID Core ID that is used as master
-n CHANNELS Number of memory channels
-m MB Memory to allocate (see also --socket-mem)
-r RANKS Force number of memory ranks (don't detect)
-b, --pci-blacklist Add a PCI device in black list.
Prevent EAL from using this PCI device. The argument
format is <domain:bus:devid.func>.
-w, --pci-whitelist Add a PCI device in white list.
Only use the specified PCI devices. The argument format
is <[domain:]bus:devid.func>. This option can be present
several times (once per device).
[NOTE: PCI whitelist cannot be used with -b option]
--vdev Add a virtual device.
The argument format is <driver><id>[,key=val,...]
(ex: --vdev=eth_pcap0,iface=eth2).
--vmware-tsc-map Use VMware TSC map instead of native RDTSC
--proc-type Type of this process (primary|secondary|auto)
--syslog Set syslog facility
--log-level Set default log level
-v Display version information on startup
-h, --help This help
EAL options for DEBUG use only:
--huge-unlink Unlink hugepage files after init
--no-huge Use malloc instead of hugetlbfs
--no-pci Disable PCI
--no-hpet Disable HPET
--no-shconf No shared config (mmap'd files)
EAL Linux options:
-d LIB.so Add driver (can be used multiple times)
--socket-mem Memory to allocate on sockets (comma separated values)
--huge-dir Directory where hugetlbfs is mounted
--file-prefix Prefix for hugepage filenames
--base-virtaddr Base virtual address
--create-uio-dev Create /dev/uioX (usually done by hotplug)
--vfio-intr Interrupt mode for VFIO (legacy|msi|msix)
--xen-dom0 Support running on Xen dom0 without hugetlbfs
Running binary with argv[]:'/usr/dpdk/test' '-c' '1' '--proc-type=secondary' '--file-prefix=ERROR'
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
PANIC in rte_eal_config_attach():
Cannot open '/var/run/.ERROR_config' for rte_mem_config
Test Failed
-------------------- Mbuf autotest
Test OK
-------------------- Per-lcore autotest
Test OK
-------------------- Ring autotest
Test OK
==================== group_5
Test OK
-------------------- Byte order autotest
Test OK
-------------------- TAILQ autotest
Test OK
-------------------- Command-line autotest
Test OK
-------------------- Interrupts autotest
Test OK
==================== group_6
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== group_7
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: TSC frequency is ~999972 KHz
EAL: Master lcore 0 is ready (tid=76fc1000;cpuset=[0])
EAL: lcore 1 is ready (tid=5d4002c0;cpuset=[1])
EAL: lcore 2 is ready (tid=5cc002c0;cpuset=[2])
EAL: lcore 3 is ready (tid=5c4002c0;cpuset=[3])
APP: HPET is not enabled, using TSC as default timer
-------------------- PMD ring autotest
ring_pmd_autotest
ring_pmd_autotest
Configure failed for TX port
Test Failed
-------------------- Access list control autotest
acl_autotest
acl_autotest
Command not found
-------------------- Sched autotest
Test OK
==================== kni
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== mempool_perf
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: TSC frequency is ~999968 KHz
EAL: Master lcore 0 is ready (tid=76fa1000;cpuset=[0])
EAL: lcore 1 is ready (tid=663e02c0;cpuset=[1])
EAL: lcore 2 is ready (tid=65be02c0;cpuset=[2])
EAL: lcore 3 is ready (tid=653e02c0;cpuset=[3])
APP: HPET is not enabled, using TSC as default timer
-------------------- Cycles autotest
Test OK
-------------------- Mempool performance autotest
mempool_perf_autotest
mempool_perf_autotest
start performance test (without cache)
mempool_autotest cache=0 cores=1 n_get_bulk=1 n_put_bulk=1 n_keep=32 rate_persec=1481113
mempool_autotest cache=0 cores=1 n_get_bulk=1 n_put_bulk=1 n_keep=128 rate_persec=1114112
mempool_autotest cache=0 cores=1 n_get_bulk=1 n_put_bulk=4 n_keep=32 rate_persec=1900544
mempool_autotest cache=0 cores=1 n_get_bulk=1 n_put_bulk=4 n_keep=128 rate_persec=2883584
mempool_autotest cache=0 cores=1 n_get_bulk=1 n_put_bulk=32 n_keep=32 rate_persec=3748659
mempool_autotest cache=0 cores=1 n_get_bulk=1 n_put_bulk=32 n_keep=128 rate_persec=3040870
mempool_autotest cache=0 cores=1 n_get_bulk=4 n_put_bulk=1 n_keep=32 rate_persec=2398617
mempool_autotest cache=0 cores=1 n_get_bulk=4 n_put_bulk=1 n_keep=128 rate_persec=2555904
mempool_autotest cache=0 cores=1 n_get_bulk=4 n_put_bulk=4 n_keep=32 rate_persec=8296857
mempool_autotest cache=0 cores=1 n_get_bulk=4 n_put_bulk=4 n_keep=128 rate_persec=7208960
mempool_autotest cache=0 cores=1 n_get_bulk=4 n_put_bulk=32 n_keep=32 rate_persec=9502720
mempool_autotest cache=0 cores=1 n_get_bulk=4 n_put_bulk=32 n_keep=128 rate_persec=9673113
mempool_autotest cache=0 cores=1 n_get_bulk=32 n_put_bulk=1 n_keep=32 rate_persec=2411724
mempool_autotest cache=0 cores=1 n_get_bulk=32 n_put_bulk=1 n_keep=128 rate_persec=2673868
mempool_autotest cache=0 cores=1 n_get_bulk=32 n_put_bulk=4 n_keep=32 rate_persec=15741747
mempool_autotest cache=0 cores=1 n_get_bulk=32 n_put_bulk=4 n_keep=128 rate_persec=16960716
mempool_autotest cache=0 cores=1 n_get_bulk=32 n_put_bulk=32 n_keep=32 rate_persec=32597606
mempool_autotest cache=0 cores=1 n_get_bulk=32 n_put_bulk=32 n_keep=128 rate_persec=25493504
mempool_autotest cache=0 cores=2 n_get_bulk=1 n_put_bulk=1 n_keep=32 rate_persec=26214
mempool_autotest cache=0 cores=2 n_get_bulk=1 n_put_bulk=1 n_keep=128 rate_persec=39321
mempool_autotest cache=0 cores=2 n_get_bulk=1 n_put_bulk=4 n_keep=32 rate_persec=39321
mempool_autotest cache=0 cores=2 n_get_bulk=1 n_put_bulk=4 n_keep=128 rate_persec=65535
mempool_autotest cache=0 cores=2 n_get_bulk=1 n_put_bulk=32 n_keep=32 rate_persec=78642
mempool_autotest cache=0 cores=2 n_get_bulk=1 n_put_bulk=32 n_keep=128 rate_persec=104856
mempool_autotest cache=0 cores=2 n_get_bulk=4 n_put_bulk=1 n_keep=32 rate_persec=52428
mempool_autotest cache=0 cores=2 n_get_bulk=4 n_put_bulk=1 n_keep=128 rate_persec=26214
mempool_autotest cache=0 cores=2 n_get_bulk=4 n_put_bulk=4 n_keep=32 rate_persec=104857
mempool_autotest cache=0 cores=2 n_get_bulk=4 n_put_bulk=4 n_keep=128 rate_persec=52428
mempool_autotest cache=0 cores=2 n_get_bulk=4 n_put_bulk=32 n_keep=32 rate_persec=235928
mempool_autotest cache=0 cores=2 n_get_bulk=4 n_put_bulk=32 n_keep=128 rate_persec=117964
mempool_autotest cache=0 cores=2 n_get_bulk=32 n_put_bulk=1 n_keep=32 rate_persec=52428
mempool_autotest cache=0 cores=2 n_get_bulk=32 n_put_bulk=1 n_keep=128 rate_persec=39321
mempool_autotest cache=0 cores=2 n_get_bulk=32 n_put_bulk=4 n_keep=32 rate_persec=262144
mempool_autotest cache=0 cores=2 n_get_bulk=32 n_put_bulk=4 n_keep=128 rate_persec=117964
mempool_autotest cache=0 cores=2 n_get_bulk=32 n_put_bulk=32 n_keep=32 rate_persec=471858
mempool_autotest cache=0 cores=2 n_get_bulk=32 n_put_bulk=32 n_keep=128 rate_persec=262143
==================== memcpy_perf
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== hash_perf
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== power
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== power_acpi_cpufreq
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== power_kvm_vm
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== lpm6
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== timer_perf
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
==================== ring_perf
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: rte_eal_hugepage_init: mmap() failed: Cannot allocate memory
PANIC in rte_eal_init():
Cannot init memory
Regards
Jan
On Mon, 9 Nov 2015 17:26:21 +0000
"Hunt, David" <david.hunt@intel.com> wrote:
> On 09/11/2015 17:12, Jan Viktorin wrote:
> > 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...
>
> The no prompt occurs when the 'test' binary (which is used to run each
> autotest in turn) exits before it gets to the prompt, so the test cannot
> be run. Usually this is because of lack of resources such as memory, PCI
> or similar. I had to reduce the memory requirements from 1024M to 512M
> to get one section of tests to pass (in autotest_data.py).
>
> For more information on why the autotests are failing, you can check the
> log file in the directory for that autotest run -
> arm-armv7a-linux-app-gcc/autotest-date/arm-armv7a-linuxapp-gcc.log
>
>
> >
> > 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] DPDK ArmV7 autotests
2015-11-09 17:46 ` Jan Viktorin
@ 2015-11-10 10:22 ` Hunt, David
2015-11-10 10:30 ` Thomas Monjalon
0 siblings, 1 reply; 6+ messages in thread
From: Hunt, David @ 2015-11-10 10:22 UTC (permalink / raw)
To: Jan Viktorin; +Cc: dev
On 09/11/2015 17:46, Jan Viktorin wrote:
> Here is the log. You an see, that many tests fail just because
> of the missing hugetlb support. This is strange as I modified the
> autotest_runner.py to inject "--no-huge --no-pci" options when it
> detects armv7 architecture.
I think publishing these test results to the mailing list confuses
matters somewhat. The tests are not tuned for armv7, and there are many
false negatives, giving the impression that the results are worse than
they actually should be.
The tests need to be analysed to see if they respect the --no-huge and
--no-pci flags correctly, I suspect some tests are being run even though
these flags are enabled.
I believe enough of the tests pass to allow the initial version of the
patch set to be accepted. We can look at the failing cases later, and
improve the test suite as time goes on.
Thanks,
Dave.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] DPDK ArmV7 autotests
2015-11-10 10:22 ` Hunt, David
@ 2015-11-10 10:30 ` Thomas Monjalon
2015-11-10 12:45 ` Jerin Jacob
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Monjalon @ 2015-11-10 10:30 UTC (permalink / raw)
To: Hunt, David; +Cc: dev
2015-11-10 10:22, Hunt, David:
> On 09/11/2015 17:46, Jan Viktorin wrote:
> > Here is the log. You an see, that many tests fail just because
> > of the missing hugetlb support. This is strange as I modified the
> > autotest_runner.py to inject "--no-huge --no-pci" options when it
> > detects armv7 architecture.
>
> I think publishing these test results to the mailing list confuses
> matters somewhat. The tests are not tuned for armv7, and there are many
> false negatives, giving the impression that the results are worse than
> they actually should be.
>
> The tests need to be analysed to see if they respect the --no-huge and
> --no-pci flags correctly, I suspect some tests are being run even though
> these flags are enabled.
>
> I believe enough of the tests pass to allow the initial version of the
> patch set to be accepted. We can look at the failing cases later, and
> improve the test suite as time goes on.
I agree.
The unit tests are know to require some refactoring.
I suggest to continue ARM integration while checking how to fix the
unit tests later. Maybe that Declan has some ideas or plans about the tests.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] DPDK ArmV7 autotests
2015-11-10 10:30 ` Thomas Monjalon
@ 2015-11-10 12:45 ` Jerin Jacob
0 siblings, 0 replies; 6+ messages in thread
From: Jerin Jacob @ 2015-11-10 12:45 UTC (permalink / raw)
To: Thomas Monjalon; +Cc: dev
On Tue, Nov 10, 2015 at 11:30:30AM +0100, Thomas Monjalon wrote:
> 2015-11-10 10:22, Hunt, David:
> > On 09/11/2015 17:46, Jan Viktorin wrote:
> > > Here is the log. You an see, that many tests fail just because
> > > of the missing hugetlb support. This is strange as I modified the
> > > autotest_runner.py to inject "--no-huge --no-pci" options when it
> > > detects armv7 architecture.
> >
> > I think publishing these test results to the mailing list confuses
> > matters somewhat. The tests are not tuned for armv7, and there are many
> > false negatives, giving the impression that the results are worse than
> > they actually should be.
> >
> > The tests need to be analysed to see if they respect the --no-huge and
> > --no-pci flags correctly, I suspect some tests are being run even though
> > these flags are enabled.
> >
> > I believe enough of the tests pass to allow the initial version of the
> > patch set to be accepted. We can look at the failing cases later, and
> > improve the test suite as time goes on.
>
> I agree.
> The unit tests are know to require some refactoring.
> I suggest to continue ARM integration while checking how to fix the
Make sense.
> unit tests later. Maybe that Declan has some ideas or plans about the tests.
I have tried autotest on armv8, results looks very promising.
Few more features need for armv8 port like lpm, optimized hash,
removing x86 dependencies from examples directory etc.
But these needs change in the common code
so IMO have existing code as base port and common code
changes we will add step by step otherwise it will be difficult manage.
root@arm64:/export/dpdk-armv8# python app/test/autotest.py build/app/test
build
build/app/test -c f -n 4
Test name Test result Test
Total
================================================================================
Start group_1: Success [00m 02s]
Timer autotest: Success [00m 41s]
Debug autotest: Success [00m 00s]
Errno autotest: Success [00m 00s]
Meter autotest: Success [00m 00s]
Common autotest: Success [00m 01s]
Dump log history: Success [00m 00s]
Dump rings: Success [00m 00s]
Dump mempools: Success [00m 00s][00m 46s]
Start group_2: Success [00m 02s]
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(failes on x86 too) [00m 00s]
Hash autotest: Success [05m 04s][05m 55s]
Start group_3: Success [00m 02s]
LPM autotest: Fail [Not found] [00m 00s]
IVSHMEM autotest: Fail [Not found](NA for arm64)[00m 00s]
Memcpy autotest: Success [00m 21s]
Memzone autotest: Success [00m 00s]
String autotest: Success [00m 00s]
Alarm autotest: Fail(failes on x86 too) [00m 00s][06m 20s]
Start group_4: Success [00m 02s]
PCI autotest: Success [00m 00s]
Malloc autotest: Success [00m 00s]
Multi-process autotest: Fail(failes on x86 too) [00m 03s]
Mbuf autotest: Success [01m 04s]
Per-lcore autotest: Success [00m 05s]
Ring autotest: Success [00m 02s][07m 37s]
Start group_5: Success [00m 02s]
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][08m 03s]
Start group_6: Success [00m 02s]
Function reentrancy autotest: Success [00m 00s]
Mempool autotest: Success [00m 08s]
Atomics autotest: Success [00m 00s]
Prefetch autotest: Success [00m 00s]
Red autotest: Success [01m 35s][09m 50s]
Start group_7: Success [00m 02s]
PMD ring autotest: Fail(needs NICS provided on cmdline) [00m 00s]
Access list control autotest: Success [00m 02s]
Sched autotest: Success [00m 00s][09m 56s]
Start kni: Success [00m 02s]
KNI autotest: Success [09m 59s]
Start mempool_perf: Success [00m 02s]
Cycles autotest: Success [00m 01s]
Mempool performance autotest: Success [09m 00s][19m 02s]
Start memcpy_perf: Success [00m 02s]
Memcpy performance autotest: Fail [Timeout] [15m 00s][34m 05s]
Start hash_perf: Success [00m 02s]
Hash performance autotest: Success [03m 44s][37m 52s]
Start power: Success [00m 02s]
Power autotest: Success [00m 00s][37m 54s]
Start power_acpi_cpufreq: Success [00m 02s]
Power ACPI cpufreq autotest: Fail(failes on x86 too) [00m 00s][37m 57s]
Start power_kvm_vm: Success [00m 02s]
Power KVM VM autotest: Fail [00m 00s][37m 59s]
Start lpm6: Success [00m 02s]
LPM6 autotest: Fail [Not found] [00m 00s][38m 01s]
Start timer_perf: Success [00m 02s]
Timer performance autotest: Success [00m 14s][38m 18s]
Start ring_perf: Success [00m 02s]
Ring performance autotest: Success [00m 22s][38m 43s]
================================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-11-10 12:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <5640CB56.4080506@intel.com>
2015-11-09 17:12 ` [dpdk-dev] DPDK ArmV7 autotests Jan Viktorin
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
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).