[PATCH 7/7] x86: switch the VIA 32-bit DMA quirk to use the struct device flag

2018-05-25 Thread Christoph Hellwig
Instead of globally disabling > 32bit DMA using the arch_dma_supported hook walk the PCI bus under the actually affected bridge and mark every device with the dma_32bit_limit flag. This also gets rid of the arch_dma_supported hook entirely. Signed-off-by: Christoph Hellwig ---

[PATCH] udmabuf: fix odd_ptr_err.cocci warnings

2018-05-25 Thread Julia Lawall
From: kbuild test robot drivers/dma-buf/udmabuf.c:167:6-12: inconsistent IS_ERR and PTR_ERR on line 168. PTR_ERR should access the value just tested by IS_ERR Semantic patch information: There can be false positives in the patch case, where it is the call to IS_ERR

[PATCH v11 3/4] arm64: Implement page table free interfaces

2018-05-25 Thread Chintan Pandya
Implement pud_free_pmd_page() and pmd_free_pte_page(). Implementation requires, 1) Clearing off the current pud/pmd entry 2) Invalidate TLB which could have previously valid but not stale entry 3) Freeing of the un-used next level page tables Signed-off-by: Chintan Pandya

[PATCH v11 2/4] arm64: tlbflush: Introduce __flush_tlb_kernel_pgtable

2018-05-25 Thread Chintan Pandya
Add an interface to invalidate intermediate page tables from TLB for kernel. Signed-off-by: Chintan Pandya --- arch/arm64/include/asm/tlbflush.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/include/asm/tlbflush.h

[PATCH v11 1/4] ioremap: Update pgtable free interfaces with addr

2018-05-25 Thread Chintan Pandya
From: Chintan Pandya The following kernel panic was observed on ARM64 platform due to a stale TLB entry. 1. ioremap with 4K size, a valid pte page table is set. 2. iounmap it, its pte entry is set to 0. 3. ioremap the same address with 2M size, update its pmd entry

[PATCH v11 4/4] Revert "arm64: Enforce BBM for huge IO/VMAP mappings"

2018-05-25 Thread Chintan Pandya
This commit 15122ee2c515a ("arm64: Enforce BBM for huge IO/VMAP mappings") is a temporary work-around until the issues with CONFIG_HAVE_ARCH_HUGE_VMAP gets fixed. Revert this change as we have fixes for the issue. Signed-off-by: Chintan Pandya --- arch/arm64/mm/mmu.c |

[PATCH v11 0/4] Fix issues with huge mapping in ioremap for ARM64

2018-05-25 Thread Chintan Pandya
This series of patches re-bring huge vmap back for arm64. Patch 1/4 has been taken by Toshi in his series of patches by name "[PATCH v3 0/3] fix free pmd/pte page handlings on x86" to avoid merge conflict with this series. Patch 4/4 may conflict with Laura's patch "[PATCHv2] arm64: Make sure

Re: [PATCH v5 01/10] sched/pelt: Move pelt related code in a dedicated file

2018-05-25 Thread Quentin Perret
Hi Vincent, On Friday 25 May 2018 at 15:12:22 (+0200), Vincent Guittot wrote: > We want to track rt_rq's utilization as a part of the estimation of the > whole rq's utilization. This is necessary because rt tasks can steal > utilization to cfs tasks and make them lighter than they are. > As we

Re: [PATCH 0/3] Provide more fine grained control over multipathing

2018-05-25 Thread Christoph Hellwig
On Fri, May 25, 2018 at 04:22:17PM +0200, Johannes Thumshirn wrote: > But Mike's and Hannes' arguments where reasonable as well, we do not > know if there are any existing setups we might break leading to > support calls, which we have to deal with. Personally I don't believe > there are lot's of

[PATCH v4] usbip: dynamically allocate idev by nports found in sysfs

2018-05-25 Thread Michael Grzeschik
As the amount of available ports varies by the kernels build configuration. To remove the limitation of the fixed 128 ports we allocate the amount of idevs by using the number we get from the kernel. Signed-off-by: Michael Grzeschik --- v1 -> v2: - reworked memory

Re: [PATCH v2 5/5] MAINTAINERS: Add Actions Semi S900 pinctrl entries

2018-05-25 Thread Manivannan Sadhasivam
On Fri, May 25, 2018 at 02:12:06PM +0200, Linus Walleij wrote: > On Fri, May 25, 2018 at 7:01 AM, Manivannan Sadhasivam > wrote: > > > FYI, I have ordered S700 based Cubieboard and will work on adding support > > for > > that first. I still don't have access to

Re: [PATCH V4] mlx4_core: allocate ICM memory in page size chunks

2018-05-25 Thread David Miller
From: Qing Huang Date: Wed, 23 May 2018 16:22:46 -0700 > When a system is under memory presure (high usage with fragments), > the original 256KB ICM chunk allocations will likely trigger kernel > memory management to enter slow path doing memory compact/migration > ops in

Re: [PATCH 0/3] Provide more fine grained control over multipathing

