2017-03-13 23:07 GMT+09:00 DaeSeok Youn <daeseok.youn@xxxxxxxxx>: > 2017-03-13 20:51 GMT+09:00 Dan Carpenter <dan.carpenter@xxxxxxxxxx>: >> On Mon, Mar 13, 2017 at 07:54:21PM +0900, Daeseok Youn wrote: >>> If the atomisp_kernel_zalloc() has "true" as a second parameter, it >>> tries to allocate zeroing memory from kmalloc(vmalloc) and memset. >>> But using kzalloc is rather than kmalloc followed by memset with 0. >>> (vzalloc is for same reason with kzalloc) >>> >>> And also atomisp_kernel_malloc() can be used with >>> atomisp_kernel_zalloc(<size>, false); >>> >> >> We should just change all the callers to kvmalloc() and kvzmalloc(). > ok. I will try to change all the callers to kvmalloc() and kvzalloc(). The kvmalloc() and kvzalloc() are not ready to use in staging-testing branch on staging tree. If the kvmalloc and kvzalloc are available to use, I will replace atomisp_kernel_malloc() and atomisp_kernel_zalloc() with kvmalloc() and kvzalloc(). Thanks. Regards, Daeseok Youn. > > Thanks. > Regards, > Daeseok Youn >> >> regards, >> dan carpenter >> -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
