Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752806AbcJJNBa (ORCPT ); Mon, 10 Oct 2016 09:01:30 -0400 Received: from foss.arm.com ([217.140.101.70]:46710 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752504AbcJJNB1 (ORCPT ); Mon, 10 Oct 2016 09:01:27 -0400 Date: Mon, 10 Oct 2016 14:51:37 +0200 From: John Einar Reitan To: Rob Clark Cc: Benjamin Gaignard , "linux-media@vger.kernel.org" , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Cc Ma , Joakim Bech , Burt Lien , Linus Walleij , Linaro MM SIG Mailman List , Linaro Kernel Mailman List Subject: Re: [PATCH v10 0/3] Secure Memory Allocation Framework Message-ID: <20161010125136.GA2844@e106921-lin.trondheim.arm.com> Mail-Followup-To: Rob Clark , Benjamin Gaignard , "linux-media@vger.kernel.org" , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Cc Ma , Joakim Bech , Burt Lien , Linus Walleij , Linaro MM SIG Mailman List , Linaro Kernel Mailman List References: <1475581644-10600-1-git-send-email-benjamin.gaignard@linaro.org> <20161005131959.GE20761@phenom.ffwll.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 907 Lines: 21 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