From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Dave Chinner <david@fromorbit.com>,
Andi Kleen <ak@linux.intel.com>,
Christoph Hellwig <hch@infradead.org>,
kernel-team@fb.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-mm@kvack.org,
linux-nfs@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 2/9] fs: tracepoints around multigrain timestamp events
Date: Fri, 5 Jul 2024 14:07:03 -0400 [thread overview]
Message-ID: <20240705140703.711d816b@rorschach.local.home> (raw)
In-Reply-To: <20240705-mgtime-v3-2-85b2daa9b335@kernel.org>
On Fri, 05 Jul 2024 13:02:36 -0400
Jeff Layton <jlayton@kernel.org> wrote:
> diff --git a/include/trace/events/timestamp.h b/include/trace/events/timestamp.h
> new file mode 100644
> index 000000000000..a004e5572673
> --- /dev/null
> +++ b/include/trace/events/timestamp.h
> @@ -0,0 +1,109 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#undef TRACE_SYSTEM
> +#define TRACE_SYSTEM timestamp
> +
> +#if !defined(_TRACE_TIMESTAMP_H) || defined(TRACE_HEADER_MULTI_READ)
> +#define _TRACE_TIMESTAMP_H
> +
> +#include <linux/tracepoint.h>
> +#include <linux/fs.h>
> +
> +TRACE_EVENT(inode_set_ctime_to_ts,
> + TP_PROTO(struct inode *inode,
> + struct timespec64 *ctime),
> +
> + TP_ARGS(inode, ctime),
> +
> + TP_STRUCT__entry(
> + __field(dev_t, dev)
> + __field(ino_t, ino)
> + __field(u32, gen)
It's best to keep the above 4 byte word below 8 byte words, otherwise,
it will likely create a 4 byte hole in between.
> + __field(time64_t, ctime_s)
> + __field(u32, ctime_ns)
> + ),
> +
> + TP_fast_assign(
> + __entry->dev = inode->i_sb->s_dev;
> + __entry->ino = inode->i_ino;
> + __entry->gen = inode->i_generation;
> + __entry->ctime_s = ctime->tv_sec;
> + __entry->ctime_ns = ctime->tv_nsec;
> + ),
> +
> + TP_printk("ino=%d:%d:%ld:%u ctime=%lld.%u",
> + MAJOR(__entry->dev), MINOR(__entry->dev), __entry->ino, __entry->gen,
> + __entry->ctime_s, __entry->ctime_ns
> + )
> +);
> +
> +TRACE_EVENT(ctime_ns_xchg,
> + TP_PROTO(struct inode *inode,
> + u32 old,
> + u32 new,
> + u32 cur),
> +
> + TP_ARGS(inode, old, new, cur),
> +
> + TP_STRUCT__entry(
> + __field(dev_t, dev)
> + __field(ino_t, ino)
> + __field(u32, gen)
> + __field(u32, old)
> + __field(u32, new)
> + __field(u32, cur)
> + ),
> +
> + TP_fast_assign(
> + __entry->dev = inode->i_sb->s_dev;
> + __entry->ino = inode->i_ino;
> + __entry->gen = inode->i_generation;
> + __entry->old = old;
> + __entry->new = new;
> + __entry->cur = cur;
> + ),
> +
> + TP_printk("ino=%d:%d:%ld:%u old=%u:%c new=%u cur=%u:%c",
> + MAJOR(__entry->dev), MINOR(__entry->dev), __entry->ino, __entry->gen,
> + __entry->old & ~I_CTIME_QUERIED, __entry->old & I_CTIME_QUERIED ? 'Q' : '-',
> + __entry->new,
> + __entry->cur & ~I_CTIME_QUERIED, __entry->cur & I_CTIME_QUERIED ? 'Q' : '-'
> + )
> +);
> +
> +TRACE_EVENT(fill_mg_cmtime,
> + TP_PROTO(struct inode *inode,
> + struct timespec64 *ctime,
> + struct timespec64 *mtime),
> +
> + TP_ARGS(inode, ctime, mtime),
> +
> + TP_STRUCT__entry(
> + __field(dev_t, dev)
> + __field(ino_t, ino)
> + __field(u32, gen)
Same here.
-- Steve
> + __field(time64_t, ctime_s)
> + __field(time64_t, mtime_s)
> + __field(u32, ctime_ns)
> + __field(u32, mtime_ns)
> + ),
> +
> + TP_fast_assign(
> + __entry->dev = inode->i_sb->s_dev;
> + __entry->ino = inode->i_ino;
> + __entry->gen = inode->i_generation;
> + __entry->ctime_s = ctime->tv_sec;
> + __entry->mtime_s = mtime->tv_sec;
> + __entry->ctime_ns = ctime->tv_nsec;
> + __entry->mtime_ns = mtime->tv_nsec;
> + ),
> +
> + TP_printk("ino=%d:%d:%ld:%u ctime=%lld.%u mtime=%lld.%u",
> + MAJOR(__entry->dev), MINOR(__entry->dev), __entry->ino, __entry->gen,
> + __entry->ctime_s, __entry->ctime_ns,
> + __entry->mtime_s, __entry->mtime_ns
> + )
> +);
> +#endif /* _TRACE_TIMESTAMP_H */
> +
> +/* This part must be outside protection */
> +#include <trace/define_trace.h>
>
next prev parent reply other threads:[~2024-07-05 18:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 17:02 [PATCH v3 0/9] fs: multigrain timestamp redux Jeff Layton
2024-07-05 17:02 ` [PATCH v3 1/9] fs: add infrastructure for multigrain timestamps Jeff Layton
2024-07-08 12:30 ` Jeff Layton
2024-07-08 15:24 ` Jeff Layton
2024-07-08 15:32 ` Uros Bizjak
2024-07-05 17:02 ` [PATCH v3 2/9] fs: tracepoints around multigrain timestamp events Jeff Layton
2024-07-05 18:07 ` Steven Rostedt [this message]
2024-07-05 18:16 ` Jeff Layton
2024-07-05 17:02 ` [PATCH v3 3/9] fs: add percpu counters to count fine vs. coarse timestamps Jeff Layton
2024-07-05 17:02 ` [PATCH v3 4/9] fs: have setattr_copy handle multigrain timestamps appropriately Jeff Layton
2024-07-05 17:02 ` [PATCH v3 5/9] Documentation: add a new file documenting multigrain timestamps Jeff Layton
2024-07-05 20:59 ` Randy Dunlap
2024-07-05 17:02 ` [PATCH v3 6/9] xfs: switch to " Jeff Layton
2024-07-05 17:02 ` [PATCH v3 7/9] ext4: " Jeff Layton
2024-07-05 17:02 ` [PATCH v3 8/9] btrfs: convert " Jeff Layton
2024-07-05 17:02 ` [PATCH v3 9/9] tmpfs: add support for " Jeff Layton
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=20240705140703.711d816b@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=adilger.kernel@dilger.ca \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).