From: Phil Yang <phil.yang@arm.com>
To: dev@dpdk.org
Cc: nd@arm.com, herbert.guan@arm.com, jianbo.liu@arm.com, phil.yang@arm.com
Subject: [dpdk-dev] [PATCH] fix memzone unit test defect in verify process.
Date: Mon, 29 Jan 2018 14:23:05 +0800 [thread overview]
Message-ID: <1517206986-32281-1-git-send-email-phil.yang@arm.com> (raw)
Runtime Log:
memzone_autotest
test basic memzone API
Zone 0: name:<rte_eth_dev_data>, IO:0x10bffc5980, len:0x34900,
virt:0xffff7ffc5980, socket_id:0, flags:0
Zone 1: name:<RG_HT_fdir_0002:81:00.0>, IO:0x10bff77180, len:0x40180,
virt:0xffff7ff77180, socket_id:0, flags:0
Zone 2: name:<RG_HT_l2_tn_0002:81:00.0>, IO:0x10bfc76600, len:0x580,
virt:0xffff7fc76600, socket_id:0, flags:0
Zone 3: name:<RG_HT_fdir_0002:81:00.1>, IO:0x10bfc24d80, len:0x40180,
virt:0xffff7fc24d80, socket_id:0, flags:0
Zone 4: name:<RG_HT_l2_tn_0002:81:00.1>, IO:0x10bf924200, len:0x580,
virt:0xffff7f924200, socket_id:0, flags:0
Zone 5: name:<testzone1>, IO:0x10bf922480, len:0x80,
virt:0xffff7f922480, socket_id:0, flags:0
Zone 6: name:<testzone2>, IO:0x10bf922000, len:0x400,
virt:0xffff7f922000, socket_id:0, flags:0
Zone 7: name:<testzone4>, IO:0x10bf921b80, len:0x400,
virt:0xffff7f921b80, socket_id:0, flags:0
check alignments and lengths
check overlapping
check socket ID
test zone lookup
test duplcate zone name
test free memzone
EAL: memzone_reserve_aligned_thread_unsafe(): No more room in config
test reserving memzone with bigger size than the maximum
test memzone_reserve flags
1GB Huge pages available
test alignment for memzone_reserve
check alignments and lengths
check overlapping
test boundary alignment for memzone_reserve
test invalid alignment for memzone_reserve
EAL: memzone_reserve_aligned_thread_unsafe(): Invalid alignment: 100
test reserving the largest size memzone possible
test reserving the largest size aligned memzone possible
check memzone cleanup
there are some memzones left after test
Zone 0: name:<rte_eth_dev_data>, IO:0x10bffc5980, len:0x34900,
virt:0xffff7ffc5980, socket_id:0, flags:0
Zone 1: name:<RG_HT_fdir_0002:81:00.0>, IO:0x10bff77180, len:0x40180,
virt:0xffff7ff77180, socket_id:0, flags:0
Zone 2: name:<RG_HT_l2_tn_0002:81:00.0>, IO:0x10bfc76600, len:0x580,
virt:0xffff7fc76600, socket_id:0, flags:0
Zone 3: name:<RG_HT_fdir_0002:81:00.1>, IO:0x10bfc24d80, len:0x40180,
virt:0xffff7fc24d80, socket_id:0, flags:0
Zone 4: name:<RG_HT_l2_tn_0002:81:00.1>, IO:0x10bf924200, len:0x580,
virt:0xffff7f924200, socket_id:0, flags:0
Test Failed
Backtrace:
#0 rte_memzone_reserve_thread_safe (name=0xaaaaaafeccf8
"rte_eth_dev_data", len=215296, socket_id=0, flags=0, align=128,
bound=0) at /root/dpdk/lib/librte_eal/common/eal_common_memzone.c:253
#1 0x0000aaaaaac98040 in rte_memzone_reserve (name=0xaaaaaafeccf8
"rte_eth_dev_data", len=215296, socket_id=0, flags=0) at
/root/dpdk/lib/librte_eal/common/eal_common_memzone.c:291
#2 0x0000aaaaaac67210 in rte_eth_dev_data_alloc () at
/root/dpdk/lib/librte_ether/rte_ethdev.c:191
#3 0x0000aaaaaac67490 in rte_eth_dev_allocate (name=0xaaaab1ba9738
"0002:81:00.0") at /root/dpdk/lib/librte_ether/rte_ethdev.c:256
#4 0x0000aaaaaae594c0 in rte_eth_dev_pci_allocate (dev=0xaaaab1ba8fa0,
private_data_size=30432) at
/root/dpdk/arm64-armv8a-linuxapp-gcc/include/rte_ethdev_pci.h:99
#5 0x0000aaaaaae59600 in rte_eth_dev_pci_generic_probe
(pci_dev=0xaaaab1ba8fa0, private_data_size=30432,
dev_init=0xaaaaaae5b0b4 <eth_ixgbe_dev_init>) at
/root/dpdk/arm64-armv8a-linuxapp-gcc/include/rte_ethdev_pci.h:158
#6 0x0000aaaaaae5c870 in eth_ixgbe_pci_probe (pci_drv=0xaaaaab2053a8
<rte_ixgbe_pmd>, pci_dev=0xaaaab1ba8fa0) at
/root/dpdk/drivers/net/ixgbe/ixgbe_ethdev.c:1762
#7 0x0000aaaaaacb7f94 in rte_pci_probe_one_driver (dr=0xaaaaab2053a8
<rte_ixgbe_pmd>, dev=0xaaaab1ba8fa0) at
/root/dpdk/drivers/bus/pci/pci_common.c:203
#8 0x0000aaaaaacb81a4 in pci_probe_all_drivers (dev=0xaaaab1ba8fa0) at
/root/dpdk/drivers/bus/pci/pci_common.c:278
#9 0x0000aaaaaacb84a4 in rte_pci_probe () at
/root/dpdk/drivers/bus/pci/pci_common.c:388
#10 0x0000aaaaaac9af74 in rte_bus_probe () at
/root/dpdk/lib/librte_eal/common/eal_common_bus.c:98
#11 0x0000aaaaaac8b800 in rte_eal_init (argc=5, argv=0xfffffffffb58) at
/root/dpdk/lib/librte_eal/linuxapp/eal/eal.c:957
#12 0x0000aaaaaab1e004 in main (argc=5, argv=0xfffffffffb58) at
test.c:86
...
Phil Yang (1):
test/memzone: fix incorrect result judging criteria
test/test/test_memzone.c | 141 +++++++++++++++++++++++++----------------------
1 file changed, 74 insertions(+), 67 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-29 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 6:23 Phil Yang [this message]
2018-01-29 6:23 ` [dpdk-dev] [PATCH] test/memzone: fix incorrect result judging criteria Phil Yang
2018-01-29 9:49 ` Burakov, Anatoly
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=1517206986-32281-1-git-send-email-phil.yang@arm.com \
--to=phil.yang@arm.com \
--cc=dev@dpdk.org \
--cc=herbert.guan@arm.com \
--cc=jianbo.liu@arm.com \
--cc=nd@arm.com \
/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).