From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Dan Williams <dan.j.williams@intel.com>,
Ingo Molnar <mingo@redhat.com>, Jan Kara <jack@suse.cz>,
Matthew Wilcox <mawilcox@microsoft.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-nvdimm@lists.01.org
Subject: Re: [PATCH v3 0/5] introduce DAX tracepoint support
Date: Mon, 19 Dec 2016 09:46:00 -0700 [thread overview]
Message-ID: <20161219164600.GA21334@linux.intel.com> (raw)
In-Reply-To: <1480610271-23699-1-git-send-email-ross.zwisler@linux.intel.com>
On Thu, Dec 01, 2016 at 09:37:46AM -0700, Ross Zwisler wrote:
> Tracepoints are the standard way to capture debugging and tracing
> information in many parts of the kernel, including the XFS and ext4
> filesystems. This series creates a tracepoint header for FS DAX and add
> the first few DAX tracepoints to the PMD fault handler. This allows the
> tracing for DAX to be done in the same way as the filesystem tracing so
> that developers can look at them together and get a coherent idea of what
> the system is doing.
>
> I do intend to add tracepoints to the normal 4k DAX fault path and to the
> DAX I/O path, but I wanted to get feedback on the PMD tracepoints before I
> went any further.
>
> This series is based on Jan Kara's "dax: Clear dirty bits after flushing
> caches" series:
>
> https://lists.01.org/pipermail/linux-nvdimm/2016-November/007864.html
>
> I've pushed a git tree with this work here:
>
> https://git.kernel.org/cgit/linux/kernel/git/zwisler/linux.git/log/?h=dax_tracepoints_v3
>
> Changes since v2:
> - Dropped "dax: remove leading space from labels" patch. (Jan)
> - Reordered TP_STRUCT__entry() fields so that all the 64 bit entries (for
> 64 bit machines) come first, followed by the 32 bit entries. This
> allows for optimal packing of the entires. (Steve)
> - Fixed 'mask' in trace_print_flags_seq_u64() to be an unsigned long long.
> (Steve)
>
> Ross Zwisler (5):
> tracing: add __print_flags_u64()
> dax: add tracepoint infrastructure, PMD tracing
> dax: update MAINTAINERS entries for FS DAX
> dax: add tracepoints to dax_pmd_load_hole()
> dax: add tracepoints to dax_pmd_insert_mapping()
>
> MAINTAINERS | 5 +-
> fs/dax.c | 56 ++++++++++-----
> include/linux/mm.h | 25 +++++++
> include/linux/pfn_t.h | 6 ++
> include/linux/trace_events.h | 4 ++
> include/trace/events/fs_dax.h | 161 ++++++++++++++++++++++++++++++++++++++++++
> include/trace/trace_events.h | 11 +++
> kernel/trace/trace_output.c | 38 ++++++++++
> 8 files changed, 288 insertions(+), 18 deletions(-)
> create mode 100644 include/trace/events/fs_dax.h
Ping on this series - Dave, were you planning on sending this for v4.10-rc1?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-12-19 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 16:37 [PATCH v3 0/5] introduce DAX tracepoint support Ross Zwisler
2016-12-01 16:37 ` [PATCH v3 1/5] tracing: add __print_flags_u64() Ross Zwisler
2016-12-01 16:53 ` Steven Rostedt
2016-12-01 16:37 ` [PATCH v3 2/5] dax: add tracepoint infrastructure, PMD tracing Ross Zwisler
2016-12-01 16:54 ` Steven Rostedt
2016-12-01 16:37 ` [PATCH v3 3/5] dax: update MAINTAINERS entries for FS DAX Ross Zwisler
2016-12-01 16:37 ` [PATCH v3 4/5] dax: add tracepoints to dax_pmd_load_hole() Ross Zwisler
2016-12-01 16:56 ` Steven Rostedt
2016-12-01 16:37 ` [PATCH v3 5/5] dax: add tracepoints to dax_pmd_insert_mapping() Ross Zwisler
2016-12-01 16:56 ` Steven Rostedt
2016-12-19 16:46 ` Ross Zwisler [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=20161219164600.GA21334@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mawilcox@microsoft.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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).