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 2/3] mm: cma: allocation trigger
Date: Tue, 20 Jan 2015 12:38:32 -0500 [thread overview]
Message-ID: <1421775513-4460-3-git-send-email-sasha.levin@oracle.com> (raw)
In-Reply-To: <1421775513-4460-1-git-send-email-sasha.levin@oracle.com>
Provides a userspace interface to trigger a CMA allocation.
Usage:
echo [pages] > alloc
This would provide testing/fuzzing access to the CMA allocation paths.
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
---
mm/cma_debug.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 58 insertions(+)
diff --git a/mm/cma_debug.c b/mm/cma_debug.c
index 3a25413..eda0a41 100644
--- a/mm/cma_debug.c
+++ b/mm/cma_debug.c
@@ -7,9 +7,22 @@
#include <linux/debugfs.h>
#include <linux/cma.h>
+#include <linux/list.h>
+#include <linux/kernel.h>
+#include <linux/dma-contiguous.h>
+#include <linux/slab.h>
#include "cma.h"
+struct cma_mem {
+ struct hlist_node node;
+ struct page *p;
+ unsigned long n;
+};
+
+static HLIST_HEAD(cma_mem_head);
+static DEFINE_SPINLOCK(cma_mem_head_lock);
+
static struct dentry *cma_debugfs_root;
static int cma_debugfs_get(void *data, u64 *val)
@@ -44,6 +57,48 @@ static void cma_debugfs_add_one(struct cma *cma, int idx)
debugfs_create_u32_array("bitmap", S_IRUGO, tmp, (u32*)cma->bitmap, u32s);
}
+static void cma_add_to_cma_mem_list(struct cma_mem *mem)
+{
+ spin_lock(&cma_mem_head_lock);
+ hlist_add_head(&mem->node, &cma_mem_head);
+ spin_unlock(&cma_mem_head_lock);
+}
+
+static int cma_alloc_mem(int count)
+{
+ struct cma_mem *mem;
+ struct page *p;
+
+ mem = kzalloc(sizeof(*mem), GFP_KERNEL);
+ if (!mem)
+ return -ENOMEM;
+
+ p = cma_alloc(dma_contiguous_default_area, count, CONFIG_CMA_ALIGNMENT);
+ if (!p) {
+ pr_info("CMA: Allocation failed.\n");
+ kfree(mem);
+ return -ENOMEM;
+ }
+
+ pr_info("CMA: Allocated %d pages at %p\n", count, p);
+
+ mem->p = p;
+ mem->n = count;
+
+ cma_add_to_cma_mem_list(mem);
+
+ return 0;
+}
+
+static int cma_alloc_write(void *data, u64 val)
+{
+ int pages = val;
+
+ return cma_alloc_mem(pages);
+}
+
+DEFINE_SIMPLE_ATTRIBUTE(cma_alloc_fops, NULL, cma_alloc_write, "%llu\n");
+
static int __init cma_debugfs_init(void)
{
int i;
@@ -52,6 +107,9 @@ static int __init cma_debugfs_init(void)
if (!cma_debugfs_root)
return -ENOMEM;
+ debugfs_create_file("alloc", S_IWUSR, cma_debugfs_root, NULL,
+ &cma_alloc_fops);
+
for (i = 0; i < cma_area_count; i++)
cma_debugfs_add_one(&cma_areas[i], i);
--
1.7.10.4
next prev parent reply other threads:[~2015-01-20 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 17:38 [PATCH 0/3] mm: cma: debugfs access to CMA Sasha Levin
2015-01-20 17:38 ` [PATCH 1/3] mm: cma: debugfs interface Sasha Levin
2015-01-20 17:38 ` Sasha Levin [this message]
2015-01-22 8:26 ` [PATCH 2/3] mm: cma: allocation trigger Joonsoo Kim
2015-01-23 2:48 ` Sasha Levin
2015-01-23 6:37 ` Joonsoo Kim
2015-01-20 17:38 ` [PATCH 3/3] mm: cma: release trigger 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=1421775513-4460-3-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).