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
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
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.
>>
>>
Hello Joonsoo,
Thank you for your answer.
On 13/02/15 06:03, Joonsoo Kim wrote:
> On Fri, Feb 13, 2015 at 01:15:40AM +0300, Stefan Strogin wrote:
>>
>> Here is an example use case when we need it. We want a big (megabytes)
>> CMA buffer to be allocated in runtime in default CMA region. If
Hello Joonsoo,
Thank you for your answer.
On 13/02/15 06:03, Joonsoo Kim wrote:
On Fri, Feb 13, 2015 at 01:15:40AM +0300, Stefan Strogin wrote:
Here is an example use case when we need it. We want a big (megabytes)
CMA buffer to be allocated in runtime in default CMA region. If someone
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.
2015-02-13 오후 12:03에 Joonsoo Kim 이(가) 쓴 글:
On Fri, Feb 13, 2015 at 01:15:40AM +0300, Stefan Strogin wrote:
Hi all.
Sorry for the long delay. Here is the second attempt to add some facility
for debugging CMA (the first one was "mm: cma: add /proc/cmainfo" [1]).
This patch set is based on
2015-02-13 오후 12:03에 Joonsoo Kim 이(가) 쓴 글:
On Fri, Feb 13, 2015 at 01:15:40AM +0300, Stefan Strogin wrote:
Hi all.
Sorry for the long delay. Here is the second attempt to add some facility
for debugging CMA (the first one was mm: cma: add /proc/cmainfo [1]).
This patch set is based on v3.19
On Fri, Feb 13, 2015 at 01:15:40AM +0300, Stefan Strogin wrote:
> Hi all.
>
> Sorry for the long delay. Here is the second attempt to add some facility
> for debugging CMA (the first one was "mm: cma: add /proc/cmainfo" [1]).
>
> This patch set is based on v3.19 and Sasha Levin's patch set
>
Hi all.
Sorry for the long delay. Here is the second attempt to add some facility
for debugging CMA (the first one was "mm: cma: add /proc/cmainfo" [1]).
This patch set is based on v3.19 and Sasha Levin's patch set
"mm: cma: debugfs access to CMA" [2].
It is also available on git:
Hi all.
Sorry for the long delay. Here is the second attempt to add some facility
for debugging CMA (the first one was mm: cma: add /proc/cmainfo [1]).
This patch set is based on v3.19 and Sasha Levin's patch set
mm: cma: debugfs access to CMA [2].
It is also available on git:
On Fri, Feb 13, 2015 at 01:15:40AM +0300, Stefan Strogin wrote:
Hi all.
Sorry for the long delay. Here is the second attempt to add some facility
for debugging CMA (the first one was mm: cma: add /proc/cmainfo [1]).
This patch set is based on v3.19 and Sasha Levin's patch set
mm: cma:
12 matches
Mail list logo
