On Mon, 20 Jun 2016 12:44:35 +0200
Simon Kagstrom <simon.kagstrom at netinsight.net> wrote:
> I.e., avoid dump messages with double 0x0x, e.g.,
>
> dump mbuf at 0x0x7fac7b17c800, phys=17b17c880, buf_len=2176
> pkt_len=2064, ol_flags=0, nb_segs=1, in_port=255
> segment at 0x0x7fac7b17c800, data=0x0x7fac7b17c8f0, data_len=2064
>
> Signed-off-by: Simon Kagstrom <simon.kagstrom at netinsight.net>
Agreed. Many other places have same glitch.
$ git grep '0x%p'
drivers/net/vmxnet3/vmxnet3_rxtx.c: "RXQ: cmd0 base : 0x%p cmd1
base : 0x%p comp ring base : 0x%p.",
drivers/net/vmxnet3/vmxnet3_rxtx.c: PMD_TX_LOG(DEBUG, "TXQ: cmd base : 0x%p
comp ring base : 0x%p data ring base : 0x%p.",
lib/librte_eal/linuxapp/kni/ethtool/ixgbe/ixgbe_ethtool.c:
printk(KERN_DEBUG "ixgbe_get_regs_2 0x%p\n", hw->hw_addr);
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("tx_phys: 0x%016llx,
tx_q addr: 0x%p\n",
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("rx_phys: 0x%016llx,
rx_q addr: 0x%p\n",
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("alloc_phys: 0x%016llx,
alloc_q addr: 0x%p\n",
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("free_phys: 0x%016llx,
free_q addr: 0x%p\n",
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("req_phys: 0x%016llx,
req_q addr: 0x%p\n",
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("resp_phys: 0x%016llx,
resp_q addr: 0x%p\n",
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("mbuf_phys: 0x%016llx,
mbuf_kva: 0x%p\n",
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_PRINT("mbuf_va: 0x%p\n",
dev_info.mbuf_va);
lib/librte_eal/linuxapp/kni/kni_misc.c: KNI_DBG("PCI found:
pci=0x%p, lad_dev=0x%p\n",
lib/librte_mbuf/rte_mbuf.c: fprintf(f, "dump mbuf at 0x%p, phys=%"PRIx64",
buf_len=%u\n",
lib/librte_mbuf/rte_mbuf.c: fprintf(f, " segment at 0x%p,
data=0x%p, data_len=%u\n",
