From: Sasha Levin <sasha.levin@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: iamjoonsoo.kim@lge.com, m.szyprowski@samsung.com,
akpm@linux-foundation.org, lauraa@codeaurora.org,
Sasha Levin <sasha.levin@oracle.com>
Subject: [PATCH v3 0/3] mm: cma: debugfs access to CMA
Date: Tue, 27 Jan 2015 21:22:54 -0500 [thread overview]
Message-ID: <1422411777-22332-1-git-send-email-sasha.levin@oracle.com> (raw)
I've noticed that there is no interfaces exposed by CMA which would let me
fuzz what's going on in there.
This small patch set exposes some information out to userspace, plus adds
the ability to trigger allocation and freeing from userspace.
Changes from v2:
- Keep allocated memory lists per-cma
- Don't allow partial free with non-zero order_per_bit
- Use 0 alignment
Changes from v1:
- Make allocation and free hooks per-cma.
- Remove additional debug prints.
Sasha Levin (3):
mm: cma: debugfs interface
mm: cma: allocation trigger
mm: cma: release trigger
mm/Kconfig | 6 ++
mm/Makefile | 1 +
mm/cma.c | 19 ++----
mm/cma.h | 20 +++++++
mm/cma_debug.c | 175 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 206 insertions(+), 15 deletions(-)
create mode 100644 mm/cma.h
create mode 100644 mm/cma_debug.c
--
1.7.10.4
next reply other threads:[~2015-01-28 2:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 2:22 Sasha Levin [this message]
2015-01-28 2:22 ` [PATCH v3 1/3] mm: cma: debugfs interface Sasha Levin
2015-01-28 2:22 ` [PATCH v3 2/3] mm: cma: allocation trigger Sasha Levin
2015-01-28 2:22 ` [PATCH v3 3/3] mm: cma: release trigger Sasha Levin
2015-01-29 7:51 ` Joonsoo Kim
2015-01-29 13:04 ` Sasha Levin
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=1422411777-22332-1-git-send-email-sasha.levin@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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;
as well as URLs for NNTP newsgroup(s).