From: Steven Rostedt <rostedt@goodmis.org>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-fsi@lists.ozlabs.org, linux-trace-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
mhiramat@kernel.org, alistair@popple.id.au, joel@jms.id.au,
jk@ozlabs.org, andrew@aj.id.au, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v4 2/2] fsi: Add IBM I2C Responder virtual FSI master
Date: Thu, 2 Feb 2023 15:29:32 -0500 [thread overview]
Message-ID: <20230202152932.34ce6304@rorschach.local.home> (raw)
In-Reply-To: <20230202191926.133340-3-eajames@linux.ibm.com>
On Thu, 2 Feb 2023 13:19:26 -0600
Eddie James <eajames@linux.ibm.com> wrote:
> +#include <linux/tracepoint.h>
> +
> +TRACE_EVENT(i2cr_i2c_error,
> + TP_PROTO(const struct i2c_client *client, __be32 command, int rc),
> + TP_ARGS(client, command, rc),
> + TP_STRUCT__entry(
> + __field(int, bus)
> + __field(unsigned short, addr)
For all of these, I would put the "unsigned short addr" at the end of
the TP_STRUCT__entry(). That's because you will inject two wasted bytes
in the structure that is generated. Granted, the tracing will likely
word align the result anyway, but still, we don't want holes in the
middle of the structure.
-- Steve
> + __array(unsigned char, command, sizeof(__be32))
> + __field(int, rc)
> + ),
> + TP_fast_assign(
> + __entry->bus = client->adapter->nr;
> + __entry->addr = client->addr;
> + memcpy(__entry->command, &command, sizeof(__be32));
> + __entry->rc = rc;
> + ),
> + TP_printk("%d-%02x command:{ %*ph } rc:%d", __entry->bus, __entry->addr,
> + (int)sizeof(__be32), __entry->command, __entry->rc)
> +);
> +
> +TRACE_EVENT(i2cr_read,
> + TP_PROTO(const struct i2c_client *client, uint32_t address, size_t size, __be64 result),
> + TP_ARGS(client, address, size, result),
> + TP_STRUCT__entry(
> + __field(int, bus)
> + __field(unsigned short, addr)
> + __field(uint32_t, address)
> + __field(size_t, size)
> + __array(unsigned char, result, sizeof(__be64))
> + ),
> + TP_fast_assign(
> + __entry->bus = client->adapter->nr;
> + __entry->addr = client->addr;
> + __entry->address = address;
> + __entry->size = size;
> + memcpy(__entry->result, &result, sizeof(__be64));
> + ),
> + TP_printk("%d-%02x address:%08x size:%zu { %*ph }", __entry->bus, __entry->addr,
> + __entry->address, __entry->size, (int)__entry->size, __entry->result)
> +);
> +
prev parent reply other threads:[~2023-02-02 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 19:19 [PATCH v4 0/2] " Eddie James
2023-02-02 19:19 ` [PATCH v4 1/2] dt-bindings: fsi: Document the " Eddie James
2023-02-02 19:19 ` [PATCH v4 2/2] fsi: Add " Eddie James
2023-02-02 20:29 ` Steven Rostedt [this message]
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=20230202152932.34ce6304@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=alistair@popple.id.au \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh+dt@kernel.org \
/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®