aboutsummaryrefslogtreecommitdiff
path: root/fs/pstore/ram.c
Commit message (Collapse)AuthorAgeFilesLines
* pstore: Allow prz to control need for lockingJoel Fernandes2017-08-201-2/+3
| | | | | | | | | | | In preparation of not locking at all for certain buffers depending on if there's contention, make locking optional depending on the initialization of the prz. Signed-off-by: Joel Fernandes <joelaf@google.com> [kees: moved locking flag into prz instead of via caller arguments] Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Joe Maples <joe@frap129.org>
* FROMLIST: pstore: drop pmsg bounce bufferMark Salyzyn2017-05-201-0/+19
| | | | | | | | | | | | | | | | | | (from https://lkml.org/lkml/2016/9/1/428) (cherry pick from android-3.10 commit b58133100b38f2bf83cad2d7097417a3a196ed0b) Removing a bounce buffer copy operation in the pmsg driver path is always better. We also gain in overall performance by not requesting a vmalloc on every write as this can cause precious RT tasks, such as user facing media operation, to stall while memory is being reclaimed. Added a write_buf_user to the pstore functions, a backup platform write_buf_user that uses the small buffer that is part of the instance, and implemented a ramoops write_buf_user that only supports PSTORE_TYPE_PMSG. Signed-off-by: Mark Salyzyn <salyzyn@google.com> Bug: 31057326 Change-Id: I4cdee1cd31467aa3e6c605bce2fbd4de5b0f8caa
* fs/pstore: fix compilation warningPatrick Tjin2017-05-201-3/+1
| | | | | | | | fs/pstore/ram.c: In function 'ramoops_probe': fs/pstore/ram.c:526:6: error: void value not ignored as it ought to be Change-Id: I8ad52a8955486df59bb8f7d09757fcb8b1a4e036 Signed-off-by: Patrick Tjin <pattjin@google.com>
* pstore: Fix the ramoops module parameters updateWang Long2017-05-201-0/+3
| | | | | | | | | | | | | | In the function ramoops_probe, the console_size, pmsg_size, ftrace_size may be update because the value is not the power of two. We should update the module parameter variables as well so they are visible through /sys/module/ramoops/parameters correctly. Change-Id: I18b89758c2e928b29a9e14edecadc80a3c40d8fb Signed-off-by: Wang Long <long.wanglong@huawei.com> Acked-by: Mark Salyzyn <salyzyn@android.com> Acked-by: Kees Cook <keescook@chromium.org> Signed-off-by: Tony Luck <tony.luck@intel.com>
* fs/pstore: initialize pmsg from device treePatrick Tjin2017-05-201-1/+20
| | | | | | | | | | | - Add pmsg initialization - or_property_read_u32 does not set *out value if case missing. Must initialize _all_ output vars before call. Based on: I5c9bcb7bd43af5a80addecf824f14dd7d63b0064 Change-Id: I2723d407be1ae77d45ad5486a2ddd13b82c5c588 Signed-off-by: Patrick Tjin <pattjin@google.com>
* fs:pstore:ramoops: config mem from dtYi-wei Zhao2017-05-201-1/+62
| | | | | | | | | | | | | | | configure the start & size of ramoops memory using device tree. the "dummy" device is no harm as long as initial mem_size is zero. Conflicts: fs/pstore/ram.c Cherry-picked from: bc4df1ea67057fa2117aa6f5b5a967d2ca2cc846 Change-Id: I756e933bea072399cb80ffd78dc79a42b448fed9 Signed-off-by: Yi-wei Zhao <gbjc64@motorola.com> Reviewed-by: Jeffrey Carlyle <jeff.carlyle@motorola.com> Signed-off-by: Patrick Tjin <pattjin@google.com>
* 3.10.67 -> 3.10.68Jan Engelmohr2016-08-261-5/+8
|
* first commitMeizu OpenSource2016-08-151-0/+622