DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: gowrishankar muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bus/fslmc: use PRIu64 instead of llX in format specifier
Date: Fri, 13 Apr 2018 16:07:11 +0530	[thread overview]
Message-ID: <16f772e5-71f6-6116-3750-d6e7a6293249@nxp.com> (raw)
In-Reply-To: <e7d0dcb0-8eb4-3081-0092-52bff60e8f1b@linux.vnet.ibm.com>

On Friday 13 April 2018 02:13 PM, gowrishankar muthukrishnan wrote:
> On Friday 13 April 2018 02:26 PM, Shreyansh Jain wrote:
>> On Friday 13 April 2018 01:11 PM, Thomas Monjalon wrote:
>>> 13/04/2018 07:04, Gowrishankar:
>>>> -    DPAA2_BUS_DEBUG("--> Map address: %llX, size: 0x%llX",
>>>> +    DPAA2_BUS_DEBUG("--> Map address: %"PRIu64", size: 0x%"PRIu64"",
>>>
>>> You cannot replace hexadecimal by decimal.
>>> You need to use PRIx64.
>>>
>>>
>>
>> Now that Thomas has pointed out, I think the log message can be 
>> improved. Len as hex is not helpful and is out of sync with other 
>> messages in this file.
>>
>> While on this, I think it should be corrected.
>> I will fix this.
>>
>> @gowrishankar, I will post a patch in reply to your patch - can you 
>> please help me with ppc64le check? I will take care of Hemant's comment.
> 
> Yup, I check for it. Thanks Shreyansh.
> 

Can you please check this:

--->8---
@@ -270,8 +270,8 @@ fslmc_map_dma(uint64_t vaddr, rte_iova_t iovaddr 
__rte_unused, size_t len)
                 return -1;
         }

-       DPAA2_BUS_DEBUG("--> Map address: %llX, size: 0x%llX",
-                       dma_map.vaddr, dma_map.size);
+       DPAA2_BUS_DEBUG("--> Map address: 0x%"PRIx64", size: %"PRIu64"",
+                       (uint64_t)dma_map.vaddr, (uint64_t)dma_map.size);
         ret = ioctl(group->container->fd, VFIO_IOMMU_MAP_DMA, &dma_map);
         if (ret) {
                 DPAA2_BUS_ERR("VFIO_IOMMU_MAP_DMA API(errno = %d)",
@@ -303,8 +303,8 @@ fslmc_unmap_dma(uint64_t vaddr, uint64_t iovaddr 
__rte_unused, size_t len)
                 return -1;
         }

-       DPAA2_BUS_DEBUG("--> Unmap address: %llX, size: 0x%llX",
-                       dma_unmap.iova, dma_unmap.size);
+       DPAA2_BUS_DEBUG("--> Unmap address: 0x%"PRIx64", size: %"PRIu64"",
+                       (uint64_t)dma_unmap.iova, (uint64_t)dma_unmap.size);
         ret = ioctl(group->container->fd, VFIO_IOMMU_UNMAP_DMA, 
&dma_unmap);
         if (ret) {
                 DPAA2_BUS_ERR("VFIO_IOMMU_UNMAP_DMA API(errno = %d)",
@@ -401,8 +401,8 @@ static int64_t vfio_map_mcp_obj(struct 
fslmc_vfio_group *group, char *mcp_obj)
                 goto MC_FAILURE;
         }

-       DPAA2_BUS_DEBUG("Region offset = %llx  , region size = %llx",
-                       reg_info.offset, reg_info.size);
+       DPAA2_BUS_DEBUG("Region offset = 0x%"PRIx64", region size = 
%"PRIu64"",
+                       (uint64_t)reg_info.offset, (uint64_t)reg_info.size);

         v_addr = (size_t)mmap(NULL, reg_info.size,
                 PROT_WRITE | PROT_READ, MAP_SHARED,
--->8---

gcc for i686/x86_64/ARM64 are compiling fine for me.

If this works fine, feel free to use it in your patch.

-
Shreyansh

  reply	other threads:[~2018-04-13 10:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13  5:04 Gowrishankar
2018-04-13  7:10 ` Shreyansh Jain
2018-04-13  7:09   ` Hemant Agrawal
2018-04-13  7:37 ` Hemant Agrawal
2018-04-13  7:41 ` Thomas Monjalon
2018-04-13  8:56   ` Shreyansh Jain
2018-04-13  8:43     ` gowrishankar muthukrishnan
2018-04-13 10:37       ` Shreyansh Jain [this message]
2018-04-13 10:40 ` [dpdk-dev] [PATCH v2] " Gowrishankar
2018-04-13 10:47   ` gowrishankar muthukrishnan
2018-04-13 10:55 ` Gowrishankar
2018-04-13 11:17   ` Shreyansh Jain
2018-04-13 11:22 ` [dpdk-dev] [PATCH v3] " Gowrishankar
2018-04-13 12:44   ` Hemant Agrawal
2018-04-15 12:22     ` Thomas Monjalon

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=16f772e5-71f6-6116-3750-d6e7a6293249@nxp.com \
    --to=shreyansh.jain@nxp.com \
    --cc=dev@dpdk.org \
    --cc=gowrishankar.m@linux.vnet.ibm.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).