Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp5911432ybg; Tue, 22 Oct 2019 10:08:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqzlx7f9fjZZoEtFJPaqOqONNsCWwUp8OnyrQaheeM8qoVYap24KTYXI3Q9M4PdUJ5kQUhZx X-Received: by 2002:aa7:cfcd:: with SMTP id r13mr32945399edy.146.1571764123214; Tue, 22 Oct 2019 10:08:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571764123; cv=none; d=google.com; s=arc-20160816; b=C/zzVC1ms3zAcCVTqGvsrRIHJqFFAdtlmEj3eJ9X/J9nQGva4X/ORqWD7TV42g/Bz4 jMitOAs0Rm/xNqGJAEYUuZoO0S4ebqf6wSgs7u/NqZBIxXcbYJ8gRlUwXIvIWV6p4YDb x8XyuNMqYLfPf3LtwTVKCMd+KPbZNPYsWe9AXCFSLP6Zf6ZZQmBSe0rCmSlNaXyKDlYZ o5VC5ExJ1vF77mM4ZKxKtfQgHxiIxAEXNdXHTRV5ChzGNdilRS07jlMfvADoxM9YcShY KuYcZvY6oND02D1aL7WtjhGhVxiIzrd51oTPKXmIKXA6ecRvegxw1zs5rMg/rgh5hnK2 4UeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=5H56XdOux4SKyU8Ke1qZlotEUEu1Ct1El6M2VfKXQrI=; b=rctnEwjjk1Jcj2ezghb1tNPOBleFd3RNtzKHWWB0Z/c2KfDtHl3uFKI3niRgiVEGeJ VQfLHSsUobJXNe7lG9nKFEuDxpV8MjULCjC0BbljDkN93kltxllgewS2DZOKAuk52g5z zCUqw6lYmbL/mIMG3YEplfhKz2S3726x6GnoTev4o47EkUa26XtNpuGL3zqYBouoJBG1 2cQJhy37Qs6k4ENthNl+JVYvz84TK+SkncyrOUcUWAue1lJ39udjBj/KFTez1Jkc2GGt kOUx1x++ZL1f9/t8a5fRhwpQpcngs/gUpMJ8pTyNChji5yYc3goTMXGQnp1GNH1aIZq5 nq4Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=InvwlPug; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d8si1650692ejl.130.2019.10.22.10.08.14; Tue, 22 Oct 2019 10:08:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=InvwlPug; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732008AbfJVP4U (ORCPT + 99 others); Tue, 22 Oct 2019 11:56:20 -0400 Received: from mail-ot1-f68.google.com ([209.85.210.68]:38026 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729696AbfJVP4T (ORCPT ); Tue, 22 Oct 2019 11:56:19 -0400 Received: by mail-ot1-f68.google.com with SMTP id e11so14622729otl.5 for ; Tue, 22 Oct 2019 08:56:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5H56XdOux4SKyU8Ke1qZlotEUEu1Ct1El6M2VfKXQrI=; b=InvwlPuggw69FQ+wNV9b2DwABdDRrRxnQhNV+lvNJZxDm1O9d3EwMNJk3NcYkz+Zzu Xu4pfeAN/BpJeuW0jb+tvWQyIITLENhCjkoEEn1Gu1rZIh1pXRjbKwWVqb7sksaPYRJ1 dLNSv1858/je85K4xejswBfzelyWsj0LDazReY9y/KMLz1L5bkjDWXqLdVm5nMvg/vfr 5ThlE4qYsdk8MSy4T6e9+u9qdXIL0dnJpF+rVsDNGLBuMZ5sxWAA6q4vUQnAIB+1X6kB zFIbA2VLwgVdhrEj9qK4FaBSw9rxMdGuDJbGjET3Aw3htlmjbvjoGmqiQ4nB01i/WPLZ loVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5H56XdOux4SKyU8Ke1qZlotEUEu1Ct1El6M2VfKXQrI=; b=D442vdallXEvLQvYTN788CuPwk0QoGmkW6EghFZvhdGhFBzOLI87t5pxo9VLBfeloF 9+3aq3A3HtO4XOuFvJRKXfP+8ozJo7ul9Tp8Phkr4tIJ9U53qFiTL65FlAx9e7/816ZH FLVSdy+EDp2KC6Kq34lqBq4qVIj6VsiwdxLyWKUQ5RnhOxm5yg7td6NT8hZRC/i99GqS GammWZKGl6yTPIafQrV43tMPQfEMF8LpRZOYsMXOJwhVP9wVIOim1VysvGrKoX7X5rPr cFenzWdDOqHDnqQ4Pp5UQ8/8ZZcwRkSgWxkWb5+OK00tFMVWPwRYaC1tDlxnjTZcJ6A3 pDPg== X-Gm-Message-State: APjAAAVPUNhy9GXQIzTjRn4JeAgJ35ll8pXuwTZEW2Jk3+rqt9uRL7B3 +WaaxReLNkfqF3kmFnGaLLo50T6xN66xpK5/jCtSZQ== X-Received: by 2002:a9d:630c:: with SMTP id q12mr3270558otk.332.1571759778722; Tue, 22 Oct 2019 08:56:18 -0700 (PDT) MIME-Version: 1.0 References: <20191021190310.85221-1-john.stultz@linaro.org> In-Reply-To: From: John Stultz Date: Tue, 22 Oct 2019 08:56:06 -0700 Message-ID: Subject: Re: [PATCH v13 0/5] DMA-BUF Heaps (destaging ION) To: Neil Armstrong Cc: lkml , Hillf Danton , Sudipto Paul , Vincent Donnefort , Chenbo Feng , Alistair Strachan , Liam Mark , Christoph Hellwig , dri-devel , "Andrew F . Davis" , Hridya Valsaraju , Pratik Patel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 22, 2019 at 1:21 AM Neil Armstrong wrote: > > Hi John, > > On 21/10/2019 21:03, John Stultz wrote: > > Lucky number 13! :) > > > > Last week in v12 I had re-added some symbol exports to support > > later patches I have pending to enable loading heaps from > > modules. He reminded me that back around v3 (its been awhile!) I > > had removed those exports due to concerns about the fact that we > > don't support module removal. > > > > So I'm respinning the patches, removing the exports again. I'll > > submit a patch to re-add them in a later series enabling moduels > > which can be reviewed indepently. > > > > With that done, lets get on to the boilerplate! > > > > The patchset implements per-heap devices which can be opened > > directly and then an ioctl is used to allocate a dmabuf from the > > heap. > > > > The interface is similar, but much simpler then IONs, only > > providing an ALLOC ioctl. > > > > Also, I've provided relatively simple system and cma heaps. > > > > I've booted and tested these patches with AOSP on the HiKey960 > > using the kernel tree here: > > https://git.linaro.org/people/john.stultz/android-dev.git/log/?h=dev/dma-buf-heap > > Do you have a 4.19 tree with the changes ? I tried but the xarray idr replacement > is missing... so I can't test with our android-amlogic-bmeson-4.19 tree. > > If you can provide, I'll be happy to test the serie and the gralloc changes. Unfortunately I don't have a 4.19 version of dmabuf heaps (all the work has been done this year, post 4.19). I'm planning to backport to 5.4 for AOSP, but I've not really thought about 4.19. Most likely I won't have time to look at it until after the changes are upstream and the 5.4 backport is done. Is the bmeson tree likely to only stay at 4.19? Or will it move forward? thanks -john