2018-05-25 Thread Johannes Thumshirn
On Fri, May 25, 2018 at 03:05:35PM +0200, Christoph Hellwig wrote: > On Fri, May 25, 2018 at 02:53:19PM +0200, Johannes Thumshirn wrote: > > Hi, > > > > This patch series aims to provide a more fine grained control over > > nvme's native multipathing, by allowing it to be switched on and off > >

Re: [PATCH] ath10k: transmit queued frames after waking queues

2018-05-25 Thread Niklas Cassel
On Fri, May 25, 2018 at 08:50:23AM -0400, Bob Copeland wrote: > On Fri, May 25, 2018 at 02:36:56PM +0200, Niklas Cassel wrote: > > A spin lock does have the advantage of ordering: memory operations issued > > before the spin_unlock_bh() will be completed before the spin_unlock_bh() > > operation

Re: [PATCH v2 1/2] rcu: Update documentation of rcu_read_unlock()

2018-05-25 Thread Paul E. McKenney
On Fri, May 25, 2018 at 11:05:06AM +0200, Anna-Maria Gleixner wrote: > Since commit b4abf91047cf ("rtmutex: Make wait_lock irq safe") the > explanation in rcu_read_unlock() documentation about irq unsafe rtmutex > wait_lock is no longer valid. > > Remove it to prevent kernel developers reading

Re: [PATCH] ARM: dts: imx51-zii-rdu1: Make sure SD1_WP is low

2018-05-25 Thread Lucas Stach
Am Donnerstag, den 24.05.2018, 20:01 -0700 schrieb Andrey Smirnov: > Make sure that MX51_PAD_GPIO1_1 does not remain configure as > ALT0/SD1_WP (it is out of reset). This is needed because of external > pull-up resistor attached to that pad that, when left unchanged, will > drive SD1_WP high

KASAN: use-after-free Write in tls_push_record

2018-05-25 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:13405468f49d bpfilter: don't pass O_CREAT when opening con.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=109ad82f80 kernel config: https://syzkaller.appspot.com/x/.config?x=8be0182d69f8d422

Re: [PATCH 4.4 00/92] 4.4.133-stable review

2018-05-25 Thread Greg Kroah-Hartman
On Thu, May 24, 2018 at 09:47:42PM +0200, Greg Kroah-Hartman wrote: > On Thu, May 24, 2018 at 10:32:08AM -0700, Guenter Roeck wrote: > > On Thu, May 24, 2018 at 11:37:37AM +0200, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.4.133 release. > > > There are

Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files

2018-05-25 Thread Guenter Roeck
On Fri, May 25, 2018 at 6:42 AM Shreyas NC wrote: > > > > +struct skl_dfw_v4_pipe { > > > > + u8 pipe_id; > > > > + u8 pipe_priority; > > > > + u16 conn_type:4; > > > > + u16 rsvd:4; > > > > + u16 memory_pages:8; > > > > +} __packed; > > > > + > > > >

[PATCH v3] Add udmabuf misc device

2018-05-25 Thread Gerd Hoffmann
A driver to let userspace turn memfd regions into dma-bufs. Use case: Allows qemu create dmabufs for the vga framebuffer or virtio-gpu ressources. Then they can be passed around to display those guest things on the host. To spice client for classic full framebuffer display, and hopefully some

Re: [PATCH v3 6/6] tty/serial: atmel: changed the driver to work under at91-usart mfd

2018-05-25 Thread Radu Pirea
On 05/25/2018 04:35 PM, Richard Genoud wrote: On 25/05/2018 14:17, Radu Pirea wrote: On 05/15/2018 04:14 PM, Richard Genoud wrote: On 15/05/2018 14:47, Radu Pirea wrote: On Mon, 2018-05-14 at 12:57 +0200, Richard Genoud wrote: After your patch, the DMA is not selected anymore:

Re: [PATCH 0/3] Provide more fine grained control over multipathing

2018-05-25 Thread Christoph Hellwig
On Fri, May 25, 2018 at 09:58:13AM -0400, Mike Snitzer wrote: > We all basically knew this would be your position. But at this year's > LSF we pretty quickly reached consensus that we do in fact need this. > Except for yourself, Sagi and afaik Martin George: all on the cc were in > attendance and

Re: [PATCH 04/12] powerpc: Implement hw_breakpoint_arch_parse()

2018-05-25 Thread Frederic Weisbecker
On Thu, May 24, 2018 at 12:01:52PM +1000, Michael Ellerman wrote: > Frederic Weisbecker writes: > > > diff --git a/arch/powerpc/kernel/hw_breakpoint.c > > b/arch/powerpc/kernel/hw_breakpoint.c > > index 348cac9..fba6527 100644 > > --- a/arch/powerpc/kernel/hw_breakpoint.c >

Re: [PATCH] userfaultfd: prevent non-cooperative events vs mcopy_atomic races

2018-05-25 Thread Pavel Emelyanov
>> But doesn't it race even with regular PF handling, not only the fork? How >> do we handle this race? > > With the regular #PF handing, the faulting thread patiently waits until > page fault is resolved. With fork(), mremap() etc the thread that caused > the event resumes once the uffd message

Re: [PATCH] Bluetooth: Add a new Realtek 8723DE ID 0bda:b009

