linux-kernel - Re: [PATCH v4] mm: cma: add a simple kernel module as the helper to test CMA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGsJ_4zGjLgNBHsHF6xmadpsntXBRaOVt58AeOCaawZ-pbQdzQ@mail.gmail.com>
Date:	Wed, 4 Jul 2012 14:56:22 +0800
From:	Barry Song <21cnbao@...il.com>
To:	Marek Szyprowski <m.szyprowski@...sung.com>
Cc:	Michal Nazarewicz <mina86@...a86.com>,
	Barry Song <Barry.Song@....com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	workgroup.linux@....com, Barry Song <Baohua.Song@....com>
Subject: Re: [PATCH v4] mm: cma: add a simple kernel module as the helper to
 test CMA

Hi Marek,

2012/7/4 Marek Szyprowski <m.szyprowski@...sung.com>:
> Hello,
>
> On Tuesday, July 03, 2012 2:54 PM Michal Nazarewicz wrote:
>
>> > 2012/7/3 Marek Szyprowski <m.szyprowski@...sung.com>:
>> >> IMHO the right place for such code is in drivers/misc instead of tools/cma.
>> >>
>> >> This patch contains a kernel module source code so it should be put with other kernel
>> >> modules. tools/ directory is aimed to contain user space code useful for developing and
>> >> testing Linux kernel.
>>
>> On Tue, 03 Jul 2012 09:39:34 +0200, Barry Song <21cnbao@...il.com> wrote:
>> > this one is aiming to test CMA, it should be in tools/ as Michal
>> > Nazarewicz and i have talked about that.
>> > it is not a real driver at all.
>>
>> Yeah, I feel like it's better placed in tools/ not to pollute other directories with
>> drivers that are of no use to regular users.  I don't have strong feelings about it
>> though, so I'm fine either way.
>
> Other test devices/drivers are in drivers directory (drivers/usb/misc/usbtest.c for
> example), I don't see any good reason for polluting tools/ directory with kernel code.
>
> IMHO the right person to decide if it makes sense to have such drivers in drivers/mics/
> or tools/cma/ is Greg KH. Barry, please resend it and ask Greg for the decision.

sure. thanks.

>
> Best regards
> --
> Marek Szyprowski
> Samsung Poland R&D Center
>
>

-barry
--
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/