LKML Archive on lore.kernel.org help / color / mirror / Atom feed
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 v2 3/3] mm: cma: release trigger Date: Mon, 26 Jan 2015 09:26:05 -0500 [thread overview] Message-ID: <1422282365-20015-4-git-send-email-sasha.levin@oracle.com> (raw) In-Reply-To: <1422282365-20015-1-git-send-email-sasha.levin@oracle.com> Provides a userspace interface to trigger a CMA release. Usage: echo [pages] > free This would provide testing/fuzzing access to the CMA release paths. Signed-off-by: Sasha Levin <sasha.levin@oracle.com> --- mm/cma_debug.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/mm/cma_debug.c b/mm/cma_debug.c index 39c7116..0a63945 100644 --- a/mm/cma_debug.c +++ b/mm/cma_debug.c @@ -11,6 +11,7 @@ #include <linux/kernel.h> #include <linux/dma-contiguous.h> #include <linux/slab.h> +#include <linux/mm_types.h> #include "cma.h" @@ -43,6 +44,56 @@ static void cma_add_to_cma_mem_list(struct cma_mem *mem) spin_unlock(&cma_mem_head_lock); } +static struct cma_mem *cma_get_entry_from_list(void) +{ + struct cma_mem *mem = NULL; + + spin_lock(&cma_mem_head_lock); + if (!hlist_empty(&cma_mem_head)) { + mem = hlist_entry(cma_mem_head.first, struct cma_mem, node); + hlist_del_init(&mem->node); + } + spin_unlock(&cma_mem_head_lock); + + return mem; +} + +static int cma_free_mem(struct cma *cma, int count) +{ + struct cma_mem *mem = NULL; + + while (count) { + mem = cma_get_entry_from_list(); + if (mem == NULL) + return 0; + + if (mem->n <= count) { + cma_release(cma, mem->p, mem->n); + count -= mem->n; + kfree(mem); + } else { + cma_release(cma, mem->p, count); + mem->p += count; + mem->n -= count; + count = 0; + cma_add_to_cma_mem_list(mem); + } + } + + return 0; + +} + +static int cma_free_write(void *data, u64 val) +{ + int pages = val; + struct cma *cma = data; + + return cma_free_mem(cma, pages); +} + +DEFINE_SIMPLE_ATTRIBUTE(cma_free_fops, NULL, cma_free_write, "%llu\n"); + static int cma_alloc_mem(struct cma *cma, int count) { struct cma_mem *mem; @@ -89,6 +140,9 @@ static void cma_debugfs_add_one(struct cma *cma, int idx) debugfs_create_file("alloc", S_IWUSR, cma_debugfs_root, cma, &cma_alloc_fops); + debugfs_create_file("free", S_IWUSR, cma_debugfs_root, cma, + &cma_free_fops); + debugfs_create_file("base_pfn", S_IRUGO, tmp, &cma->base_pfn, &cma_debugfs_fops); debugfs_create_file("count", S_IRUGO, tmp, -- 1.7.10.4
next prev parent reply other threads:[~2015-01-26 14:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-26 14:26 [PATCH v2 0/3] mm: cma: debugfs access to CMA Sasha Levin 2015-01-26 14:26 ` [PATCH v2 1/3] mm: cma: debugfs interface Sasha Levin 2015-01-26 14:26 ` [PATCH v2 2/3] mm: cma: allocation trigger Sasha Levin 2015-01-27 8:06 ` Joonsoo Kim 2015-01-27 15:08 ` Sasha Levin 2015-01-28 1:34 ` Joonsoo Kim 2015-01-26 14:26 ` Sasha Levin [this message] 2015-01-27 8:10 ` [PATCH v2 3/3] mm: cma: release trigger Joonsoo Kim 2015-01-27 18:25 ` Sasha Levin 2015-01-27 20:13 ` Sasha Levin 2015-01-28 1:35 ` Joonsoo Kim
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=1422282365-20015-4-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: linkBe 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).