Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752735AbbBLW1H (ORCPT ); Thu, 12 Feb 2015 17:27:07 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:34006 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751562AbbBLW1E (ORCPT ); Thu, 12 Feb 2015 17:27:04 -0500 From: Sasha Levin To: linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: iamjoonsoo.kim@lge.com, m.szyprowski@samsung.com, akpm@linux-foundation.org, lauraa@codeaurora.org, s.strogin@partner.samsung.com, Sasha Levin Subject: [PATCH v5 0/3] mm: cma: debugfs access to CMA Date: Thu, 12 Feb 2015 17:26:45 -0500 Message-Id: <1423780008-16727-1-git-send-email-sasha.levin@oracle.com> X-Mailer: git-send-email 2.1.0 X-Source-IP: aserv0021.oracle.com [141.146.126.233] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1318 Lines: 44 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 v4: - Inform user if he has attempted to free a partial block when the page order != 0. Changes from v3: - Minor build fix, sent incorrect patch for v3 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 | 25 ++++----- mm/cma.h | 24 ++++++++ mm/cma_debug.c | 170 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 211 insertions(+), 15 deletions(-) create mode 100644 mm/cma.h create mode 100644 mm/cma_debug.c -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/