linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jaewon Kim <jaewon31.kim@samsung.com>
To: willy@infradead.org, walken@google.com, bp@suse.de,
	akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	jaewon31.kim@gmail.com, Jaewon Kim <jaewon31.kim@samsung.com>
Subject: [PATCH v2 0/2] mm: mmap: add mmap trace point
Date: Fri, 13 Mar 2020 10:14:18 +0900	[thread overview]
Message-ID: <20200313011420.15995-1-jaewon31.kim@samsung.com> (raw)
In-Reply-To: <CGME20200313011430epcas1p423b939dea080fda77a2e0fe3f6531489@epcas1p4.samsung.com>

Create mmap trace file and add trace point of vm_unmapped_area.

To include mmap trace, remove inline of vm_unmapped_area and move code
to mmap.c. There is no logical change.

Jaewon Kim (2):
  mmap: remove inline of vm_unmapped_area
  mm: mmap: add trace point of vm_unmapped_area

 include/linux/mm.h          | 21 +-----------------
 include/trace/events/mmap.h | 52 +++++++++++++++++++++++++++++++++++++++++++++
 mm/mmap.c                   | 24 +++++++++++++++++++++
 3 files changed, 77 insertions(+), 20 deletions(-)
 create mode 100644 include/trace/events/mmap.h

-- 
2.13.7



       reply	other threads:[~2020-03-13  1:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200313011430epcas1p423b939dea080fda77a2e0fe3f6531489@epcas1p4.samsung.com>
2020-03-13  1:14 ` Jaewon Kim [this message]
     [not found]   ` <CGME20200313011430epcas1p129e4033f12b9c02f71443e0b359a26e5@epcas1p1.samsung.com>
2020-03-13  1:14     ` [PATCH v2 1/2] mmap: remove inline of vm_unmapped_area Jaewon Kim
2020-03-13  3:02       ` Andrew Morton
2020-03-13  3:27         ` Jaewon Kim
2020-03-13 10:36       ` Vlastimil Babka
     [not found]   ` <CGME20200313011430epcas1p436a6c02a262debcd755f3e1378331764@epcas1p4.samsung.com>
2020-03-13  1:14     ` [PATCH v2 2/2] mm: mmap: add trace point " Jaewon Kim
2020-03-13 11:25       ` 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=20200313011420.15995-1-jaewon31.kim@samsung.com \
    --to=jaewon31.kim@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=jaewon31.kim@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=walken@google.com \
    --cc=willy@infradead.org \
    /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