linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Stefan Roesch <shr@devkernel.io>
Cc: kernel-team@fb.com, acme@redhat.com, akpm@linux-foundation.org,
	bobwxc@email.cn, brauner@kernel.org, brho@google.com,
	broonie@kernel.org, catalin.marinas@arm.com, cgel.zte@gmail.com,
	corbet@lwn.net, dave@stgolabs.net, ebiederm@xmission.com,
	eugenis@google.com, hannes@cmpxchg.org, linmiaohe@huawei.com,
	mhiramat@kernel.org, mhocko@suse.com, ran.xiaokai@zte.com.cn,
	rppt@kernel.org, shuah@kernel.org, shy828301@gmail.com,
	song@kernel.org, Vincenzo.Frascino@arm.com, will@kernel.org,
	willy@infradead.org, yang.yang29@zte.com.cn,
	zhengqi.arch@bytedance.com, linux-doc@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [RESEND RFC PATCH v1 07/20] mm: add tracepoints to ksm
Date: Mon, 23 Jan 2023 10:45:30 -0500	[thread overview]
Message-ID: <20230123104530.4ec0aeb4@gandalf.local.home> (raw)
In-Reply-To: <20230123050042.1752641-8-shr@devkernel.io>

On Sun, 22 Jan 2023 21:00:29 -0800
Stefan Roesch <shr@devkernel.io> wrote:

> This adds the following tracepoints to ksm:
> - start / stop scan
> - ksm enter / exit
> - merge a page
> - merge a page with ksm
> - remove a page
> - remove a rmap item
> 
> Signed-off-by: Stefan Roesch <shr@devkernel.io>
> ---
>  MAINTAINERS                |   1 +
>  include/trace/events/ksm.h | 257 +++++++++++++++++++++++++++++++++++++
>  mm/ksm.c                   |  20 ++-
>  3 files changed, 276 insertions(+), 2 deletions(-)
>  create mode 100644 include/trace/events/ksm.h

From the tracing pov:

Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>

-- Steve


       reply	other threads:[~2023-01-23 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230123050042.1752641-1-shr@devkernel.io>
     [not found] ` <20230123050042.1752641-8-shr@devkernel.io>
2023-01-23 15:45   ` Steven Rostedt [this message]
2023-01-23 17:37 [RESEND RFC PATCH v1 00/20] mm: process/cgroup ksm support Stefan Roesch
2023-01-23 17:37 ` [RESEND RFC PATCH v1 07/20] mm: add tracepoints to ksm Stefan Roesch
2023-01-30 17:03   ` Steven Rostedt

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=20230123104530.4ec0aeb4@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=Vincenzo.Frascino@arm.com \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bobwxc@email.cn \
    --cc=brauner@kernel.org \
    --cc=brho@google.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=cgel.zte@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dave@stgolabs.net \
    --cc=ebiederm@xmission.com \
    --cc=eugenis@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mhocko@suse.com \
    --cc=ran.xiaokai@zte.com.cn \
    --cc=rppt@kernel.org \
    --cc=shr@devkernel.io \
    --cc=shuah@kernel.org \
    --cc=shy828301@gmail.com \
    --cc=song@kernel.org \
    --cc=will@kernel.org \
    --cc=willy@infradead.org \
    --cc=yang.yang29@zte.com.cn \
    --cc=zhengqi.arch@bytedance.com \
    /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