[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54EA6641.3010207@lge.com>
Date: Mon, 23 Feb 2015 08:29:05 +0900
From: Gioh Kim <gioh.kim@....com>
To: Stefan Strogin <s.strogin@...tner.samsung.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>
CC: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Michal Nazarewicz <mina86@...a86.com>,
aneesh.kumar@...ux.vnet.ibm.com,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Dmitry Safonov <d.safonov@...tner.samsung.com>,
Pintu Kumar <pintu.k@...sung.com>,
Weijie Yang <weijie.yang@...sung.com>,
Laura Abbott <lauraa@...eaurora.org>,
SeongJae Park <sj38.park@...il.com>,
Hui Zhu <zhuhui@...omi.com>, Minchan Kim <minchan@...nel.org>,
Dyasly Sergey <s.dyasly@...sung.com>,
Vyacheslav Tyrtov <v.tyrtov@...sung.com>,
gregory.0xf0@...il.com, sasha.levin@...cle.com, pavel@....cz,
stefan.strogin@...il.com
Subject: Re: [PATCH 0/4] mm: cma: add some debug information for CMA
2015-02-17 오전 4:29에 Stefan Strogin 이(가) 쓴 글:
> Hello Gioh,
>
> Thank you for your answer.
>
> On 14/02/15 10:40, Gioh Kim wrote:
>>>
>>> If this tracer is justifiable, I think that making it conditional is
>>> better than just enabling always on CONFIG_CMA_DEBUGFS. Some users
>>> don't want to this feature although they enable CONFIG_CMA_DEBUGFS.
>>>
>>> Thanks.
>>>
>>
>> Hello,
>>
>> Thanks for your work. It must be helpful to me.
>>
>> What about add another option to activate stack-trace?
>> In my platform I know all devices using cma area, so I usually don't
>> need stack-trace.
>>
>
> So Joonsoo suggests to add an option for buffer list, and you suggest to
> add another in addition to the first one (and also add CONFIG_STACKTRACE
> to dependences) right?
>
Right. Another option for only stack-trace might be good.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists