[PATCH v2 01/18] xen: introduce the pvcalls interface header

2017-05-19 Thread Stefano Stabellini
Introduce the C header file which defines the PV Calls interface. It is imported from xen/include/public/io/pvcalls.h. Signed-off-by: Stefano Stabellini CC: konrad.w...@oracle.com CC: boris.ostrov...@oracle.com CC: jgr...@suse.com --- include/xen/interface/io/pvcalls.h | 120

[PATCH v2 05/18] xen/pvcalls: connect to a frontend

2017-05-19 Thread Stefano Stabellini
Introduce a per-frontend data structure named pvcalls_back_priv. It contains pointers to the command ring, its event channel, a list of active sockets and a tree of passive sockets (passing sockets need to be looked up from the id on listen, accept and poll commands, while active sockets only on re

Re: [PATCH 04/29] printk-formats.txt: standardize document format

2017-05-19 Thread Randy Dunlap
On 05/19/17 13:28, Mauro Carvalho Chehab wrote: > Em Fri, 19 May 2017 03:26:08 -0700 > Joe Perches escreveu: > >> On Thu, 2017-05-18 at 22:25 -0300, Mauro Carvalho Chehab wrote: >>> Each text file under Documentation follows a different >>> format. Some doesn't even have titles! >>> >>> Change it

Re: [PATCH] ARM64: defconfig: enable IR core, decoders and Meson IR device

2017-05-19 Thread Kevin Hilman
Neil Armstrong writes: > This patch enables the MEDIA Infrared RC Decoders and Meson Infrared > decoder for ARM64 defconfig. > These drivers are selected as modules by default. > > Signed-off-by: Neil Armstrong > --- > arch/arm64/configs/defconfig | 5 + > 1 file changed, 5 insertions(+) >

Re: [PATCH] dm ioctl: Restore __GFP_HIGH in copy_params()

2017-05-19 Thread Mikulas Patocka
On Fri, 19 May 2017, Michal Hocko wrote: > On Thu 18-05-17 19:50:46, Junaid Shahid wrote: > > (Adding back the correct linux-mm email address and also adding > > linux-kernel.) > > > > On Thursday, May 18, 2017 01:41:33 PM David Rientjes wrote: > [...] > > > Let's ask Mikulas, who changed this

[PATCH net v2] bonding: fix accounting of active ports in 3ad

2017-05-19 Thread Jarod Wilson
As of 7bb11dc9f59d and 0622cab0341c, bond slaves in a 3ad bond are not removed from the aggregator when they are down, and the active slave count is NOT equal to number of ports in the aggregator, but rather the number of ports in the aggregator that are still enabled. The sysfs spew for bonding_sh

Re: [RFC PATCH 2/2] mm, oom: do not trigger out_of_memory from the #PF

2017-05-19 Thread Tetsuo Handa
Michal Hocko wrote: > On Sat 20-05-17 00:22:30, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > On Fri 19-05-17 22:02:44, Tetsuo Handa wrote: > > > > Michal Hocko wrote: > > > > > Any allocation failure during the #PF path will return with > > > > > VM_FAULT_OOM > > > > > which in turn results i

[PATCH] ipc: Fail build if IPC structures change layout

2017-05-19 Thread Kees Cook
Since struct layout can be seen at build-time, turn runtime report into a build failure so it can be fixed more quickly. Cc: Manfred Spraul Signed-off-by: Kees Cook --- Should be applied on top of the -mm tree's IPC changes --- ipc/msg.c | 5 + ipc/sem.c | 5 + ipc/shm.c | 5 + 3 fi

[PATCH v2 2/3] drm/radeon: Cleanup HDMI audio interrupt handling for evergreen

2017-05-19 Thread Lyude
Same as the previous patch, but now for handling HDMI audio interrupts. Changes since v1: - Preserve the order we write back all registers Signed-off-by: Lyude --- drivers/gpu/drm/radeon/evergreen.c | 153 +++-- drivers/gpu/drm/radeon/radeon.h| 7 +- 2 file

[PATCH v2 1/3] drm/radeon: Cleanup display interrupt handling for evergreen, si

2017-05-19 Thread Lyude
The current code here is really, really bad. A huge amount of it looks to be copy pasted, it has some weird hatred of arrays and code sharing, switch cases everywhere for things that really don't need them, and it makes the file seem immensely more complex then it actually is. This is a pain for ma

[PATCH v2 0/3] Cleanup evergreen/si IRQ handling code

2017-05-19 Thread Lyude
This is the first part of me going through and cleaning up the IRQ handling code for radeon, since after taking a look at it the other day while trying to debug something I realized basically all of the code was copy pasted everywhere, and quite difficult to actually read through. Will come up wit

[PATCH v2 3/3] drm/radeon: Cleanup pageflipping IRQ handling for evergreen, si

2017-05-19 Thread Lyude
Same as the previous patch, but for pageflipping now. This also lets us clear up the copy paste for vblank/vline IRQs. Changes since v1: - Preserve the order all registers are written back Signed-off-by: Lyude --- drivers/gpu/drm/radeon/evergreen.c | 105 --- dri

Re: stackprotector: ascii armor the stack canary

2017-05-19 Thread Daniel Micay
On Fri, 2017-05-19 at 17:26 -0400, r...@redhat.com wrote: > Zero out the first byte of the stack canary value on 64 bit systems, > in order to prevent unterminated C string overflows from being able > to successfully overwrite the canary, even if an attacker somehow > guessed or obtained the canary

Re: [PATCH] dt-bindings: Document optional "reserved-names" property

2017-05-19 Thread Florian Fainelli
On 05/12/2017 04:55 PM, Rob Herring wrote: > On Tue, May 09, 2017 at 10:18:47AM -0700, Florian Fainelli wrote: >> Define an optional string property: "reserved-names" which can be used >> by the client program to tag/identify reserved memory regions. >> >> Signed-off-by: Florian Fainelli >> --- >>

[PATCH v2 5/7] arch/sparc: Enable queued rwlocks for SPARC

2017-05-19 Thread Babu Moger
Enable queued rwlocks for SPARC. Here are the discussions on this feature when this was introduced. https://lwn.net/Articles/572765/ https://lwn.net/Articles/582200/ Cleaned-up the arch_read_xxx and arch_write_xxx definitions in spinlock_64.h. These routines are replaced by the functions in includ

[PATCH v2 3/7] arch/sparc: Define config parameter CPU_BIG_ENDIAN

2017-05-19 Thread Babu Moger
Found this problem while enabling queued rwlock on SPARC. The parameter CONFIG_CPU_BIG_ENDIAN is used to clear the specific byte in qrwlock structure. Without this parameter, we clear the wrong byte. Here is the code. static inline u8 *__qrwlock_write_byte(struct qrwlock *lock) { return (

[PATCH v2 4/7] arch/sparc: Introduce cmpxchg_u8 SPARC

2017-05-19 Thread Babu Moger
SPARC supports 32 bit and 64 bit cmpxchg right now. Add support for 8 bit (1 byte) cmpxchg. This is required to support queued rwlocks feature which uses 1 byte cmpxchg. The function __cmpxchg_u8 here uses the 4 byte cas instruction with a byte manipulation to achieve 1 byte cmpxchg. Signed-off-

[PATCH v2 1/7] kernel/locking: Fix compile error with qrwlock.c

2017-05-19 Thread Babu Moger
Some architectures use the following guard in include file "asm/spinlock_types.h" to discourage including the file directly. Saw these compile errors on SPARC when queued rwlock feature is enabled. CC kernel/locking/qrwlock.o In file included from ./include/asm-generic/qrwlock_types.h:5,

[PATCH v2 6/7] arch/sparc: Introduce xchg16 for SPARC

2017-05-19 Thread Babu Moger
SPARC supports 32 bit and 64 bit xchg right now. Add the support for 16 bit (2 byte) xchg. This is required to support queued spinlock feature which uses 2 byte xchg. This is achieved using 4 byte cas instructions with byte manipulations. Also re-arranged the code to call __cmpxchg_u32 inside xchg

[PATCH v2 2/7] arch/sparc: Remove the check #ifndef __LINUX_SPINLOCK_TYPES_H

2017-05-19 Thread Babu Moger
Remove the un-necessary "ifndef __LINUX_SPINLOCK_TYPES_H" stanza from SPARC. Signed-off-by: Babu Moger Suggested-by: David Miller --- arch/sparc/include/asm/spinlock_types.h |4 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/arch/sparc/include/asm/spinlock_types.h b/ar

[PATCH v2 0/7] Enable queued rwlock and queued spinlock for SPARC

2017-05-19 Thread Babu Moger
This series of patches enables queued rwlock and queued spinlock support for SPARC. These features were introduced some time ago in upstream. Here are some of the earlier discussions. https://lwn.net/Articles/572765/ https://lwn.net/Articles/582200/ https://lwn.net/Articles/561775/ https://lwn.net/

[PATCH v2 7/7] arch/sparc: Enable queued spinlock support for SPARC

2017-05-19 Thread Babu Moger
This patch makes the necessary changes in SPARC architecture to enable queued spinlock support. Here are some of the earlier discussions about this feature. https://lwn.net/Articles/561775/ https://lwn.net/Articles/590243/ Cleaned-up the spinlock_64.h. The definitions of arch_spin_xxx are replaced

Re: [PATCH] x86/mm: synchronize pgd in vmemmap_free()

2017-05-19 Thread John Hubbard
Hi Jerome, On 05/19/2017 11:01 AM, Jérôme Glisse wrote: When we free kernel virtual map we should synchronize p4d/pud for all the pgds to avoid any stall entry in non canonical pgd. "any stale entry in the non-canonical pgd", is what I think you meant to type there. Also, it would be nice to

Re: [PATCH RFC 0/3] Improve stability of system clock

2017-05-19 Thread John Stultz
On Wed, May 17, 2017 at 9:54 PM, Richard Cochran wrote: > On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote: >> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar >> wrote: >> > Is there a better way to run the timekeeping code in an userspace >> > application? I suspect it would need

Re: [PATCH] mm: clarify why we want kmalloc before falling backto vmallock

2017-05-19 Thread John Hubbard
On 05/17/2017 01:09 AM, Michal Hocko wrote: From: Michal Hocko While converting drm_[cm]alloc* helpers to kvmalloc* variants Chris Wilson has wondered why we want to try kmalloc before vmalloc fallback even for larger allocations requests. Let's clarify that one larger physically contiguous blo

Re: mm, something wring in page_lock_anon_vma_read()?

2017-05-19 Thread Xishi Qiu
On 2017/5/20 6:00, Hugh Dickins wrote: > On Fri, 19 May 2017, Xishi Qiu wrote: >> On 2017/5/19 16:52, Xishi Qiu wrote: >>> On 2017/5/18 17:46, Xishi Qiu wrote: >>> Hi, my system triggers this bug, and the vmcore shows the anon_vma seems be freed. The kernel is RHEL 7.2, and the bug

[for-next][PATCH] tracing: Make sure RCU is watching before calling a stack trace

2017-05-19 Thread Steven Rostedt
I'll probably just push this to Linus tomorrow along with my other changes. -- Steve git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next Head SHA1: a33d7d94eed92b23fbbc7b0de06a41b2bbaa49e3 Steven Rostedt (VMware) (1): tracing: Make sure RCU is watching befo

Re: [linux-sunxi] Re: [RFC PATCH 07/11] drm: sun4i: add support for the TV encoder in H3 SoC

2017-05-19 Thread Chen-Yu Tsai
On Sat, May 20, 2017 at 2:23 AM, Jernej Škrabec wrote: > Hi, > > Dne petek, 19. maj 2017 ob 20:08:18 CEST je Icenowy Zheng napisal(a): >> 于 2017年5月20日 GMT+08:00 上午2:03:30, Maxime Ripard electrons.com> 写到: >> >On Thu, May 18, 2017 at 12:43:50AM +0800, Icenowy Zheng wrote: >> >> Allwinner H3 featur

Re: [PATCH v2 1/2] Documentation: dt: Update ti,emif bindings

2017-05-19 Thread Rob Herring
On Fri, May 19, 2017 at 12:57:07PM -0500, Dave Gerlach wrote: > Update the Texas Instruments EMIF binding document to include the device > tree bindings for ti,emif-am3352 and ti,emif-am4372 which are used by > the ti-emif-sram driver to provide low-level PM functionality. > > Signed-off-by: Dave

Re: Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers

2017-05-19 Thread J. R. Okajima
"J. R. Okajima": > I don't know whether the fix is good to me or not yet. I will test your > fix, but I am busy now and my test will be a few weeks later. Other > people may want the fix soon. So I'd suggest you to reproduce the > problem on your side. I guess "mem=1G" or "mem=512M" will make it ea

Re: [linux-sunxi] Re: [RFC PATCH 01/11] dt-bindings: update the binding for Allwinner H3 TVE support

2017-05-19 Thread Chen-Yu Tsai
On Sat, May 20, 2017 at 2:06 AM, Icenowy Zheng wrote: > > > 于 2017年5月20日 GMT+08:00 上午2:02:15, Maxime Ripard > 写到: >>On Thu, May 18, 2017 at 12:43:44AM +0800, Icenowy Zheng wrote: >>> -On SoCs other than the A33 and V3s, there is one more clock >>required: >>> +For the following compatibles: >>>

Re: mm, something wring in page_lock_anon_vma_read()?

2017-05-19 Thread Hugh Dickins
On Sat, 20 May 2017, Xishi Qiu wrote: > On 2017/5/20 6:00, Hugh Dickins wrote: > > > > You're ignoring the rcu_read_lock() on entry to page_lock_anon_vma_read(), > > and the SLAB_DESTROY_BY_RCU (recently renamed SLAB_TYPESAFE_BY_RCU) nature > > of the anon_vma_cachep kmem cache. It is not safe to

Re: [RFC PATCH v2 12/17] cgroup: Remove cgroup v2 no internal process constraint

2017-05-19 Thread Mike Galbraith
On Fri, 2017-05-19 at 16:38 -0400, Tejun Heo wrote: > Hello, Waiman. > > On Mon, May 15, 2017 at 09:34:11AM -0400, Waiman Long wrote: > > The rationale behind the cgroup v2 no internal process constraint is > > to avoid resouorce competition between internal processes and child > > cgroups. Howeve

Re: mm, something wring in page_lock_anon_vma_read()?

2017-05-19 Thread Xishi Qiu
On 2017/5/20 10:02, Hugh Dickins wrote: > On Sat, 20 May 2017, Xishi Qiu wrote: >> On 2017/5/20 6:00, Hugh Dickins wrote: >>> >>> You're ignoring the rcu_read_lock() on entry to page_lock_anon_vma_read(), >>> and the SLAB_DESTROY_BY_RCU (recently renamed SLAB_TYPESAFE_BY_RCU) nature >>> of the ano

[PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts

2017-05-19 Thread Sam Povilus
The number of xilinx ps uart should be set by a kernel parameter instead of using a #define. This allows the user to set the number of xilinx ps uart using only kconfig and not modifying kernel source. The ps uart is used in Xilnx Zynq chips usually in quantities maxing at two, but there may be ot

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

2017-05-19 Thread Masami Hiramatsu
> > > Note on the latest linux-next and on the commit that introduced this the > > > config > > > and kernel yields only *one* page: > > > > > > x86/mm: Checked W+X mappings: FAILED, 1 W+X pages found. > > > > > > I believe this is more indication

Re: mm, something wring in page_lock_anon_vma_read()?

2017-05-19 Thread Hugh Dickins
On Sat, 20 May 2017, Xishi Qiu wrote: > > Here is a bug report form redhat: > https://bugzilla.redhat.com/show_bug.cgi?id=1305620 > And I meet the bug too. However it is hard to reproduce, and > 624483f3ea82598("mm: rmap: fix use-after-free in __put_anon_vma") is not help. > > From the vmcore,

Re: [RESEND: PATCH v4 2/4] remoteproc: qcom: refactor mss fw image loading sequence

2017-05-19 Thread Sricharan R
Hi Bjorn/Avaneesh, On 5/16/2017 11:32 PM, Avaneesh Kumar Dwivedi wrote: > This patch refactor code to first load all firmware blobs > and then update modem proc to authenticate and boot fw. > Also make a trivial change in a error log. > > Signed-off-by: Avaneesh Kumar Dwivedi > --- > drivers/re

Re: mm, something wring in page_lock_anon_vma_read()?

2017-05-19 Thread zhong jiang
On 2017/5/20 10:40, Hugh Dickins wrote: > On Sat, 20 May 2017, Xishi Qiu wrote: >> Here is a bug report form redhat: >> https://bugzilla.redhat.com/show_bug.cgi?id=1305620 >> And I meet the bug too. However it is hard to reproduce, and >> 624483f3ea82598("mm: rmap: fix use-after-free in __put_ano

Re: [PATCH v3] jbd2: preserve original nofs flag during journal restart

2017-05-19 Thread Theodore Ts'o
On Thu, May 18, 2017 at 09:28:50AM -0700, Tahsin Erdogan wrote: > When a transaction starts, start_this_handle() saves current > PF_MEMALLOC_NOFS value so that it can be restored at journal stop time. > Journal restart is a special case that calls start_this_handle() without > stopping the transact

RE: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

2017-05-19 Thread Cheng, Collins
Hi Alex, Yes, I hope kernel can disable SR-IOV and related VF resource allocation if the system BIOS is not SR-IOV capable. Adding the parameter "pci=nosriov" sounds a doable solution, but it would need user to add this parameter manually, right? I think an automatic detection would be better.

Re: [PATCH 7/7] DWARF: add the config option

2017-05-19 Thread Andy Lutomirski
On Fri, May 19, 2017 at 2:35 PM, Josh Poimboeuf wrote: > On Fri, May 19, 2017 at 04:29:13PM -0500, Josh Poimboeuf wrote: >> > How are you handling control flow? >> >> Control flow of what? >> >> > > Here's the struct in its current state: >> > > >> > > #define UNDWARF_REG_UNDEFINED 0 >

Re: [4.12 regression] Thinkpad X250 Touchpad and Trackpoint not recognized anymore; commit e839ffa: "Input: synaptics - add support for Intertouch devices"

2017-05-19 Thread Pascal Wichmann
> Looks like you running your patched kernel? That's right. >>> CONFIG_RMI4_CORE=m >>> CONFIG_RMI4_I2C=m >>> CONFIG_RMI4_SPI=m >>> # CONFIG_RMI4_SMB is not set > > This is your issue I believe. Indeed, enabling that configuration solves that issue. However, I think it is quite unintuitive that

Re: [PATCH v2 1/5] pinctrl: qcom: Add ipq8074 pinctrl driver

2017-05-19 Thread Bjorn Andersson
On Thu 18 May 01:39 PDT 2017, Varadarajan Narayanan wrote: > > > On 5/18/2017 1:03 AM, Bjorn Andersson wrote: > > On Mon 15 May 02:05 PDT 2017, Varadarajan Narayanan wrote: > > > > > On 5/14/2017 9:53 AM, Bjorn Andersson wrote: > > > > On Thu 11 May 03:33 PDT 2017, Varadarajan Narayanan wrote:

[PATCH 0/2] Enhance libsas hotplug feature

2017-05-19 Thread Yijing Wang
Now the libsas hotplug has some issues, Dan Williams report a similar bug here before https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html The issues we have found 1. if LLDD burst reports lots of phy-up/phy-down sas events, some events may lost because a same sas events is pen

[PATCH 1/2] libsas: Don't process sas events in static works

2017-05-19 Thread Yijing Wang
Now libsas hotplug work is static, LLDD driver queue the hotplug work into shost->work_q. If LLDD driver burst post lots hotplug events to libsas, the hotplug events may pending in the workqueue like shost->work_q new work[PORTE_BYTES_DMAED] --> |[PHYE_LOSS_OF_SIGNAL][PORTE_BYTES_DMAED] -> proces

[PATCH 2/2] libsas: Enhance libsas hotplug

2017-05-19 Thread Yijing Wang
Libsas complete a hotplug event notified by LLDD in several works, for example, if libsas receive a PHYE_LOSS_OF_SIGNAL, we process it in following steps: notify_phy_event[interrupt context] sas_queue_event [queue work on shost->work_q] sas_phye_loss_of_sign

Re: [PATCH] regmap: add regmap_debugfs_exit as devres action

2017-05-19 Thread Stefan Agner
On 2017-05-19 09:46, Mark Brown wrote: > On Mon, May 15, 2017 at 01:08:27AM -0700, Stefan Agner wrote: > >> Instead of manually cleanup regmap_debugfs_exit, use devres action >> to do the cleanup. This also works for external users of >> regmap_attach_dev. > > Why? It's also not clear to me that

Re: [PATCH 3/3][v4] staging: fsl-mc: move bus driver out of staging

2017-05-19 Thread Marc Zyngier
On Fri, May 19 2017 at 02:41:43 PM, Matthias Brugger wrote: > On 19/05/17 15:13, laurentiu.tu...@nxp.com wrote: >> From: Stuart Yoder >> >> Move the source files out of staging into their final locations: >>-include files in drivers/staging/fsl-mc/include go to include/linux/fsl >>-irq-g

[PATCHv2 0/3] Enable no_cache flag to driver_data

2017-05-19 Thread yi1 . li
From: Yi Li Changes in v2: - Rebase to Luis R. Rodriguez's 20170501-driver-data-try2 branch - Expose DRIVER_DATA_REQ_NO_CACHE flag to public driver_data_req_params structure, so upper drivers can ask driver_data driver to bypass the internal caching mechanism. This will be

[PATCHv2 1/3] firmware_class: move NO_CACHE from private to driver_data_req_params

2017-05-19 Thread yi1 . li
From: Yi Li This adds DRIVER_DATA_REQ_NO_CACHE flag with .req flag under struct driver_data_req_params. When this flag is set, the driver_data driver will bypass the internal caching mechanism, its used by streaming case and other drivers which implement their own cache thing. Signed-off-by: Yi

[PATCHv2 2/3] iwlwifi: use DRIVER_DATA_REQ_NO_CACHE for driver_data

2017-05-19 Thread yi1 . li
From: Yi Li Set DRIVER_DATA_REQ_NO_CACHE flag to disable driver_data driver caching mechanism, iwlwifi has its own firmware cache management. Signed-off-by: Yi Li --- drivers/net/wireless/intel/iwlwifi/iwl-drv.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/wireless/intel/i

[PATCHv2 1/2] firmware: Enable pre-allocated buffer support in driver_data

2017-05-19 Thread yi1 . li
From: Yi Li This enables the equivalent feature of the legacy request_firmware_into_buf to driver_data, so caller can allocate and manage the firmware buffer instead of by driver_data class internally. The caller need to setup alloc_buf and alloc_buf_size in the @driver_data_req_params structure.

[PATCHv2 3/3] test: add no_cache to driver_data load tester

2017-05-19 Thread yi1 . li
From: Yi Li This adds a no_cache flag to simple sync and async test. Signed-off-by: Yi Li --- lib/test_driver_data.c | 43 +++-- tools/testing/selftests/firmware/driver_data.sh | 36 + 2 files changed, 76 insertions(+), 3 deletio

[PATCHv2 0/2] Enable pre-allocated buffer support for driver_data

2017-05-19 Thread yi1 . li
From: Yi Li This series enables the equivalent pre-allocated buffer feature in request_firmware_into_buf to driver_data API, so caller can allocate firmware data buffer and pass to driver_data. This will be used for streaming support of driver_data, which allow caller to manage the size and buff

[PATCHv2 2/2] test: add pre-allocated buffer to driver_data tester

2017-05-19 Thread yi1 . li
From: Yi Li This adds pre-allocated buffer test cases to the simple sync and async test. Signed-off-by: Yi Li --- lib/test_driver_data.c | 68 - tools/testing/selftests/firmware/driver_data.sh | 36 + 2 files changed, 103 insertions(

[PATCHv2 2/3] test: add streaming test to driver_data tester

2017-05-19 Thread yi1 . li
From: Yi Li This adds streaming test case, which pre-allocate the buffer and ask driver_data_request_sync API to read 4KB each. Since the dummy firmware image is very small, the test only stream couple bytes. A manual test method: echo -n 'bigfile' > /sys/devices/virtual/misc/test_driver_data0/co

[PATCHv2 0/3] Add streaming support to driver_data API

2017-05-19 Thread yi1 . li
From: Yi Li This series enables the streaming support on driver_data sync API and add self test and FPGA mgr to test/use stream firmware in 4KB trucks. Changes in v2: - Rebase to Luis R. Rodriguez's 20170501-driver-data-try2 branch - Expended fw_get_filesystem_firmware function and a

[PATCHv2 3/3] fpga_mgr: Add streaming support through the new driver_data API

2017-05-19 Thread yi1 . li
From: Yi Li Since the FPGA image are getting bigger in size, this add an new API fpga_mgr_firmware_stream in FPGA manager, which will stream FPGA image in 4KB trunks. Signed-off-by: Yi Li --- drivers/fpga/fpga-mgr.c | 111 ++ include/linux/fpga/fpg

[PATCHv2 1/3] firmware: Add streaming support for driver_data_request_sync API

2017-05-19 Thread yi1 . li
From: Yi Li By setting the driver_data_req_params req flag of DRIVER_DATA_REQ_STREAMING and DRIVER_DATA_REQ_NO_CACHE, caller can streaming firmware image to the pre-allocated buffer in small trunks. Caller also need to setup the img_offset pointer and firmware image **path to avoid searching the

[RFC PATCH] vmalloc: show more detail info in vmallocinfo for clarify

2017-05-19 Thread Yisheng Xie
When ioremap a 67112960 bytes vm_area with the vmallocinfo: [..] 0xec79b000-0xec7fa000 389120 ftl_add_mtd+0x4d0/0x754 pages=94 vmalloc 0xec80-0xecbe1000 4067328 kbox_proc_mem_write+0x104/0x1c4 phys=8b52 ioremap we get result: 0xf100-0xf5001000 67112960 devm_ioremap+0x38/0x7c phys

<    4   5   6   7   8   9