From: Mayank Rana <quic_mrana@quicinc.com>
To: Carl Vanderlip <quic_carlv@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kernel test robot <lkp@intel.com>,
Jeffrey Hugo <quic_jhugo@quicinc.com>, <mhi@lists.linux.dev>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bus/mhi: Switch trace_mhi_gen_tre fields to native endian
Date: Fri, 4 Oct 2024 11:24:44 -0700 [thread overview]
Message-ID: <17db9ffe-4e30-4776-a1f1-6da81cc0fcc2@quicinc.com> (raw)
In-Reply-To: <20241004170321.4047492-1-quic_carlv@quicinc.com>
On 10/4/2024 10:03 AM, Carl Vanderlip wrote:
> Each of the __field() macros were triggering sparse warnings similar to:
> trace.h:87:1: sparse: sparse: cast to restricted __le64
> trace.h:87:1: sparse: sparse: restricted __le64 degrades to integer
> trace.h:87:1: sparse: sparse: restricted __le64 degrades to integer
>
> Change each little endian type to its similarly sized native integer.
> Convert inputs into native endian.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202402071859.8qMhgJEQ-lkp@intel.com/
do you want to add Fixes tag as:
Fixes: ceeb64f41fe6 ("bus: mhi: host: Add tracing support")
> Signed-off-by: Carl Vanderlip <quic_carlv@quicinc.com>
> Reviewed-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> ---
> drivers/bus/mhi/host/trace.h | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/bus/mhi/host/trace.h b/drivers/bus/mhi/host/trace.h
> index 95613c8ebe06..3e0c41777429 100644
> --- a/drivers/bus/mhi/host/trace.h
> +++ b/drivers/bus/mhi/host/trace.h
> @@ -9,6 +9,7 @@
> #if !defined(_TRACE_EVENT_MHI_HOST_H) || defined(TRACE_HEADER_MULTI_READ)
> #define _TRACE_EVENT_MHI_HOST_H
>
> +#include <linux/byteorder/generic.h>
> #include <linux/tracepoint.h>
> #include <linux/trace_seq.h>
> #include "../common.h"
> @@ -97,18 +98,18 @@ TRACE_EVENT(mhi_gen_tre,
> __string(name, mhi_cntrl->mhi_dev->name)
> __field(int, ch_num)
> __field(void *, wp)
> - __field(__le64, tre_ptr)
> - __field(__le32, dword0)
> - __field(__le32, dword1)
> + __field(uint64_t, tre_ptr)
> + __field(uint32_t, dword0)
> + __field(uint32_t, dword1)
> ),
>
> TP_fast_assign(
> __assign_str(name);
> __entry->ch_num = mhi_chan->chan;
> __entry->wp = mhi_tre;
> - __entry->tre_ptr = mhi_tre->ptr;
> - __entry->dword0 = mhi_tre->dword[0];
> - __entry->dword1 = mhi_tre->dword[1];
> + __entry->tre_ptr = le64_to_cpu(mhi_tre->ptr);
> + __entry->dword0 = le32_to_cpu(mhi_tre->dword[0]);
> + __entry->dword1 = le32_to_cpu(mhi_tre->dword[1]);
> ),
>
> TP_printk("%s: Chan: %d TRE: 0x%p TRE buf: 0x%llx DWORD0: 0x%08x DWORD1: 0x%08x\n",
> @@ -176,19 +177,19 @@ DECLARE_EVENT_CLASS(mhi_process_event_ring,
>
> TP_STRUCT__entry(
> __string(name, mhi_cntrl->mhi_dev->name)
> - __field(__le32, dword0)
> - __field(__le32, dword1)
> + __field(uint32_t, dword0)
> + __field(uint32_t, dword1)
> __field(int, state)
> - __field(__le64, ptr)
> + __field(uint64_t, ptr)
> __field(void *, rp)
> ),
>
> TP_fast_assign(
> __assign_str(name);
> __entry->rp = rp;
> - __entry->ptr = rp->ptr;
> - __entry->dword0 = rp->dword[0];
> - __entry->dword1 = rp->dword[1];
> + __entry->ptr = le64_to_cpu(rp->ptr);
> + __entry->dword0 = le32_to_cpu(rp->dword[0]);
> + __entry->dword1 = le32_to_cpu(rp->dword[1]);
> __entry->state = MHI_TRE_GET_EV_STATE(rp);
> ),
>
Reviewed-by: Mayank Rana <quic_mrana@quicinc.com>
Regards,
Mayank
next prev parent reply other threads:[~2024-10-04 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 17:03 Carl Vanderlip
2024-10-04 18:24 ` Mayank Rana [this message]
2024-10-06 18:10 ` Manivannan Sadhasivam
2024-10-06 18:11 ` Manivannan Sadhasivam
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=17db9ffe-4e30-4776-a1f1-6da81cc0fcc2@quicinc.com \
--to=quic_mrana@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.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
all inboxes | Powered by JetHome®