Re: [PATCH v10 0/3] Secure Memory Allocation Framework

From	John Einar Reitan <john.reitan@foss.arm.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v10 0/3] Secure Memory Allocation Framework
Date	2016-10-10 15:10 +0200
Message-ID	<sqIv8-1FC-13@gated-at.bofh.it> (permalink)
References	(1 earlier) <soUqJ-1wC-1@gated-at.bofh.it> <soUK5-1DV-9@gated-at.bofh.it> <spkbx-35y-73@gated-at.bofh.it> <spDQS-19L-11@gated-at.bofh.it> <spEDf-1QU-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, Oct 07, 2016 at 10:42:17AM -0400, Rob Clark wrote:
> probably should keep the discussion on github (USAGE.md was updated a
> bit more and merged into https://github.com/cubanismo/allocator so
> look there for the latest)..
> 
> but briefly:
> 
> 1) my expectation is if the user is implementing some use-case, it
> knows what devices and APIs are involved, otherwise it wouldn't be
> able to pass a buffer to that device/API..

As I described at Linaro Connect late-connected devices could cause new
constrains to appear. I.e. some (additonal) HDMI connection or WiFi Display etc.
Including all the might-happen devices might lead to unoptimal buffers
just to be able to handle some rarely-happen events.

I guess the easy resolve here is for the user to do a reallocation with
the new constraints added and replace the buffer(s) in question, but
with a slight lag in enabling the new device.

John

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH v10 0/3] Secure Memory Allocation Framework Benjamin Gaignard <benjamin.gaignard@linaro.org> - 2016-10-04 13:50 +0200
  [PATCH v10 3/3] SMAF: add test secure module Benjamin Gaignard <benjamin.gaignard@linaro.org> - 2016-10-04 13:50 +0200
  [PATCH v10 1/3] create SMAF module Benjamin Gaignard <benjamin.gaignard@linaro.org> - 2016-10-04 13:50 +0200
  [PATCH v10 2/3] SMAF: add CMA allocator Benjamin Gaignard <benjamin.gaignard@linaro.org> - 2016-10-04 13:50 +0200
  Re: [PATCH v10 0/3] Secure Memory Allocation Framework Daniel Vetter <daniel@ffwll.ch> - 2016-10-05 15:30 +0200
    Re: [PATCH v10 0/3] Secure Memory Allocation Framework Daniel Vetter <daniel@ffwll.ch> - 2016-10-05 15:50 +0200
      Re: [PATCH v10 0/3] Secure Memory Allocation Framework Benjamin Gaignard <benjamin.gaignard@linaro.org> - 2016-10-06 14:20 +0200
    Re: [PATCH v10 0/3] Secure Memory Allocation Framework Benjamin Gaignard <benjamin.gaignard@linaro.org> - 2016-10-05 15:50 +0200
      Re: [PATCH v10 0/3] Secure Memory Allocation Framework Rob Clark <robdclark@gmail.com> - 2016-10-06 19:00 +0200
        Re: [PATCH v10 0/3] Secure Memory Allocation Framework Benjamin Gaignard <benjamin.gaignard@linaro.org> - 2016-10-07 16:00 +0200
          Re: [PATCH v10 0/3] Secure Memory Allocation Framework Rob Clark <robdclark@gmail.com> - 2016-10-07 16:50 +0200
            Re: [PATCH v10 0/3] Secure Memory Allocation Framework John Einar Reitan <john.reitan@foss.arm.com> - 2016-10-10 15:10 +0200

csiph-web