[PATCH] iommu/io-pgtable-arm: hide unused ipmmu_iotlb_sync

There are two sets of iommu_ops in this driver, and only one of them contains a reference to the ipmmu_iotlb_sync function. This leads to a compiler warning when these operations are not in use: drivers/iommu/ipmmu-vmsa.c:622:13: error: 'ipmmu_iotlb_sync' defined but not used [-Werror=unused-func

[PATCH v5 09/22] mm: Cache some VMA fields in the vm_fault structure

When handling speculative page fault, the vma->vm_flags and vma->vm_page_prot fields are read once the page table lock is released. So there is no more guarantee that these fields would not change in our back. They will be saved in the vm_fault structure before the VMA is checked for changes. This

[PATCH] fm10k: mark PM functions as __maybe_unused

A cleanup of the PM code left an incorrect #ifdef in place, leading to a harmless build warning: drivers/net/ethernet/intel/fm10k/fm10k_pci.c:2502:12: error: 'fm10k_suspend' defined but not used [-Werror=unused-function] drivers/net/ethernet/intel/fm10k/fm10k_pci.c:2475:12: error: 'fm10k_resume'

Re: [PATCH V8 00/14] mmc: Add Command Queue support

On 11 October 2017 at 14:58, Adrian Hunter wrote: > On 11/10/17 15:13, Ulf Hansson wrote: >> On 10 October 2017 at 15:31, Adrian Hunter wrote: >>> On 10/10/17 16:08, Ulf Hansson wrote: [...] I have also run some test on my ux500 board and enabling the blkmq pa

[PATCH v5 13/22] mm: Introduce __maybe_mkwrite()

The current maybe_mkwrite() is getting passed the pointer to the vma structure to fetch the vm_flags field. When dealing with the speculative page fault handler, it will be better to rely on the cached vm_flags value stored in the vm_fault structure. This patch introduce a __maybe_mkwrite() servi

[PATCH v5 12/22] mm: Introduce __lru_cache_add_active_or_unevictable

The speculative page fault handler which is run without holding the mmap_sem is calling lru_cache_add_active_or_unevictable() but the vm_flags is not guaranteed to remain constant. Introducing __lru_cache_add_active_or_unevictable() which has the vma flags value parameter instead of the vma pointer

[PATCH v5 11/22] mm/migrate: Pass vm_fault pointer to migrate_misplaced_page()

migrate_misplaced_page() is only called during the page fault handling so it's better to pass the pointer to the struct vm_fault instead of the vma. This way during the speculative page fault path the saved vma->vm_flags could be used. Signed-off-by: Laurent Dufour --- include/linux/migrate.h |

[PATCH] xhci: Set DMA parameters appropriately

xHCI requires that data buffers do not cross 64KB boundaries (and are thus at most 64KB long as well) - whilst xhci_queue_{bulk,isoc}_tx() already split their input buffers into individual TRBs as necessary, it's still a good idea to advertise the limitations via the standard DMA API mechanism, so

[PATCH v5 16/22] mm: Provide speculative fault infrastructure

From: Peter Zijlstra Provide infrastructure to do a speculative fault (not holding mmap_sem). The not holding of mmap_sem means we can race against VMA change/removal and page-table destruction. We use the SRCU VMA freeing to keep the VMA around. We use the VMA seqcount to detect change (includi

Re: [PATCH] [net-next] ip_tunnel: fix building with NET_IP_TUNNEL=m

I forgot to Cc Amine, sorry. On Wed, Oct 11, 2017 at 3:55 PM, Arnd Bergmann wrote: > When af_mpls is built-in but the tunnel support is a module, > we get a link failure: > > net/mpls/af_mpls.o: In function `mpls_init': > af_mpls.c:(.init.text+0xdc): undefined reference to `ip_tunnel_encap_add_op

[PATCH] f2fs: add bug_on when f2fs_gc even fails to get one victim

This can help us to debug on some corner case. Signed-off-by: Yunlong Song --- fs/f2fs/gc.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c index 197ebf4..960503e 100644 --- a/fs/f2fs/gc.c +++ b/fs/f2fs/gc.c @@ -986,6 +986,7 @@ int f2fs_gc(str

[PATCH v5 14/22] mm: Introduce __vm_normal_page()

When dealing with the speculative fault path we should use the VMA's field cached value stored in the vm_fault structure. Currently vm_normal_page() is using the pointer to the VMA to fetch the vm_flags value. This patch provides a new __vm_normal_page() which is receiving the vm_flags flags value

[PATCH v5 17/22] mm: Try spin lock in speculative path

There is a deadlock when a CPU is doing a speculative page fault and another one is calling do_unmap(). The deadlock occurred because the speculative path try to spinlock the pte while the interrupt are disabled. When the other CPU in the unmap's path has locked the pte then is waiting for all the

[PATCH] [net-next] ip_tunnel: fix building with NET_IP_TUNNEL=m

When af_mpls is built-in but the tunnel support is a module, we get a link failure: net/mpls/af_mpls.o: In function `mpls_init': af_mpls.c:(.init.text+0xdc): undefined reference to `ip_tunnel_encap_add_ops' This adds a Kconfig statement to prevent the broken configuration and force mpls to be a m

RE: [PATCH 1/1] vmbus: hvsock: add proper sync for vmbus_hvsock_device_unregister()

Thanks Dan. Will do. K. Y > -Original Message- > From: Dan Carpenter [mailto:dan.carpen...@oracle.com] > Sent: Wednesday, October 11, 2017 2:42 AM > To: KY Srinivasan > Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; o...@aepfle.de; a...@cano

[PATCH] mtd: cfi: convert inline functions to macros

The map_word_() functions, dating back to linux-2.6.8, try to perform bitwise operations on a 'map_word' structure. This may have worked with compilers that were current then (gcc-3.4 or earlier), but end up being rather inefficient on any version I could try now (gcc-4.4 or higher). Specifically w

Re: [PATCH v6 4/4] perf vendor events arm64: Add ThunderX2 implementation defined pmu core events

On Wed, Oct 11, 2017 at 03:24:31PM +0200, Robert Richter wrote: > On 11.10.17 13:19:27, Will Deacon wrote: > > On Tue, Aug 29, 2017 at 02:47:30PM +0200, Robert Richter wrote: > > > Shaokun, > > > > > > On 29.08.17 17:26:00, Zhangshaokun wrote: > > > > On 2017/8/24 20:03, Ganapatrao Kulkarni wrote:

[PATCH v5 18/22] mm: Adding speculative page fault failure trace events

This patch a set of new trace events to collect the speculative page fault event failures. Signed-off-by: Laurent Dufour --- include/trace/events/pagefault.h | 87 mm/memory.c | 59 ++- 2 files changed, 135 ins

[PATCH v5 21/22] x86/mm: Add speculative pagefault handling

From: Peter Zijlstra Try a speculative fault before acquiring mmap_sem, if it returns with VM_FAULT_RETRY continue with the mmap_sem acquisition and do the traditional fault. Signed-off-by: Peter Zijlstra (Intel) [Clearing of FAULT_FLAG_ALLOW_RETRY is now done in handle_speculative_fault()] [

[PATCH v5 22/22] powerpc/mm: Add speculative page fault

This patch enable the speculative page fault on the PowerPC architecture. This will try a speculative page fault without holding the mmap_sem, if it returns with VM_FAULT_RETRY, the mmap_sem is acquired and the traditional page fault processing is done. Build on if CONFIG_SPF is defined (currentl

[PATCH v5 20/22] perf tools: Add support for the SPF perf event

Add support for the new speculative faults event. Signed-off-by: Laurent Dufour --- tools/include/uapi/linux/perf_event.h | 1 + tools/perf/util/evsel.c | 1 + tools/perf/util/parse-events.c| 4 tools/perf/util/parse-events.l| 1 + tools/perf/util/python.c

[PATCH v5 19/22] perf: Add a speculative page fault sw event

Add a new software event to count succeeded speculative page faults. Signed-off-by: Laurent Dufour --- include/uapi/linux/perf_event.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h index 140ae638cfd6..101e509ee39b 100644 ---

Re: [PATCH v4] HID: hid-multitouch: support fine-grain orientation reporting

On Oct 11 2017 or thereabouts, Jiri Kosina wrote: > On Wed, 11 Oct 2017, Benjamin Tissoires wrote: > > > I am not sure if libinput even uses ABS_MT_ORIENTATION > > I don't think it does, so that should be okay. However ... I had a meeting this Peter at noon today. The summary is that libinput do

[PATCH v5 15/22] mm: Introduce __page_add_new_anon_rmap()

When dealing with speculative page fault handler, we may race with VMA being split or merged. In this case the vma->vm_start and vm->vm_end fields may not match the address the page fault is occurring. This can only happens when the VMA is split but in that case, the anon_vma pointer of the new VM

[PATCH v5 10/22] mm: Protect SPF handler against anon_vma changes

The speculative page fault handler must be protected against anon_vma changes. This is because page_add_new_anon_rmap() is called during the speculative path. In addition, don't try speculative page fault if the VMA don't have an anon_vma structure allocated because its allocation should be protec

[PATCH v5 02/22] powerpc/mm: Define CONFIG_SPF

Define CONFIG_SPF for BOOK3S_64 and SMP. This enables the Speculative Page Fault handler. Support is only provide for BOOK3S_64 currently because: - require CONFIG_PPC_STD_MMU because checks done in set_access_flags_filter() - require BOOK3S because we can't support for book3e_hugetlb_preload()

[PATCH v5 05/22] mm: Introduce pte_spinlock for FAULT_FLAG_SPECULATIVE

When handling page fault without holding the mmap_sem the fetch of the pte lock pointer and the locking will have to be done while ensuring that the VMA is not touched in our back. So move the fetch and locking operations in a dedicated function. Signed-off-by: Laurent Dufour --- mm/memory.c |

[PATCH v5 01/22] x86/mm: Define CONFIG_SPF

Introduce CONFIG_SPF which turns on the Speculative Page Fault handler when building for 64bits with SMP. Signed-off-by: Laurent Dufour --- arch/x86/Kconfig | 4 1 file changed, 4 insertions(+) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 063f1e0d51aa..a726618b7018 100644 --- a/a

[PATCH] ARM: don't discard memblock for kexec

Discarding the memblock arrays usually works, but causes problems with kexec, as pointed out by this kbuild warning: WARNING: vmlinux.o(.text+0x7c60): Section mismatch in reference from the function machine_kexec_prepare() to the function .meminit.text:memblock_is_region_memory() This lets us k

Re: [PATCH v16 5/5] virtio-balloon: VIRTIO_BALLOON_F_CTRL_VQ

On Wed, Oct 11, 2017 at 02:03:20PM +0800, Wei Wang wrote: > On 10/10/2017 11:15 PM, Michael S. Tsirkin wrote: > > On Mon, Oct 02, 2017 at 04:38:01PM +, Wang, Wei W wrote: > > > On Sunday, October 1, 2017 11:19 AM, Michael S. Tsirkin wrote: > > > > On Sat, Sep 30, 2017 at 12:05:54PM +0800, Wei W

[PATCH 2/2] Bluetooth: BT_HCIUART now depends on SERIAL_DEV_BUS

It is no longer possible to build BT_HCIUART into the kernel when SERIAL_DEV_BUS is a loadable module, even if none of the SERIAL_DEV_BUS based implementations are selected: drivers/bluetooth/hci_ldisc.o: In function `hci_uart_set_flow_control': hci_ldisc.c:(.text+0xb40): undefined reference to `

[PATCH 1/2] Bluetooth: hci_bcm: fix build error without CONFIG_PM

This was introduced by the rework adding PM support: drivers/bluetooth/hci_bcm.c: In function 'bcm_device_exists': drivers/bluetooth/hci_bcm.c:156:22: error: 'struct bcm_device' has no member named 'hu' if (device && device->hu && device->hu->serdev) ^~ The pointer is not

Re: [PATCH v3 6/8] PM / devfreq: Remove unneeded conditional statement

On Wed, Oct 11, 2017 at 8:36 PM, MyungJoo Ham wrote: >> The commit 0ec09ac2cebe9 ("PM / devfreq: Set the freq_table of devfreq >> device") initializes the freq_table array of each devfreq device always. >> In result, it is unneeded to check whether profile->freq_table is NULL >> or not. >> >> Sign

[PATCH] configfs: make function arguments const

This is a followup patch for: https://lkml.org/lkml/2017/10/11/375 Make the struct config_item_type *type function argument of functions config_{item/group}_init_type_name const as the argument in both the functions is only stored in the ci_type field of a config_item structure which is const. Mak

Re: [PATCH] fs/afs/flock and fs/locks: Fix possible sleep-in-atomic bugs in posix_lock_file

On Wed, Oct 11, 2017 at 10:47:43AM +0100, David Howells wrote: > J. Bruce Fields wrote: > > > Does that mean nobody's tested fcntl locking over afs since that change in > > 2010? > > Quite feasibly not. I've been beating kAFS into shape and I'm aware of the > lock thing. It's on the list after

Re: [PATCH 1/2] IB/hfi1: Use preempt_{dis,en}able_nort()

Em Wed, Oct 11, 2017 at 01:03:55PM +0200, Sebastian Andrzej Siewior escreveu: > On 2017-10-10 16:02:18 [-0300], Arnaldo Carvalho de Melo wrote: > > > > Right, and so far there were no strong objection for this one to be > > merged on the -rt tree, Sebastian, can you do it please? Adding Dennis' >

Re: [PATCH 2/2] IB/hfi1: Handle packets in the theaded handler only

Em Wed, Oct 11, 2017 at 12:44:56PM +0200, Sebastian Andrzej Siewior escreveu: > On 2017-10-10 16:15:29 [-0300], Arnaldo Carvalho de Melo wrote: > > This may not even be needed, i.e. Sebastian Siewior said that recent > > rt patches already identify the way this driver uses threaded interrupts > > a

Re: [PATCH v2] livepatch: unpatch all klp_objects if klp_module_coming fails

On Mon, 2 Oct 2017, Joe Lawrence wrote: > When an incoming module is considered for livepatching by > klp_module_coming(), it iterates over multiple patches and multiple > kernel objects in this order: > > list_for_each_entry(patch, &klp_patches, list) { > klp_for_each_object(

Re: [PATCH] rtl8xxxu: mark expected switch fall-throughs

On 10/11/2017 04:41 AM, Kalle Valo wrote: Jes Sorensen writes: On 10/10/2017 03:30 PM, Gustavo A. R. Silva wrote: In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. While this isn't harmful, to me this looks like pointless patch chur

Re: [PATCH] pci: Fix a possible sleep-in-atomic bug in pci_set_power_state

On Mon, Oct 09, 2017 at 12:15:17PM -0500, Bjorn Helgaas wrote: > I assume it's easy to produce an actual failure here? Why haven't we > seen bug reports about this? The bug was detected with static analysis. You have to enable a debug feature in the .config if you want sleeping with spinlock hel

Re: [PATCH v3 5/8] PM / devfreq: Get the available next frequency on update_devfreq()

On Wed, Oct 11, 2017 at 8:30 PM, MyungJoo Ham wrote: >> The update_devfreq() considers only user frequency (min_freq/max_freq) >> and the next target_freq provided by the governor. But, the commit >> a76caf55e5b35 ("thermal: Add devfreq cooling") is able to disable >> OPP as a cooling device. In r

Re: [PATCH v3 12/33] tracing: Add variable support to hist triggers

Hi Namhyung, On Mon, 2017-10-09 at 12:27 +0900, Namhyung Kim wrote: > Hi Tom, > > On Fri, Sep 22, 2017 at 02:59:52PM -0500, Tom Zanussi wrote: > > Add support for saving the value of a current event's event field by > > assigning it to a variable that can be read by a subsequent event. > > > > T

[PATCH 5/9] staging: fsl-dpaa2/eth: Refactor interrupt arming in NAPI poll

Take into consideration the return value of napi_complete_done(), since there might be an indication that it's not suitable to enable driver interrupts yet. Signed-off-by: Bogdan Purcareata --- drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 2/9] staging: fsl-dpaa2/eth: Account for Rx FD buffers on error path

On Rx path, if we fail to build an skb from the incoming FD, we still need to update the channel buffer count accordingly, otherwise we risk depleting the pool while the software counter still sees available buffers. Signed-off-by: Ioana Radulescu --- drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth

Re: [PATCH] vmalloc: add __alloc_vm_area() for optimizing vmap stack

On 08.10.2017 12:16, Christoph Hellwig wrote: This looks fine in general, but a few comments: - can you split adding the new function from switching over the fork codeok - at least kasan and vmalloc_user/vmalloc_32_user use very similar patterns, can you switch them over as well?

[PATCH 9/9] staging: fsl-dpaa2/eth: Add firmware version

Include firmware version in the driver information exported through ethtool. Signed-off-by: Ioana Radulescu --- drivers/staging/fsl-dpaa2/ethernet/dpaa2-ethtool.c | 14 +- drivers/staging/fsl-dpaa2/ethernet/dpni-cmd.h | 5 drivers/staging/fsl-dpaa2/ethernet/dpni.c | 3

[PATCH 8/9] staging: fsl-dpaa2/eth: Don't use netdev_err too early

Early during probe the netdevice name is not initialized yet, so use dev_err instead of netdev_err when printing error messages. Signed-off-by: Ioana Radulescu --- drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/f

[PATCH 7/9] staging: fsl-dpaa2/eth: Use implicit clear of link interrupt

dpni_get_irq_status() also looks at the input value of its status parameter, and if not null it automatically clears from pending state the bits that are set there. Use this feature to avoid a separate MC command for clearing the interrupt event bits after reading the status. Signed-off-by: Ioana

[PATCH 6/9] staging: fsl-dpaa2/eth: Fix double DMA unmap

In case we fail to allocate a skb for a fragmented ingress frame, the cleanup function will attempt to unmap again the first frame fragment, which had already been unmapped during early Rx processing. Avoid this by freeing the first buffer immediately in case we hit an error, leaving the cleanup f

[PATCH 4/9] staging: fsl-dpaa2/eth: Check if notification rearm is successful

In case dpaa2_io_service_rearm() fails with an error other then EBUSY, it will do so silently; add a check for this and a warning message, as a failure here means we're unable to receive any more traffic on the current cpu. Signed-off-by: Ioana Radulescu --- drivers/staging/fsl-dpaa2/ethernet/dp

Re: [PATCH v4] HID: hid-multitouch: support fine-grain orientation reporting

On Wed, 11 Oct 2017, Benjamin Tissoires wrote: > I am not sure if libinput even uses ABS_MT_ORIENTATION I don't think it does, so that should be okay. However ... > , but I'd go for fixing the documentation. And re-reading it, it's not > clear that the doc tells us to have [0,90]. It mentions n

Re: [PATCH net-next 2/2] net sched act_vlan: VLAN action rewrite to use RCU lock/unlock and update

On Wed, 2017-10-11 at 06:10 -0700, Eric Dumazet wrote: > On Tue, 2017-10-10 at 22:33 -0400, Manish Kurup wrote: > > Using a spinlock in the VLAN action causes performance issues when the VLAN > > action is used on multiple cores. Rewrote the VLAN action to use RCU read > > locking for reads and upd

[PATCH 3/9] staging: fsl-dpaa2/eth: Check SGT final bit is present

For scatter-gather ingress frames, we expect to receive a list of fragments from the hardware, last of which is marked with a "final" bit. Add a check to make sure the Rx frame has this bit set correctly; there's not much we can do in case of a malformed frame, but at least issue a warning. Signe

[PATCH 1/9] staging: fsl-dpaa2/eth: Fix potential endless loop

We incorrectly assumed that dpaa2_io_release() can only return -EBUSY as an error code, when in fact it can also fail in case some of its arguments don't have valid values. Make sure we only retry the operation while the portal is busy and abort for all other error cases, otherwise we risk enterin

Re: [PATCHv2 0/7] Add support for USB OTG on STM32F7

Hi, Alexandre Torgue writes: > Hi > > On 10/11/2017 01:50 PM, Felipe Balbi wrote: >> >> Hi, >> >> Alexandre Torgue writes: >>> Hi Felip >>> >>> On 10/11/2017 12:04 PM, Felipe Balbi wrote: Hi, Amelie Delaunay writes: > The STM32F7 MCU family embeds two DWC2 USB OTG cor

Re: [PATCH] scsi: use set_host_byte instead of open-coding it

On Wed, Oct 11, 2017 at 03:05:40PM +0200, Steffen Maier wrote: > Maybe I misunderstand, but doesn't set_host_byte only set the host byte but > leave the other 3 parts untouched in c->result? > > static inline void set_host_byte(struct scsi_cmnd *cmd, char status) > { > cmd->result = (cmd->re

[PATCH] f2fs: update dirty status for CURSEG as well

Without this patch, it will cause all the free segments using up in some corner case. For example, there are 100 segments, and 20 of them are reserved for ovp. If 79 segments are full of data, segment 80 becomes CURSEG segment, write 512 blocks and then delete 511 blocks. Since it is CURSEG segment

Re: [PATCH] drivers: Adding driver support for "One by Wacom CTL472/672" (parameters transferred from CTL471/671 since only difference is the force resolution)

On Sun, 8 Oct 2017, ? ?? wrote: > Signed-off-by: Mx Jing Changelog is missing, please provide one. Adding Jason and Ping to CC. > --- > drivers/hid/wacom_wac.c | 8 > 1 file changed, 8 insertions(+) > > diff --git a/drivers/hid/wacom_wac.c b/drivers/hid/wacom_wac.c > index aa692e28b

Re: [PATCH v6 4/4] perf vendor events arm64: Add ThunderX2 implementation defined pmu core events

On 11.10.17 13:19:27, Will Deacon wrote: > On Tue, Aug 29, 2017 at 02:47:30PM +0200, Robert Richter wrote: > > Shaokun, > > > > On 29.08.17 17:26:00, Zhangshaokun wrote: > > > On 2017/8/24 20:03, Ganapatrao Kulkarni wrote: > > > > This is not a full event list, but a short list of useful events. >

Re: [PATCH V9 00/15] mmc: Add Command Queue support

On 27 September 2017 at 00:25, Ulf Hansson wrote: > On 22 September 2017 at 14:36, Adrian Hunter wrote: >> Hi >> >> Here is V9 of the hardware command queue patches without the software >> command queue patches, now using blk-mq and now with blk-mq support for >> non-CQE I/O. >> >> HW CMDQ offers

Re: [PATCH] HID: usbhid: Convert timers to use timer_setup()

On Wed, 4 Oct 2017, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. Adds pointer back to hid_device for > multitouch. Applied, thank

Re: [PATCH 4.13 000/160] 4.13.6-stable review

On 10/10/2017 12:48 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.13.6 release. There are 160 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be m

Re: [PATCH 4.9 000/105] 4.9.55-stable review

On 10/10/2017 12:49 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.55 release. There are 105 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be m

Re: [PATCH 4.4 00/47] 4.4.92-stable review

On 10/10/2017 12:50 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.92 release. There are 47 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be ma

Re: [PATCH v2 1/4] kmemcheck: remove annotations

On Sat 07-10-17 03:02:13, Sasha Levin wrote: > Remove kmemcheck annotations, and calls to kmemcheck from the kernel. How did you generate this? I suspect a git grep + sed? Because this doesn't seem to be correct. I didn't get further than this > @@ -266,7 +264,6 @@ static inline int dma_map_sg_at

Re: [PATCH net-next 1/2] net sched act_vlan: Change stats update to use per-core stats

Wed, Oct 11, 2017 at 04:32:27AM CEST, kurup.man...@gmail.com wrote: >The VLAN action maintains one set of stats across all cores, and uses a >spinlock to synchronize updates to it from the same. Changed this to use a >per-CPU stats context instead. >This change will result in better performance. >

RE: [PATCH] perf tools: fix: Force backward ring buffer mapped readonly

> perf record's --overwrite option doesn't work as we expect. > For example: > > $ ~/linux/tools/perf$ sudo rm ./perf.data* > rm: cannot remove './perf.data*': No such file or directory > : ~/linux/tools/perf$ sudo ./perf record -m 4 -e raw_syscalls:* -g -- > overwrite \ >

Re: [PATCH 0/6] Cache coherent device memory (CDM) with HMM v5

On Sun, Oct 1, 2017 at 6:49 AM, Jerome Glisse wrote: > On Sat, Sep 30, 2017 at 10:57:38AM +0800, Bob Liu wrote: >> On 2017/9/27 0:16, Jerome Glisse wrote: >> > On Tue, Sep 26, 2017 at 05:56:26PM +0800, Bob Liu wrote: >> >> On Tue, Sep 12, 2017 at 7:36 AM, Jerome Glisse wrote: >> >>> On Sun, Sep 1

Re: [PATCH v3 4/8] PM / devfreq: Show the all available frequencies

On Wed, Oct 11, 2017 at 8:26 PM, MyungJoo Ham wrote: >> The commit a76caf55e5b35 ("thermal: Add devfreq cooling") allows >> the devfreq device to use the cooling device. When the cooling down >> are required, the devfreq_cooling.c disables the OPP entry with >> the dev_pm_opp_disable(). In result,

Re: [PATCH] arm64: remove unneeded copy to init_utsname()->machine

Hi, On Wed, Oct 11, 2017 at 10:03:28PM +0900, Masahiro Yamada wrote: > Hi arm64 maintainers, > > Could you check this please? This patch has been queued [1] in arm64's for-next/core branch [2], and should be in v4.15. Thanks, Mark. [1] https://git.kernel.org/pub/scm/linux/kernel/git/arm64/lin

Re: [PATCH net-next 2/2] net sched act_vlan: VLAN action rewrite to use RCU lock/unlock and update

Wed, Oct 11, 2017 at 04:33:39AM CEST, kurup.man...@gmail.com wrote: >Using a spinlock in the VLAN action causes performance issues when the VLAN >action is used on multiple cores. Rewrote the VLAN action to use RCU read >locking for reads and updates instead. > >Signed-off-by: Manish Kurup >--- >

Re: [PATCH] MIPS: Fix exception entry when CONFIG_EVA enabled

On 10/11/2017 03:59 AM, Matt Redfearn wrote: Commit 9fef68686317b ("MIPS: Make SAVE_SOME more standard") made several changes to the order in which registers are saved in the SAVE_SOME macro, used by exception handlers to save the processor state. In particular, it removed the move k1, sp in th

Re: [PATCH 3.18 00/32] 3.18.75-stable review

On 10/10/2017 12:50 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 3.18.75 release. There are 32 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be m

Re: ftrace: Save module init functions kallsyms symbols for tracing

On Wed, 11 Oct 2017 13:19:42 +0200 Jessica Yu wrote: > Unfortunately, my next two weeks are looking grim, so I don't think I > can invest too much time on this before the 4.15 merge window :-/ I > don't want to slow you down, so for now please continue with what you > have, but I can gladly revis

Re: [PATCH net-next 2/2] net sched act_vlan: VLAN action rewrite to use RCU lock/unlock and update

On Tue, 2017-10-10 at 22:33 -0400, Manish Kurup wrote: > Using a spinlock in the VLAN action causes performance issues when the VLAN > action is used on multiple cores. Rewrote the VLAN action to use RCU read > locking for reads and updates instead. > > Signed-off-by: Manish Kurup > --- > includ

Re: [v11 3/6] mm, oom: cgroup-aware OOM killer

On Tue 10-10-17 14:13:00, David Rientjes wrote: [...] > For these reasons: unfair comparison of root mem cgroup usage to bias > against that mem cgroup from oom kill in system oom conditions, the > ability of users to completely evade the oom killer by attaching all > processes to child cgroups

[PATCH] configfs: make ci_type field and some pointers const

The ci_type field of the config_item structure do not modify the fields of the config_item_type structure it points to. And the other pointers initialized with ci_type do not modify the fields as well. So, make the ci_type field and the pointers initialized with ci_type as const. Signed-off-by: B

Re: [PATCH] of: Devices with pci_epf_bus_type require DMA configuration

On Wed, Oct 11, 2017 at 3:00 AM, Kishon Vijay Abraham I wrote: > pci-epc-core.c invokes of_dma_configure in order to configure > the coherent_dma_mask/dma_mask of endpoint function device. This is > required for dma_alloc_coherent to succeed in pci function driver > (pci-epf-test.c). However after

[PATCH 2/7] ARM: dts: imx53-tx53: remove the regulators bus

It is not recommended to place the regulator nodes inside 'simple-bus', so adjust them accordingly. The motivation for rearranging this is to make it easier to add new regulator nodes in the future. Signed-off-by: Lothar Waßmann --- arch/arm/boot/dts/imx53-tx53-x03x.dts | 38 +++ ar

Re: [PATCH V8 00/14] mmc: Add Command Queue support

On 11/10/17 15:13, Ulf Hansson wrote: > On 10 October 2017 at 15:31, Adrian Hunter wrote: >> On 10/10/17 16:08, Ulf Hansson wrote: >>> [...] >>> >>> >>> I have also run some test on my ux500 board and enabling the blkmq >>> path via the new MMC Kconfig option. My idea was to run some i

Re: [PATCH v2] HID: usbhid: fix out-of-bounds bug

On Thu, 28 Sep 2017, Jaejoong Kim wrote: > The hid descriptor identifies the length and type of subordinate > descriptors for a device. If the received hid descriptor is smaller than > the size of the struct hid_descriptor, it is possible to cause > out-of-bounds. > > In addition, if bNumDescript

Re: [PATCH] scsi: use set_host_byte instead of open-coding it

On 10/10/2017 05:29 PM, Johannes Thumshirn wrote: Call set_host_byte() instead of open-coding it. Converted using this simple Coccinelle spatch @@ local idexpression struct scsi_cmnd *c; expression E1; @@ - c->result = E1 << 16; + set_host_byte(c, E1); Maybe I misunderstand, but doesn't se

Re: [PATCH 2/4] perf/ftrace: Fix function trace events

On Wed, 11 Oct 2017 13:59:54 +0200 Jiri Olsa wrote: > > @@ -330,7 +354,7 @@ perf_ftrace_function_call(unsigned long > > entry->ip = ip; > > entry->parent_ip = parent_ip; > > perf_trace_buf_submit(entry, ENTRY_SIZE, rctx, TRACE_FN, > > - 1, ®s, head, NULL); > >

Re: [PATCH] arm64: remove unneeded copy to init_utsname()->machine

Hi arm64 maintainers, Could you check this please? 2017-09-14 20:40 GMT+09:00 Masahiro Yamada : > As you see in init/version.c, init_uts_ns.name.machine is initially > set to UTS_MACHINE. There is no point to copy the same string. > > I dug the git history to figure out why this line is here.

[PATCH v3 2/2] arm64: docs: describe ELF hwcaps

From: Mark Rutland We don't document our ELF hwcaps, leaving developers to interpret them according to hearsay, guesswork, or (in exceptional cases) inspection of the current kernel code. This is less than optimal, and it would be far better if we had some definitive description of each of the E

[PATCH v3 1/2] arm64: Expose support for optional ARMv8-A features

ARMv8-A adds a few optional features for ARMv8.2 and ARMv8.3. Expose them to the userspace via HWCAPs and mrs emulation. SHA2-512 - Instruction support for SHA512 Hash algorithm (e.g SHA512H, SHA512H2, SHA512U0, SHA512SU1) SHA3 - SHA3 crypto instructions (EOR3, RAX1, XAR, BCAX).

Re: [PATCH] x86/boot: remove bogus #include

Hi x86 maintainers, 2017-09-21 0:27 GMT+09:00 Masahiro Yamada : > The defines UTS_RELEASE, but I do not > see any reference to it in arch/x86/boot/header.S . > > Signed-off-by: Masahiro Yamada > --- > > arch/x86/boot/header.S | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/x86/boo

Re: [PATCH RFC tip/core/rcu 12/15] lib/assoc_array: Remove smp_read_barrier_depends()

On Wed, Oct 11, 2017 at 01:19:59PM +0100, David Howells wrote: > Paul E. McKenney wrote: > > > - node = result.terminal_node.node; > > - smp_read_barrier_depends(); > > + node = READ_ONCE(result.terminal_node.node); /* Address dependency. */ > > The main problem I have with this method of

[PATCH] powerpc/perf: Add ___GFP_NOWARN flag to alloc_pages_node()

Stack trace output during a stress test: [4.310049] Freeing initrd memory: 22592K [4.310646] rtas_flash: no firmware flash support [4.313341] cpuhp/64: page allocation failure: order:0, mode:0x14480c0(GFP_KERNEL|__GFP_ZERO|__GFP_THISNODE), nodemask=(null) [4.313465] cpuhp/64 cpuse

Re: [PATCH v3 3/8] PM / devfreq: Show the available min/max frequency through sysfs node

On Wed, Oct 11, 2017 at 8:15 PM, MyungJoo Ham wrote: >> The existing {min|max}_freq sysfs nodes don't consider whether min/max_freq >> are available or not. Those sysfs nodes show just the stored value >> in the struct devfreq. >> >> The devfreq uses the OPP interface and then dev_pm_opp_{disable|

Re: [PATCH 1/4] perf/ftrace: Revert ("perf/ftrace: Fix double traces of perf on ftrace:function")

On Wed, 11 Oct 2017 09:45:29 +0200 Peter Zijlstra wrote: > Revert commit: > > 75e8387685f6 ("perf/ftrace: Fix double traces of perf on ftrace:function") > > The reason I instantly stumbled on that patch is that it only addresses the > ftrace situation and doesn't mention the other _5_ places

Re: [PATCH RFC tip/core/rcu 0/15] Remove to-be-unneeded smp_read_barrier_depends()

On Wed, Oct 11, 2017 at 01:21:03PM +0100, David Howells wrote: > Paul E. McKenney wrote: > > > Will Deacon has proposed adding smp_read_barrier_depends() to READ_ONCE(), > > which would mean that quite a few instances of smp_read_barrier_depends() > > would become redundant. > > It's not clear f

Re: [PATCH 4.9 000/105] 4.9.55-stable review

On Tue, Oct 10, 2017 at 06:58:40PM -0600, Shuah Khan wrote: > On 10/10/2017 01:49 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.55 release. > > There are 105 patches in this series, all will be posted as a response > > to this one. If anyone has any iss

Re: [RFC][PATCH] tracing/jump-labels: Add message when a trace event has no instances

On Wed, 11 Oct 2017 09:21:09 +0200 Peter Zijlstra wrote: > On Tue, Oct 10, 2017 at 06:56:30PM -0400, Steven Rostedt wrote: > > > +/* Without jump labels we don't know how many instances, just assume one */ > > +static inline int static_key_instances(struct static_key *key) > > +{ > > + return

Re: [PATCH RFC tip/core/rcu 12/15] lib/assoc_array: Remove smp_read_barrier_depends()

On Wed, Oct 11, 2017 at 01:22:17PM +0100, Will Deacon wrote: > On Wed, Oct 11, 2017 at 01:19:59PM +0100, David Howells wrote: > > Paul E. McKenney wrote: > > > > > - node = result.terminal_node.node; > > > - smp_read_barrier_depends(); > > > + node = READ_ONCE(result.terminal_node.node); /* Addre

RE: [PATCH] rtl8xxxu: mark expected switch fall-throughs

From: Joe Perches > Sent: 11 October 2017 11:21 > On Tue, 2017-10-10 at 14:30 -0500, Gustavo A. R. Silva wrote: > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > > where we are expecting to fall through. > > perhaps use Arnaldo's idea: > > https://lkml.org/lkml/2017/2/9/8

Re: linux-next: Tree for Oct 9th (drivers/dma/stm32-mdma.c)

On Tue, Oct 10, 2017 at 09:27:18AM -0700, Randy Dunlap wrote: > On 10/09/17 14:21, Mark Brown wrote: > > For my birthday I've gone and got myself a linux-next tree: Nice thing you chose to do for the day :D > > > > Changes since 20170929: > > > > on i386: > > drivers/dma/stm32-mdma.o: In func

Re: [PATCH 2/2] ARM: dts: gr-peach: Enable ostm0 and ostm1 timers

On Mon, Oct 9, 2017 at 10:48 AM, Jacopo Mondi wrote: > Enable ostm0 and ostm1 timers to be used as clock source and clockevent > source. The timers provides greater accuracy than the already enabled > mtu2 one. > > With these enabled: > > clocksource: ostm: mask: 0x max_cycles: 0x,

[PATCH v2] stackdepot: ignore junk last entry in case of switch from user mode.

Issue observed on ARM. Whenever there is switch from user mode, we end up with invalid last entry with some user space address as below:- save_stack+0x40/0xec __set_page_owner+0x2c/0x64 __handle_domain_irq+0x9c/0x130 gic_handle_irq+0x40/0x80 __irq_usr+0x4c/0x60 0xb6507818 So in t

Re: [PATCH v2 03/16] iommu: introduce iommu invalidate API function

On 11/10/17 13:15, Joerg Roedel wrote: > On Wed, Oct 11, 2017 at 11:54:52AM +, Liu, Yi L wrote: >> I didn't quite get 'iovm' mean. Can you explain a bit about the idea? > > It's short for IO Virtual Memory, basically a replacement term for 'svm' > that is not ambiguous (afaik) and not specific

<    2   3   4   5   6   7   8   9   10   >