2018-05-25 Thread Jian-Hong Pan
Hi Daniel, 2018-05-25 21:25 GMT+08:00 Daniel Drake : > Hi Jian-Hong, > > On Fri, May 25, 2018 at 3:54 AM, Jian-Hong Pan wrote: >> >> Without this patch we cannot turn on the Bluethooth adapter on HP >> 14-bs007la. > > Please correct me if I'm wrong,

Re: [PATCH v2 10/10] vfio: ccw: Let user wait when busy on IO

2018-05-25 Thread Heiko Carstens
On Fri, May 25, 2018 at 12:21:18PM +0200, Pierre Morel wrote: > In the current implementation, we do not want to start a new SSCH > command before the last one ends. > > Currently the user needs to poll on the -EBUSY error to > wait before sending a new request. > > Let's be friendly with global

[PATCH] PCI: Try to clean up resources via remove if shutdown doesn't exist

2018-05-25 Thread Sinan Kaya
It is up to a driver to implement shutdown() callback. If shutdown() callback is not implemented, PCI device can have pending interrupt and even do DMA transactions while the system is going down. If kexec is in use, this can damage the newly booting kexec kernel or even prevent it from booting

Re: [RFT v2 1/4] perf cs-etm: Generate sample for missed packets

2018-05-25 Thread Robert Walker
Hi Leo, Following the discussions from your reply to this with a simplified patch, this version of the patch works better as you also need to emit a branch sample when handling a CS_ETM_TRACE_ON packet to indicate the end of a block of trace. This patch does not break the output from perf

Re: OMAP serial runtime PM and autosuspend (was: Re: [PATCH 4/7] dt-bindings: gnss: add u-blox binding))

2018-05-25 Thread Johan Hovold
On Thu, May 24, 2018 at 06:32:37AM -0700, Tony Lindgren wrote: > * Johan Hovold [180524 09:20]: > > On Mon, May 21, 2018 at 08:48:32AM -0700, Tony Lindgren wrote: > > > Well if you have some better mechanism in mind let's try it out. Short of > > > sprinkling

Re: Turris Omnia firmware possibilities [Was: Re: led: hw-trigger, global brightness and multi-colored leds]

2018-05-25 Thread Tomas Hlavacek
On Fri, May 25, 2018 at 8:08 AM, Uwe Kleine-K├Ânig wrote: > Hello Tomas, > > On 05/25/2018 12:08 AM, Tomas Hlavacek wrote: >> But I also have good news: The FW of the MCU is also OSS (see the repo >> in the link (1)). There is a method for flashing the MCU over I2C from >>

Re: [PATCH 0/3] Provide more fine grained control over multipathing

2018-05-25 Thread Mike Snitzer
On Fri, May 25 2018 at 9:05am -0400, Christoph Hellwig wrote: > On Fri, May 25, 2018 at 02:53:19PM +0200, Johannes Thumshirn wrote: > > Hi, > > > > This patch series aims to provide a more fine grained control over > > nvme's native multipathing, by allowing it to be switched on

Re: [PATCH 01/12] perf/breakpoint: Split attribute parse and commit

2018-05-25 Thread Frederic Weisbecker
On Thu, May 24, 2018 at 11:56:01AM +1000, Michael Ellerman wrote: > Frederic Weisbecker writes: > > > diff --git a/kernel/events/hw_breakpoint.c b/kernel/events/hw_breakpoint.c > > index 6e28d28..51320c2 100644 > > --- a/kernel/events/hw_breakpoint.c > > +++

Re: [RFT v2 1/4] perf cs-etm: Generate sample for missed packets

2018-05-25 Thread Robert Walker
Hi Leo, On 23/05/18 14:22, Leo Yan wrote: Hi Rob, On Wed, May 23, 2018 at 12:21:18PM +0100, Robert Walker wrote: Hi Leo, On 22/05/18 10:52, Leo Yan wrote: On Tue, May 22, 2018 at 04:39:20PM +0800, Leo Yan wrote: [...] Rather than the patch I posted in my previous email, I think below new

Re: [PATCH] PCI: hv: Do not wait forever on a device that has disappeared

2018-05-25 Thread Lorenzo Pieralisi
On Wed, May 23, 2018 at 09:12:01PM +, Dexuan Cui wrote: > > Before the guest finishes the device initialization, the device can be > removed anytime by the host, and after that the host won't respond to > the guest's request, so the guest should be prepared to handle this > case. > >

[PATCH 1/2] regmap: add missing prototype for devm_init_slimbus

2018-05-25 Thread Srinivas Kandagatla
For some reason the devm variant of slimbus init is not added into the header eventhough this __devm_regmap_init_slimbus() is an exported function. This patch adds this. This also fixes below warning in regmap-slimbus.c regmap-slimbus.c:65:15: warning: symbol '__devm_regmap_init_slimbus' was not

[PATCH 2/2] regmap: slimbus: allow register offsets up to 16 bits

2018-05-25 Thread Srinivas Kandagatla
As per SLIMBus specs Value Elements and Information Elements address map ranges from 0x000 - 0xFFF. So allow register addresses up to 16 bits Fixes: 7d6f7fb053ad ("regmap: add SLIMbus support") Signed-off-by: Srinivas Kandagatla ---

