All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Starkey <Brian.Starkey@arm.com>
To: John Stultz <john.stultz@linaro.org>
Cc: nd <nd@arm.com>, Alistair Strachan <astrachan@google.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Andrew F . Davis" <afd@ti.com>, Liam Mark <lmark@codeaurora.org>
Subject: Re: [EARLY RFC][PATCH 0/4] ION per heap devices
Date: Mon, 18 Feb 2019 11:51:48 +0000	[thread overview]
Message-ID: <20190218115147.w5n2kc23xhw3xk7q@DESKTOP-E1NTVVP.localdomain> (raw)
In-Reply-To: <1550262252-15558-1-git-send-email-john.stultz@linaro.org>

Hi John,

On Fri, Feb 15, 2019 at 12:24:08PM -0800, John Stultz wrote:
> This is a *very early RFC* (it builds, that's all I'll say :)
> but I wanted to share it to get some initial feedback before I
> go down the rabit hole of trying to adapt the Android userland
> code to get this fully validated.
> 
> This patchset tries to implement the per-heap devices for ION.
> The main benefit is that it avoids multiplexing heap operations
> through the /dev/ion interface, and allows for each heap to have
> its own permissions/sepolicy rules.

In general, I've always thought that having a device node per-heap is
a bit messy for userspace. Multiplexing through the single node
doesn't seem like an insurmountable problem, but the point about
permissions/sepolicy is reasonably compelling if it's a real
requirement. What would be the reasons for that?

Thanks,
-Brian

> 
> Feedback would be greatly appreciated!
> thanks
> -john
> 
> Cc: Laura Abbott <labbott@redhat.com>
> Cc: Sumit Semwal <sumit.semwal@linaro.org>
> Cc: Liam Mark <lmark@codeaurora.org>
> Cc: Brian Starkey <Brian.Starkey@arm.com>
> Cc: Andrew F. Davis <afd@ti.com>
> Cc: Alistair Strachan <astrachan@google.com>
> Cc: dri-devel@lists.freedesktop.org
> 
> John Stultz (4):
>   ion: Add ION_VERSION ioctl
>   ion: Initial hack to create per heap devices
>   ion: Add HEAP_INFO ioctl to be able to fetch heap type
>   ion: Make "legacy" /dev/ion support optional
> 
>  drivers/staging/android/ion/Kconfig     |  7 +++
>  drivers/staging/android/ion/ion-ioctl.c | 80 +++++++++++++++++++++++++++++++++
>  drivers/staging/android/ion/ion.c       | 51 ++++++++++++++++-----
>  drivers/staging/android/ion/ion.h       |  6 +++
>  drivers/staging/android/uapi/ion.h      | 57 +++++++++++++++++++++++
>  5 files changed, 191 insertions(+), 10 deletions(-)
> 
> -- 
> 2.7.4
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-18 11:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 20:24 [EARLY RFC][PATCH 0/4] ION per heap devices John Stultz via dri-devel
2019-02-15 20:24 ` [EARLY RFC][PATCH 1/4] ion: Add ION_VERSION ioctl John Stultz via dri-devel
2019-02-19 20:46   ` Laura Abbott
2019-02-19 21:29     ` John Stultz
2019-02-15 20:24 ` [EARLY RFC][PATCH 2/4] ion: Initial hack to create per heap devices John Stultz via dri-devel
2019-02-19 21:17   ` Laura Abbott
2019-02-19 21:36     ` John Stultz
2019-02-15 20:24 ` [EARLY RFC][PATCH 3/4] ion: Add HEAP_INFO ioctl to be able to fetch heap type John Stultz via dri-devel
2019-02-19 21:13   ` Laura Abbott
2019-02-19 21:39     ` Andrew F. Davis
2019-02-19 21:46       ` Laura Abbott
2019-02-19 21:50         ` John Stultz
2019-02-19 21:47     ` John Stultz
2019-02-20 15:07       ` Brian Starkey
2019-02-20 17:29         ` John Stultz
2019-02-15 20:24 ` [EARLY RFC][PATCH 4/4] ion: Make "legacy" /dev/ion support optional John Stultz via dri-devel
2019-02-18 11:51 ` Brian Starkey [this message]
2019-02-19 17:21   ` [EARLY RFC][PATCH 0/4] ION per heap devices John Stultz
2019-02-19 20:51     ` Laura Abbott
2019-02-19 21:25 ` Laura Abbott
2019-02-19 21:30   ` Andrew F. Davis
2019-02-19 21:54     ` Laura Abbott
2019-02-19 21:55   ` John Stultz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190218115147.w5n2kc23xhw3xk7q@DESKTOP-E1NTVVP.localdomain \
    --to=brian.starkey@arm.com \
    --cc=afd@ti.com \
    --cc=astrachan@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=john.stultz@linaro.org \
    --cc=lmark@codeaurora.org \
    --cc=nd@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.