lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: "熊毓华 via lttng-dev" <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>,
	 "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>
Cc: "ychen@northwestern.edu" <ychen@northwestern.edu>,
	list徐立恒 <245038403@qq.com>,
	"Shopping Ruan" <rlq1969612634@gmail.com>
Subject: [lttng-dev] questions about mapping from file names to corresponding inode
Date: Thu, 7 May 2020 13:23:10 +0800 (GMT+08:00)	[thread overview]
Message-ID: <1bb0377a.88648.171ed966cd8.Coremail.xiongyuhua@zju.edu.cn> (raw)
Message-ID: <20200507052310.H1g9cubv3ZSw_PYlgECnlmdaJ3QD5UT_-iwCxobcXvI@z> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 919 bytes --]

Hi,

I want to know whether lttng trace data will provide mapping from file names to corresponding inode.

I refered some data parsed by babeltrace,and found that internal kernel tracepoints like writeback_dirty_inode_start、jbd2_submit_inode_data and lttng_statedump_vm_map can provide inode parameter.But I don’t know the meaning of these tracepoints mentioned above, and it seems to have little to do with the mapping we need.I want to know which tracepoint will record the mapping.

In addition, I found the get_inode_from_fd() function at lttng-uprobes.c.It seems to provide some hints, can this function provide the mapping information we want?If so, how should I use it to get the data.



Looking forward to your reply.




thanks,

yuhua


------------------
Yuhua Xiong
Lab for Internet and Security Technology
School of Computer Science and Technology
Zhejiang University
Hangzhou, 310007, P.R. China

[-- Attachment #1.2: Type: text/html, Size: 1192 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2020-05-07 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  5:23 熊毓华 via lttng-dev [this message]
2020-05-07  5:23 ` 熊毓华 via lttng-dev
     [not found] ` <6e246dec-525a-ef1b-8599-aa5904004ff0@versatic.net>
2020-05-11 16:18   ` 熊毓华 via lttng-dev
2020-05-11 16:18     ` [lttng-dev] " 熊毓华 via lttng-dev

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=1bb0377a.88648.171ed966cd8.Coremail.xiongyuhua@zju.edu.cn \
    --to=lttng-dev@lists.lttng.org \
    --cc=245038403@qq.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rlq1969612634@gmail.com \
    --cc=xiongyuhua@zju.edu.cn \
    --cc=ychen@northwestern.edu \
    --subject='Re: [lttng-dev] questions about mapping from file names to corresponding inode' \
    /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

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).