[PATCH 0/2] regmap: slimbus: minor fixes.

2018-05-25 Thread Srinivas Kandagatla
Here are 2 minor fixes for regmap slimbus. Thanks, srini Srinivas Kandagatla (2): regmap: add missing prototype for devm_init_slimbus regmap: slimbus: allow register offsets up to 16 bits drivers/base/regmap/regmap-slimbus.c | 2 +- include/linux/regmap.h | 18

Re: KASAN: use-after-free Read in ccid2_hc_tx_packet_recv

2018-05-25 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:b50694381cfc Merge branch 'stable/for-linus-4.17' of git:/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=17151cb780 kernel config:

Re: [PATCH 1/3] nvme: provide a way to disable nvme mpath per subsystem

2018-05-25 Thread Mike Snitzer
On Fri, May 25 2018 at 8:53am -0400, Johannes Thumshirn wrote: > Provide a way to disable NVMe native multipathing on a per-subsystem > basis to enable a user to use dm-mpath and nvme native multipathing on > the same host for different nvme devices. > > Signed-off-by:

Re: [PATCH v2] bpf, arm32: Correct check_imm24

2018-05-25 Thread Daniel Borkmann
On 05/11/2018 05:06 AM, Wang YanQing wrote: > imm24 is signed, so the right range is: > [-(1<<(24 - 1)), (1<<(24 - 1)) - 1] > > Note:this patch also fix a typo. > > Signed-off-by: Wang YanQing Through which tree will this fix be routed? (And the cleanup in "[PATCH v2] bpf,

Re: [PATCH v4 00/26] arm64: provide pseudo NMI with GICv3

2018-05-25 Thread Julien Thierry
On 25/05/18 11:40, Julien Thierry wrote: On 25/05/18 11:16, Daniel Thompson wrote: On Fri, May 25, 2018 at 10:49:06AM +0100, Julien Thierry wrote: This series is a continuation of the work started by Daniel [1]. The goal is to use GICv3 interrupt priorities to simulate an NMI. To achieve

Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files

2018-05-25 Thread Shreyas NC
> > > +struct skl_dfw_v4_pipe { > > > + u8 pipe_id; > > > + u8 pipe_priority; > > > + u16 conn_type:4; > > > + u16 rsvd:4; > > > + u16 memory_pages:8; > > > +} __packed; > > > + > > > +struct skl_dfw_v4_module { > > > + char uuid[SKL_UUID_STR_SZ]; > > > + Any reason to not

Re: [PATCH v3 6/6] tty/serial: atmel: changed the driver to work under at91-usart mfd

2018-05-25 Thread Richard Genoud
On 25/05/2018 14:17, Radu Pirea wrote: > > > On 05/15/2018 04:14 PM, Richard Genoud wrote: >> On 15/05/2018 14:47, Radu Pirea wrote: >>> On Mon, 2018-05-14 at 12:57 +0200, Richard Genoud wrote: After your patch, the DMA is not selected anymore: atmel_usart_serial

Re: [alsa-devel] [PATCH v2 1/3] ASoC: topology: Improve backwards compatibility with v4 topology files

2018-05-25 Thread Shreyas NC
Adding Vinod to help review as well.. > Commit dc31e741db49 ("ASoC: topology: ABI - Add the types for BE > DAI") introduced sound topology files version 5. Initially, this > change made the topology code incompatible with v4 topology files. > Backwards compatibility with v4 configuration files was

Re: [PATCH] powerpc/64s: Clear PCR on boot

2018-05-25 Thread Guenter Roeck
On Fri, May 18, 2018 at 11:37:42AM +1000, Michael Neuling wrote: > Clear the PCR (Processor Compatibility Register) on boot to ensure we > are not running in a compatibility mode. > > We've seen this cause problems when a crash (and kdump) occurs while > running compat mode guests. The kdump

Re: [PATCH V2] PCI/portdrv: do not disable device on reboot/shutdown

2018-05-25 Thread Sinan Kaya
On 5/24/2018 2:35 PM, Bjorn Helgaas wrote: > That sounds like a reasonable idea, and it is definitely another can > of worms. I looked briefly at some of the .shutdown() cases: should we throw it into 4.18 and see what happens? -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an

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

2018-05-25 Thread Kalle Valo
Sergei Shtylyov writes: > On 5/25/2018 2:13 AM, Gustavo A. R. Silva wrote: > >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases >> where we are expecting to fall through. >> >> Signed-off-by: Gustavo A. R. Silva >>

Re: [PATCH] Bluetooth: Add a new Realtek 8723DE ID 0bda:b009

2018-05-25 Thread Daniel Drake
Hi Jian-Hong, On Fri, May 25, 2018 at 3:54 AM, Jian-Hong Pan wrote: > > Without this patch we cannot turn on the Bluethooth adapter on HP > 14-bs007la. Please correct me if I'm wrong, but it looks like we are still waiting for the testing of this patch from our

Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files

2018-05-25 Thread Guenter Roeck
On Fri, May 25, 2018 at 2:04 AM Lin, Mengdong wrote: > > -Original Message- > > From: alsa-devel-boun...@alsa-project.org [mailto: alsa-devel-bounces@alsa- > > project.org] On Behalf Of Mark Brown > > Sent: Thursday, May 24, 2018 11:12 PM > > On Thu, May 24, 2018

[PATCH v5 04/10] sched/dl: add dl_rq utilization tracking

2018-05-25 Thread Vincent Guittot
Similarly to what happens with rt tasks, cfs tasks can be preempted by dl tasks and the cfs's utilization might no longer describes the real utilization level. Current dl bandwidth reflects the requirements to meet deadline when tasks are enqueued but not the current utilization of the dl sched

[PATCH v5 05/10] cpufreq/schedutil: get max utilization

2018-05-25 Thread Vincent Guittot
Now that we have both the dl class bandwidth requirement and the dl class utilization, we can use the max of the 2 values when agregating the utilization of the CPU. Signed-off-by: Vincent Guittot --- kernel/sched/sched.h | 6 +- 1 file changed, 5 insertions(+),

[PATCH v5 01/10] sched/pelt: Move pelt related code in a dedicated file

2018-05-25 Thread Vincent Guittot
We want to track rt_rq's utilization as a part of the estimation of the whole rq's utilization. This is necessary because rt tasks can steal utilization to cfs tasks and make them lighter than they are. As we want to use the same load tracking mecanism for both and prevent useless dependency

[PATCH v5 07/10] sched/irq: add irq utilization tracking

2018-05-25 Thread Vincent Guittot
interrupt and steal time are the only remaining activities tracked by rt_avg. Like for sched classes, we can use PELT to track their average utilization of the CPU. But unlike sched class, we don't track when entering/leaving interrupt; Instead, we take into account the time spent under interrupt

[PATCH v5 08/10] cpufreq/schedutil: take into account interrupt

2018-05-25 Thread Vincent Guittot
The time spent under interrupt can be significant but it is not reflected in the utilization of CPU when deciding to choose an OPP. Now that we have access to this metric, schedutil can take it into account when selecting the OPP for a CPU. The CPU utilization is : irq util_avg + (1 - irq

[PATCH v5 02/10] sched/rt: add rt_rq utilization tracking

2018-05-25 Thread Vincent Guittot
schedutil governor relies on cfs_rq's util_avg to choose the OPP when cfs tasks are running. When the CPU is overloaded by cfs and rt tasks, cfs tasks are preempted by rt tasks and in this case util_avg reflects the remaining capacity but not what cfs want to use. In such case, schedutil can

[PATCH v5 06/10] sched: remove rt and dl from sched_avg

2018-05-25 Thread Vincent Guittot
the utilization level of the CPU by rt and dl tasks is now tracked with PELT so we can use these metrics and remove them from the rt_avg which will track only interrupt and stolen virtual time. Signed-off-by: Vincent Guittot --- kernel/sched/deadline.c | 2 --

[PATCH v5 03/10] cpufreq/schedutil: add rt utilization tracking

2018-05-25 Thread Vincent Guittot
Add both cfs and rt utilization when selecting an OPP for cfs tasks as rt can preempt and steal cfs's running time. Signed-off-by: Vincent Guittot --- kernel/sched/cpufreq_schedutil.c | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git

[PATCH v5 09/10] sched: remove rt_avg code

2018-05-25 Thread Vincent Guittot
rt_avg is no more used anywhere so we can remove all related code Signed-off-by: Vincent Guittot --- kernel/sched/core.c | 26 -- kernel/sched/sched.h | 17 - 2 files changed, 43 deletions(-) diff --git a/kernel/sched/core.c

[PATCH v5 10/10] proc/sched: remove unused sched_time_avg_ms

2018-05-25 Thread Vincent Guittot
/proc/sys/kernel/sched_time_avg_ms entry is not used anywhere. Remove it Signed-off-by: Vincent Guittot --- include/linux/sched/sysctl.h | 1 - kernel/sched/core.c | 8 kernel/sched/sched.h | 1 - kernel/sysctl.c | 8 4

[PATCH v5 00/10] track CPU utilization

2018-05-25 Thread Vincent Guittot
This patchset initially tracked only the utilization of RT rq. During OSPM summit, it has been discussed the opportunity to extend it in order to get an estimate of the utilization of the CPU. - Patches 1-3 correspond to the content of patchset v4 and add utilization tracking for rt_rq. When

[PATCH] mm, page_alloc: do not break __GFP_THISNODE by zonelist reset

2018-05-25 Thread Vlastimil Babka
In __alloc_pages_slowpath() we reset zonelist and preferred_zoneref for allocations that can ignore memory policies. The zonelist is obtained from current CPU's node. This is a problem for __GFP_THISNODE allocations that want to allocate on a different node, e.g. because the allocating thread has

Re: [PATCH 0/3] Provide more fine grained control over multipathing

2018-05-25 Thread Christoph Hellwig
On Fri, May 25, 2018 at 02:53:19PM +0200, Johannes Thumshirn wrote: > Hi, > > This patch series aims to provide a more fine grained control over > nvme's native multipathing, by allowing it to be switched on and off > on a per-subsystem basis instead of a big global switch. No. The only reason

Re: [PATCH v6 3/9] docs: Add Generic Counter interface documentation

2018-05-25 Thread William Breathitt Gray
On Fri, May 25, 2018 at 11:26:11AM +0200, Fabrice Gasnier wrote: >On 05/22/2018 07:08 PM, Jonathan Cameron wrote: > +* Quadrature x2 Rising: > + Rising edges on either quadrature pair signals updates the respective > + count. Quadrature encoding determines the direction. This

[PATCH 2/3] nvme multipath: added SUBSYS_ATTR_RW

2018-05-25 Thread Johannes Thumshirn
From: Mike Snitzer Prep for adding dev_attr in addition to subsys_attr for 'mpath_personality'. Signed-off-by: Mike Snitzer --- drivers/nvme/host/core.c | 34 ++ 1 file changed, 18 insertions(+), 16 deletions(-) diff

[RFC PATCH 2/3] USB: serial: enable serdev support

2018-05-25 Thread Johan Hovold
Enable serdev support by using the serdev opt-in tty-port registration helpers. FIXME: serdev core always allocates and registers a serdev controller during port registration only to immediately roll back in the common case when there is no serdev slave defined in firmware FIXME: serdev does not

[PATCH 3/3] nvme multipath: add dev_attr_mpath_personality

2018-05-25 Thread Johannes Thumshirn
From: Mike Snitzer Allows the ability to consistently access 'mpath_personality' regardless of which mode we're in (native vs other), using: /sys/block/nvmeXn1/device/mpath_personality Signed-off-by: Mike Snitzer --- drivers/nvme/host/core.c | 57

[PATCH 1/3] nvme: provide a way to disable nvme mpath per subsystem

2018-05-25 Thread Johannes Thumshirn
Provide a way to disable NVMe native multipathing on a per-subsystem basis to enable a user to use dm-mpath and nvme native multipathing on the same host for different nvme devices. Signed-off-by: Johannes Thumshirn --- drivers/nvme/host/core.c | 63

[PATCH 0/3] Provide more fine grained control over multipathing

2018-05-25 Thread Johannes Thumshirn
Hi, This patch series aims to provide a more fine grained control over nvme's native multipathing, by allowing it to be switched on and off on a per-subsystem basis instead of a big global switch. The prime use-case is for mixed scenarios where user might want to use nvme's native multipathing

[RFC PATCH 0/3] USB: serial: add device tree (and serdev) support

2018-05-25 Thread Johan Hovold
These are some patches I've been using to test out using serdev with USB serial. Adding device-tree support to USB serial is really a separate matter and could be merged before the remaining issues related to hotplug are addressed for serdev. Note that this has been a low-intensity on-going

[RFC PATCH 3/3] dbg: ARM: dts: boneblack: add USB topology and serdev nodes

2018-05-25 Thread Johan Hovold
Add a hub device and two USB devices, of which one has a combined node. Note that we need to represent the serial ports as well -- consider devices with multiple ports per interface; which one should serdev use? Sibling devices can also be described this way (e.g. gpio@0), and would need to use

[RFC PATCH 1/3] USB: serial: add device-tree support

2018-05-25 Thread Johan Hovold
Lookup and associate serial-port device-tree nodes given a parent USB-interface node during probe. Note that a serial-port node must be named "serial" and have a "reg" property so that ports on multi-port interfaces can be distinguished. _interface { #address-cells = <1>;

Re: [PATCH v8 4/6] cpuset: Make generate_sched_domains() recognize isolated_cpus

2018-05-25 Thread Juri Lelli
On 25/05/18 11:31, Patrick Bellasi wrote: [...] > Right, so the problem seems to be that we "need" to call > arch_update_cpu_topology() and we do that by calling > partition_sched_domains() which was initially introduced by: > >029190c515f1 ("cpuset sched_load_balance flag") > > back in

Re: [PATCH] arm64: dts: qcom: msm8996: Use UFS_GDSC for UFS

2018-05-25 Thread Vivek Gautam
Hi Bjorn, On Fri, May 25, 2018 at 4:01 AM, Bjorn Andersson wrote: > The UFS host controller occationally (20%) fails to enable > gcc_ufs_axi_clk because the UFS GDSC is not enabled. In most cases it's > enabled through the UFS phy driver, but to make sure it's enabled

Re: [GIT PULL] isolation: 1Hz residual tick offloading v4

2018-05-25 Thread Luiz Capitulino
On Fri, 25 May 2018 04:56:25 +0200 Frederic Weisbecker wrote: > On Tue, May 22, 2018 at 10:10:19PM +0300, Yauheni Kaliuta wrote: > > Hi, Frederic! > > > > > On Mon, 29 Jan 2018 02:10:26 +0100, Frederic Weisbecker wrote: > > > On Wed, Jan 24, 2018 at 10:46:08AM

[PATCH 1/6 v1 resend] fs: use << for MS_* flags

2018-05-25 Thread Christian Brauner
The definitions for MS_* flags are currently a mixture between hex values and bit-shifts. All higher values are already initialized with bit-shifts for MS_* constants starting with (1<<16). This patch switches the definitions for MS_* constants over to uniformly use bit-shifts. Note that the BIT()

[PATCH 4/6 v1 resend] statfs: add ST_SHARED

2018-05-25 Thread Christian Brauner
Currently userspace can only determine whether a mountpoint is shared by parsing /proc//mountinfo. It would be convenient to simply retrieve this property with a statvfs() call. This let's userspace avoid costly parsing, supports cases where /proc is not mounted, and supports usecases where file

[PATCH 3/6 v1 resend] statfs: add ST_UNBINDABLE

2018-05-25 Thread Christian Brauner
Currently userspace can only determine whether a mountpoint is unbindable by parsing /proc//mountinfo. It would be convenient to simply retrieve this property with a statvfs() call. This let's userspace avoid costly parsing, supports cases where /proc is not mounted, and supports usecases where

[PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

2018-05-25 Thread Benjamin Tissoires
When we receive a RMI4 report, we should not unconditionally send an input_sync event. Instead, we should let the rmi4 transport layer do it for us. This fixes a situation where we might receive X in a report and the rest in a subsequent one. And this messes up user space. Link:

[PATCH 5/6 v1 resend] statfs: add ST_SLAVE

2018-05-25 Thread Christian Brauner
Currently userspace can only determine whether a mountpoint is slave by parsing /proc//mountinfo. It would be convenient to simply retrieve this property with a statvfs() call. This let's userspace avoid costly parsing, supports cases where /proc is not mounted, and supports usecases where file

Re: [PATCH] ath10k: transmit queued frames after waking queues

2018-05-25 Thread Bob Copeland
On Fri, May 25, 2018 at 02:36:56PM +0200, Niklas Cassel wrote: > A spin lock does have the advantage of ordering: memory operations issued > before the spin_unlock_bh() will be completed before the spin_unlock_bh() > operation has completed. > > However, ath10k_htt_tx_dec_pending() was called

[PATCH 2/6 v1 resend] statfs: use << to align with fs header

2018-05-25 Thread Christian Brauner
After switching to using bit-shifts to define MS_* flags switch over ST_* flags too. ST_* and MS_* flags generally have the exact same value. Initializing them identically let's userspace easily detect when flags indicate the same property but use a different value in doing so. Signed-off-by:

[PATCH 6/6 v1 resend] statfs: add ST_PRIVATE

2018-05-25 Thread Christian Brauner
Currently userspace can only determine whether a mountpoint is private by parsing /proc//mountinfo. It would be convenient to simply retrieve this property with a statvfs() call. This let's userspace avoid costly parsing, supports cases where /proc is not mounted, and supports usecases where file

[PATCH 0/6 v1 resend] statfs: handle mount propagation

2018-05-25 Thread Christian Brauner
From: Christian Brauner Hey, This is v1 of this patchset. All changes from v0 to v1 are non-functional. Specifically, the commit messages and justification have been extended as requested by Linus and Al. This little series does the following: - unify the

Re: [PATCH] mmc: sdhci-*: Don't emit error msg if sdhci_add_host() fails

2018-05-25 Thread Patrice CHOTARD
Hi Jisheng On 05/25/2018 09:15 AM, Jisheng Zhang wrote: > I noticed below error msg with sdhci-pxav3 on some berlin platforms: > > [.] sdhci-pxav3 f7ab.sdhci failed to add host > > It is due to getting related vmmc or vqmmc regulator returns > -EPROBE_DEFER. It doesn't matter at all but

[PATCH v14 1/2] cpufreq: Add Kryo CPU scaling driver

2018-05-25 Thread Ilia Lin
In Certain QCOM SoCs like apq8096 and msm8996 that have KRYO processors, the CPU frequency subset and voltage value of each OPP varies based on the silicon variant in use. Qualcomm Process Voltage Scaling Tables defines the voltage and frequency value based on the msm-id in SMEM and speedbin blown

[PATCH v14 2/2] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu

2018-05-25 Thread Ilia Lin
The qcom-cpufreq-kryo driver reads the msm-id and efuse value from the SoC to provide the OPP framework with required information. This is used to determine the voltage and frequency value for each OPP of operating-points-v2 table when it is parsed by the OPP framework. This change adds

[PATCH v14 0/2] Kryo CPU scaling driver

2018-05-25 Thread Ilia Lin
[v14] * Addressed comment from Sudeep about DT compatible * Added MAINTAINERS entry [v13] * Addressed comment from Sudeep about DT compatible check on init [v12] * Addressed comments from Sudeep and Viresh about the single init [v11] * Addressed comment from Russel about device_node

[PATCH RFC 1/2] locking: Implement an algorithm choice for Wound-Wait mutexes

2018-05-25 Thread Thomas Hellstrom
The current Wound-Wait mutex algorithm is actually not Wound-Wait but Wait-Die. Implement also Wound-Wait as a per-ww-class choice. Wound-Wait is, contrary to Wait-Die a preemptive algorithm and is known to generate fewer backoffs in some cases. Testing reveals that this is true if the number of

[PATCH RFC 0/2] locking: Fix ww_mutex algorithm inconsistency.

2018-05-25 Thread Thomas Hellstrom
The algorithm used for linux Wound/Wait mutexes, is actually not Wound/Wait but Wait/Die. See for example http://www.mathcs.emory.edu/~cheung/Courses/554/Syllabus/8-recv+serial/deadlock-compare.html Rather than renaming them across the tree to something like Wait/Die mutexes or Deadlock

[PATCH RFC 2/2] drm: Change deadlock-avoidance algorithm for the modeset locks.

2018-05-25 Thread Thomas Hellstrom
For modeset locks we don't expect a high number of contending transactions so change algorithm from Wait-Die to Wound-Wait. Signed-off-by: Thomas Hellstrom --- drivers/gpu/drm/drm_modeset_lock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] drivers/net/phy/micrel: Fix for PHY KSZ8061 errrata: Potential link-up failure when Ethernet cable is connected slowly

2018-05-25 Thread Alexander Onnasch
Signed-off-by: Alexander Onnasch --- drivers/net/phy/micrel.c | 24 +++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c index 6c45ff6..7d80a00 100644 ---

Re: [PATCH] ath10k: transmit queued frames after waking queues

2018-05-25 Thread Niklas Cassel
On Thu, May 24, 2018 at 11:50:34AM -0400, Bob Copeland wrote: > On Mon, May 21, 2018 at 10:37:01PM +0200, Niklas Cassel wrote: > > On Thu, May 17, 2018 at 03:26:25PM -0700, Adrian Chadd wrote: > > > On Thu, 17 May 2018 at 16:16, Niklas Cassel > > > wrote: > > > > > > >

[PATCH v4 6/7] ARM: dts: at91: sama5d2: add nodes for I2S controllers

2018-05-25 Thread Codrin Ciubotariu
From: Cyrille Pitchen This patch adds DT nodes for I2S0 and I2S1. It also adds an alias for each I2S node. Signed-off-by: Cyrille Pitchen [codrin.ciubota...@microchip.com: added phandle to new mux clock] Signed-off-by: Codrin Ciubotariu

[PATCH v4 5/7] ASoC: atmel-i2s: add driver for the new Atmel I2S controller

2018-05-25 Thread Codrin Ciubotariu
From: Cyrille Pitchen This patch adds support for the Atmel I2S controller embedded into sama5d2x SoCs. Signed-off-by: Cyrille Pitchen Signed-off-by: Codrin Ciubotariu --- Changes in v4: - treated

[PATCH v4 2/7] clk: at91: add I2S clock mux driver

2018-05-25 Thread Codrin Ciubotariu
This driver is a simple muxing driver that controls the I2S's clock input by using syscon/regmap to change the parrent. The available inputs can be Peripheral clock and Generated clock. Signed-off-by: Codrin Ciubotariu --- arch/arm/mach-at91/Kconfig | 4 ++

[PATCH v4 3/7] ARM: dts: at91: sama5d2: add I2S clock muxing nodes

2018-05-25 Thread Codrin Ciubotariu
This patch adds two clock muxes for the two I2S buses present on sama5d2 platforms. Signed-off-by: Codrin Ciubotariu --- arch/arm/boot/dts/sama5d2.dtsi | 18 ++ 1 file changed, 18 insertions(+) diff --git a/arch/arm/boot/dts/sama5d2.dtsi

[PATCH v4 4/7] ASoC: atmel-i2s: dt-bindings: add DT bindings for I2S controller

2018-05-25 Thread Codrin Ciubotariu
From: Cyrille Pitchen This patch adds DT bindings for the new Atmel I2S controller embedded inside sama5d2x SoCs. Signed-off-by: Cyrille Pitchen Signed-off-by: Codrin Ciubotariu --- Changes in v4:

[PATCH v4 7/7] ARM: dts: at91: sama5d2 Xplained: add pin muxing for I2S

2018-05-25 Thread Codrin Ciubotariu
From: Cyrille Pitchen This patch sets the pin muxing for the I2S controllers Signed-off-by: Cyrille Pitchen [codrin.ciubota...@microchip.com: added pin muxing for the second controller] Signed-off-by: Codrin Ciubotariu

[PATCH v4 0/7] ASoC: add driver for Atmel I2S controller

2018-05-25 Thread Codrin Ciubotariu
This is a rework of Cyrille's patches named: [PATCH v3 0/2] ASoC: add driver for Atmel I2S controller https://lkml.org/lkml/2015/9/29/454 This is the version 4 of the series, and addresses the received feedback on the mailing lists. This series applies on top of asoc-next branch of

[PATCH v4 1/7] dt-bindings: clk: at91: add an I2S mux clock

2018-05-25 Thread Codrin Ciubotariu
The I2S mux clock can be used to select the I2S input clock. The available parents are the peripheral and the generated clocks. Signed-off-by: Codrin Ciubotariu --- .../devicetree/bindings/clock/at91-clock.txt | 34 ++ 1 file changed,

<    1   2   3   4   5   6   7   8   9   >