Re: [PATCH v4 0/2] RFC: Secure Memory Allocation Framework

2015-10-06 Thread Benjamin Gaignard
I have mind few uses cases: - the basic one when an HW device need contiguous memory. - I have a device that could not cross some memory boundaries so I need a specific allocator for it. - when allocating memory for security some platform have address constraints or need to allocate memory in

Re: [PATCH v4 0/2] RFC: Secure Memory Allocation Framework

2015-10-05 Thread Laura Abbott
On 10/05/2015 03:11 AM, Benjamin Gaignard wrote: version 4 changes: - rebased on kernel 4.3-rc3 - fix missing EXPORT_SYMBOL for smaf_create_handle() version 3 changes: - Remove ioctl for allocator selection instead provide the name of the targeted allocator with allocation request.

[PATCH v4 0/2] RFC: Secure Memory Allocation Framework

2015-10-05 Thread Benjamin Gaignard
version 4 changes: - rebased on kernel 4.3-rc3 - fix missing EXPORT_SYMBOL for smaf_create_handle() version 3 changes: - Remove ioctl for allocator selection instead provide the name of the targeted allocator with allocation request. Selecting allocator from userland isn't the prefered