From: Steven Rostedt <rostedt@goodmis.org>
To: Ross Zwisler <ross.zwisler@linux.intel.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>,
Dave Chinner <david@fromorbit.com>,
Ingo Molnar <mingo@redhat.com>, Jan Kara <jack@suse.cz>,
Matthew Wilcox <mawilcox@microsoft.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-nvdimm@lists.01.org
Subject: Re: [PATCH v3 5/5] dax: add tracepoints to dax_pmd_insert_mapping()
Date: Thu, 1 Dec 2016 11:56:55 -0500 [thread overview]
Message-ID: <20161201115655.4315d942@gandalf.local.home> (raw)
In-Reply-To: <1480610271-23699-6-git-send-email-ross.zwisler@linux.intel.com>
On Thu, 1 Dec 2016 09:37:51 -0700
Ross Zwisler <ross.zwisler@linux.intel.com> wrote:
> Add tracepoints to dax_pmd_insert_mapping(), following the same logging
> conventions as the tracepoints in dax_iomap_pmd_fault().
>
> Here is an example PMD fault showing the new tracepoints:
>
> big-1504 [001] .... 326.960743: xfs_filemap_pmd_fault: dev 259:0 ino
> 0x1003
>
> big-1504 [001] .... 326.960753: dax_pmd_fault: dev 259:0 ino 0x1003
> shared WRITE|ALLOW_RETRY|KILLABLE|USER address 0x10505000 vm_start
> 0x10200000 vm_end 0x10700000 pgoff 0x200 max_pgoff 0x1400
>
> big-1504 [001] .... 326.960981: dax_pmd_insert_mapping: dev 259:0 ino
> 0x1003 shared write address 0x10505000 length 0x200000 pfn 0x100600 DEV|MAP
> radix_entry 0xc000e
>
> big-1504 [001] .... 326.960986: dax_pmd_fault_done: dev 259:0 ino 0x1003
> shared WRITE|ALLOW_RETRY|KILLABLE|USER address 0x10505000 vm_start
> 0x10200000 vm_end 0x10700000 pgoff 0x200 max_pgoff 0x1400 NOPAGE
>
> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> Reviewed-by: Jan Kara <jack@suse.cz>
> ---
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
--
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>
next prev parent reply other threads:[~2016-12-01 16:56 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 [this message]
2016-12-19 16:46 ` [PATCH v3 0/5] introduce DAX tracepoint support Ross Zwisler
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=20161201115655.4315d942@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=ross.zwisler@linux.intel.com \
--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).