From: Laura Abbott <labbott@redhat.com>
To: Chen Feng <puck.chen@hisilicon.com>,
Liam Mark <lmark@codeaurora.org>,
Sumit Semwal <sumit.semwal@linaro.org>
Cc: devel@driverdev.osuosl.org, Greg KH <gregkh@linuxfoundation.org>,
Zhuangluan Su <suzhuangluan@hisilicon.com>,
linux-kernel@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
"Xiaqing \(A\)" <saberlily.xia@hisilicon.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Linaro-mm-sig] [PATCH v3] staging: android: ion: Zero CMA allocated memory
Date: Fri, 26 Jan 2018 22:52:28 -0800 [thread overview]
Message-ID: <b0380b1b-2583-89fb-72c9-b9a606ee6a8a@redhat.com> (raw)
In-Reply-To: <5A6BDE11.9070403@hisilicon.com>
On 01/26/2018 06:04 PM, Chen Feng wrote:
>
>
> On 2018/1/27 1:48, Liam Mark wrote:
>> Since commit 204f672255c2 ("staging: android: ion: Use CMA APIs directly")
>> the CMA API is now used directly and therefore the allocated memory is no
>> longer automatically zeroed.
>>
>> Explicitly zero CMA allocated memory to ensure that no data is exposed to
>> userspace.
>>
>> Fixes: 204f672255c2 ("staging: android: ion: Use CMA APIs directly")
>> Signed-off-by: Liam Mark <lmark@codeaurora.org>
>> ---
>> Changes in v2:
>> - Clean up the commit message.
>> - Add 'Fixes:'
>>
>> Changes in v3:
>> - Add support for highmem pages
>>
>> drivers/staging/android/ion/ion_cma_heap.c | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>>
>> diff --git a/drivers/staging/android/ion/ion_cma_heap.c b/drivers/staging/android/ion/ion_cma_heap.c
>> index 86196ffd2faf..fa3e4b7e0c9f 100644
>> --- a/drivers/staging/android/ion/ion_cma_heap.c
>> +++ b/drivers/staging/android/ion/ion_cma_heap.c
>> @@ -21,6 +21,7 @@
>> #include <linux/err.h>
>> #include <linux/cma.h>
>> #include <linux/scatterlist.h>
>> +#include <linux/highmem.h>
>>
>> #include "ion.h"
>>
>> @@ -51,6 +52,22 @@ static int ion_cma_allocate(struct ion_heap *heap, struct ion_buffer *buffer,
>> if (!pages)
>> return -ENOMEM;
>>
>> + if (PageHighMem(pages)) {
>> + unsigned long nr_clear_pages = nr_pages;
>> + struct page *page = pages;
>> +
>> + while (nr_clear_pages > 0) {
>> + void *vaddr = kmap_atomic(page);
>> +
>> + memset(vaddr, 0, PAGE_SIZE);
>> + kunmap_atomic(vaddr);
>
> Here. This way may cause performance latency at mapping-memset-umap page one bye one.
>
> Take a look at ion_heap_pages_zero.
>
> Not very critical, arm64 always have linear mapping.
>
This is under a PageHighMem check so arm64 isn't affected. It's also
the same algorithm arm32 dma-mapping.c uses so I'd like to see some
data about the performance improvement before we go changing things
too much.
Thanks,
Laura
>
>> + page++;
>> + nr_clear_pages--;
>> + }
>> + } else {
>> + memset(page_address(pages), 0, size);
>> + }
>> +
>> table = kmalloc(sizeof(*table), GFP_KERNEL);
>> if (!table)
>> goto err;
>>
>
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-01-27 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 17:48 Liam Mark
2018-01-27 2:04 ` [Linaro-mm-sig] " Chen Feng
2018-01-27 6:52 ` Laura Abbott [this message]
2018-02-06 22:49 ` Laura Abbott
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=b0380b1b-2583-89fb-72c9-b9a606ee6a8a@redhat.com \
--to=labbott@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=puck.chen@hisilicon.com \
--cc=saberlily.xia@hisilicon.com \
--cc=sumit.semwal@linaro.org \
--cc=suzhuangluan@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®