[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whVyH-wSWLd=Zn4rwo+91T+qzRvfMPC2yFX98GxykOqOw@mail.gmail.com>
Date: Thu, 6 Oct 2022 11:20:16 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: Phil Chang (張世勳)
<Phil.Chang@...iatek.com>,
"ira.weiny@...el.com" <ira.weiny@...el.com>,
Jens Wiklander <jens.wiklander@...aro.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
"Fabio M. De Francesco" <fmdefrancesco@...il.com>,
Christoph Hellwig <hch@....de>,
"op-tee@...ts.trustedfirmware.org" <op-tee@...ts.trustedfirmware.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH 2/4] tee: Remove vmalloc page support
On Wed, Oct 5, 2022 at 11:24 PM Sumit Garg <sumit.garg@...aro.org> wrote:
>
> Sorry but you need to get your driver mainline in order to support
> vmalloc interface.
Actually, I think even then we shouldn't support vmalloc - and
register_shm_helper() just needs to be changed to pass in an array of
actual page pointers instead.
At that point TEE_SHM_USER_MAPPED should also go away, because then
it's the caller that should just do either the user space page
pinning, or pass in the kernel page pointer.
JensW, is there some reason that wouldn't work?
Linus
Powered by blists - more mailing lists