linux-kernel - Using ion memory for direct-io

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <678F3D1BB717D949B966B68EAEB446ED0BCCFFC4@dggeml511-mbs.china.huawei.com>
Date:   Fri, 14 Apr 2017 09:18:25 +0000
From:   "Zengtao (B)" <prime.zeng@...ilicon.com>
To:     "labbott@...hat.com" <labbott@...hat.com>,
        "sumit.semwal@...aro.org" <sumit.semwal@...aro.org>
CC:     "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "arve@...roid.com" <arve@...roid.com>,
        "riandrews@...roid.com" <riandrews@...roid.com>,
        "devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Using ion memory for direct-io

Hi 

Currently, the ion mapped to userspace will be forced with VM_IO and VM_PFNMAP flags.
When I use the ion memory to do the direct-io, it will fail when reaching the get_user_pages,

Back to the VM_IO and VM_PFNMAP flag, there two flags are introduced by the remap_pfn_range called 
by the ion_heap_mmap_user.

>From my point of view, all ion memory(cma/vmalloc/system heap) are managed by linux vm, it
is not reasonable to have the VM_IO and VM_PFNMAP flag, but I don't any suitable function
to replace the remap_pfn_range, any suggestions?

Thanks && Regards

Zengtao