All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gang Li <ligang.bdlg@bytedance.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH 3/3] mm: mmap_lock: add ip to mmap_lock tracepoints
Date: Tue, 31 Aug 2021 11:24:12 +0800	[thread overview]
Message-ID: <4cded873-3706-8d2c-765c-5c896aa13714@bytedance.com> (raw)
In-Reply-To: <b0b30c3d-0fb8-7d29-2a60-0cce0309986b@bytedance.com>

Hi Steven! Sorry to bother you ;)

(I resend this email because the last one was not cc to mailing list.)

It has been ten days since my last email. What's your opinion about my 
patch "[PATCH 3/3] mm: mmap_lock: add ip to mmap_lock tracepoints"? 
Briefly, lock events are so frequent that ip collection and lock event 
collection cannot be separated, otherwise it will cause the wrong order 
of data.

I am developing a tool to analyze mmap_lock contend using this feature. 
Adding ip to mmap_lock tracepoints is quite convenient.

Sorry to bother you again. Hoping for your reply. Thanks!

-- Gang

On 8/20/21 2:18 AM, Gang Li wrote:
 > On 8/2/21 10:44 AM, Gang Li wrote:
 >> On 7/31/21 4:03 AM, Steven Rostedt wrote:
 >>> Yes, synthetic events are just like normal events, and have triggers,
 >>> stack traces, and do pretty much anything that another event can do.
 >>>
 > Hi!
 >
 > I find that sometimes the output data is out of order, which leads to 
inaccurate time stamps and make it hard to analyze.

  reply	other threads:[~2021-08-31  3:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  9:28 [PATCH 3/3] mm: mmap_lock: add ip to mmap_lock tracepoints Gang Li
2021-07-29 17:33 ` Axel Rasmussen
2021-07-29 17:33   ` Axel Rasmussen
2021-07-30  5:32   ` Gang Li
2021-07-30 20:03     ` Steven Rostedt
2021-08-02  2:44       ` Gang Li
2021-08-19 18:18         ` Gang Li
2021-08-31  3:24           ` Gang Li [this message]
2021-07-30  8:12   ` Vlastimil Babka

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=4cded873-3706-8d2c-765c-5c896aa13714@bytedance.com \
    --to=ligang.bdlg@bytedance.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.