Re: [tip:perf/urgent] perf/x86: Set pmu->module in Intel PMU modules

On Thu, Jan 05, 2017 at 07:07:05AM -0800, tip-bot for David Carrillo-Cisneros wrote: > --- a/arch/x86/events/intel/cstate.c > +++ b/arch/x86/events/intel/cstate.c > @@ -434,6 +434,7 @@ static struct pmu cstate_core_pmu = { > .stop = cstate_pmu_event_stop, > .read =

Re: [PATCHv14 2/3] usb: USB Type-C connector class

On Thu, Jan 05, 2017 at 02:01:18PM +0300, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role swapping, and when the port

[PATCH] pinctrl: core: Fix panic when pinctrl devices with hogs are unregistered

Commit df61b366af26 ('pinctrl: core: Use delayed work for hogs') deferred part of the registration for pinctrl devices if the pinctrl device has hogs. This introduced a window where if the pinctrl device with hogs was sucessfully registered, but then unregistered again (which could be caused by

[PATCH 2/2] ocfs2: fix deadlocks when taking inode lock at vfs entry points

Commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()") results in a deadlock, as the author "Tariq Saeed" realized shortly after the patch was merged. The discussion happened here (https://oss.oracle.com/pipermail/ocfs2-devel/2015-September/011085.html). The reason why taking

Re: [PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current state is too deep

On 1/5/2017 7:43 AM, Rik van Riel wrote: On Thu, 2017-01-05 at 23:29 +0800, Alex Shi wrote: The obsolete commit 71abbbf85 want to introduce a dynamic cstates, but it was removed for long time. Just left the nonsense deeper cstate checking. Since all target_residency and exit_latency are going

Re: [PATCH 15/20] ARM/hw_breakpoint: Convert to hotplug state machine

On Wed, Jan 04, 2017 at 02:32:06PM +, Will Deacon wrote: > On Wed, Jan 04, 2017 at 01:56:44PM +, Mark Rutland wrote: > > On Tue, Jan 03, 2017 at 09:33:36AM +, Mark Rutland wrote: > > > On Mon, Jan 02, 2017 at 09:15:29PM +0100, Linus Walleij wrote: > > > > On Mon, Jan 2, 2017 at 4:00

Re: VT switch broken with docking station DP

On Thu, Jan 05, 2017 at 04:37:27PM +0100, Takashi Iwai wrote: > Hi, > > recently I noticed that VT console doesn't work any longer when I dock > a Dell E7270 laptop with a DP monitor. The bug detail is like this: > > At first, I boot the laptop without dock. I can switch between X and > VT via

Re: [PATCH] KVM: eventfd: fix NULL deref irqbypass consumer

On Thu, 5 Jan 2017 11:24:08 +0100 Paolo Bonzini wrote: > On 05/01/2017 10:05, Wanpeng Li wrote: > > From: Wanpeng Li > > > > Reported syzkaller: > > > > BUG: unable to handle kernel NULL pointer dereference at > > 0008 > > IP:

RE: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

Great to see this coming along so well. Thanks a lot to Jarkko ! I just wanted to point out a few things I deem important at this point: - Number of virtual handles: >From what I see there are currently 14 slots for virtual objects in the RFC >(if I'm mistaking, please correct me). I'd advice to

Re: [RFC PATCH 0/7] locking/rtqspinlock: Realtime queued spinlocks

On 01/05/2017 04:44 AM, Peter Zijlstra wrote: > On Wed, Jan 04, 2017 at 10:25:14AM -0500, Waiman Long wrote: >> On 01/04/2017 07:49 AM, Peter Zijlstra wrote: >>> On Tue, Jan 03, 2017 at 01:00:23PM -0500, Waiman Long wrote: This patchset introduces a new variant of queued spinlocks - the

[PATCH 1/2] Documentation: devicetree: Add document bindings for mtk-cir

From: Sean Wang This patch adds documentation for devicetree bindings for Mediatek IR controller. Signed-off-by: Sean Wang --- .../devicetree/bindings/media/mtk-cir.txt | 23 ++ 1 file changed, 23 insertions(+)

Re: [PATCH 2/7] PM / devfreq: exynos-ppmu: Use the regmap interface to handle the registers

Hello Chanwoo, sorry for the late reply. I was staying with my parents over the Christmas days and didn't have access to the board. Also internet connectivity was a bit troublesome *rolleyes* Chanwoo Choi wrote: > 2016-12-20 22:47 GMT+09:00 Tobias Jakobi : >> Hey

[PATCH 0/2] media: rc: add support for IR receiver on MT7623 SoC

From: Sean Wang This patchset introduces Consumer IR (CIR) support for MT7623 SoC or other similar SoC and implements raw mode for more compatibility with different protocols. The driver simply reports the duration of pulses and spaces to rc core logic to decode. Sean

Re: [PATCH] drm: nouveau: fix build when LEDS_CLASS=m

On 01/05/17 00:01, Daniel Vetter wrote: > On Wed, Jan 04, 2017 at 02:24:51PM -0800, Randy Dunlap wrote: >> On 01/04/17 11:29, Jani Nikula wrote: >>> On Wed, 04 Jan 2017, Daniel Vetter wrote: On Sun, Jan 01, 2017 at 04:20:53PM -0800, Randy Dunlap wrote: > From: Randy

[PATCH 2/2] media: rc: add driver for IR remote receiver on MT7623 SoC

From: Sean Wang This patch adds driver for IR controller on Mediatek MT7623 SoC. Currently testing successfully on NEC and SONY remote controller only but it should work on others (lirc, rc-5 and rc-6). Signed-off-by: Sean Wang ---

Re: [RFC PATCH 0/7] locking/rtqspinlock: Realtime queued spinlocks

On Thu, Jan 05, 2017 at 10:55:55AM -0500, Waiman Long wrote: > What I am saying that we don't need to change spinlock to rtmutex in a > -RT kernel. Instead, we can use rtqspinlock for this purpose. All the > sleeping locks will still be converted to rtmutex. No-no-no.. > Conversion of rtmutex

Re: x86: warning in unwind_get_return_address

On Tue, Dec 27, 2016 at 05:38:59PM +0100, Dmitry Vyukov wrote: > On Thu, Dec 22, 2016 at 6:17 AM, Josh Poimboeuf wrote: > > On Wed, Dec 21, 2016 at 01:46:36PM +0100, Andrey Konovalov wrote: > >> On Wed, Dec 21, 2016 at 12:36 AM, Josh Poimboeuf > >>

Re: [PATCH] drm/i915/dp: Stop enabling limited color ranges for everything

On Thu, 2017-01-05 at 09:52 +0100, Daniel Vetter wrote: > On Thu, Jan 05, 2017 at 10:41:07AM +0200, Jani Nikula wrote: > > No matter what we do here, the question remains what to do with > > Chamelium. Changing the color range is really a workaround for > > Chamelium, not a fix. Using CEA range is

Re: stack unwinder warning.

On Tue, Dec 27, 2016 at 02:00:30PM -0500, Dave Jones wrote: > I'm not sure what to make of this. Josh ? (4.10-rc1) > > WARNING: kernel stack frame pointer at c93e7858 in trinity-c6:29122 > has bad value 82103a80 > unwind stack type:0 next_sp: (null) mask:2 graph_idx:0 >

[PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current state is too deep

The obsolete commit 71abbbf85 want to introduce a dynamic cstates, but it was removed for long time. Just left the nonsense deeper cstate checking. Since all target_residency and exit_latency are going longer in deeper idle state, no needs to waste some cpu cycle on useless seeking.

[PATCH 2/3] cpu: expose pm_qos_resume_latency for each cpu

The cpu-dma PM QoS constraint impacts all the cpus in the system. There is no way to let the user to choose a PM QoS constraint per cpu. The following patch exposes to the userspace a per cpu based sysfs file in order to let the userspace to change the value of the PM QoS latency constraint.

[PATCH 3/3] cpuidle/menu: add per cpu pm_qos_resume_latency consideration

Kernel or user may have special requirement on cpu response time, like if a interrupt is pinned to a cpu, we don't want the cpu goes too deep sleep. This patch can prevent this thing happen by consider per cpu resume_latency setting in cpu sleep state selection in menu governor. The

Re: [PATCH v2,9/9] irqchip/ls-scfg-msi: add MSI affinity support

On 05/01/17 08:10, Minghuan Lian wrote: > For LS1046a and LS1043a v1.1, the MSI controller has 4 MSIRs and 4 > CPUs. A GIC SPI interrupt of MSIR can be associated with a CPU. > When changing MSI interrupt affinity, this MSI will be moved to the > corresponding MSIR and MSI message data will be

Re: [patch] mm, thp: add new background defrag option

On Thu 05-01-17 14:58:47, Vlastimil Babka wrote: [...] > I'm not a fan of either name, so I've tried to implement my own > suggestion. Turns out it was easier than expected, as there's no kernel > boot option for "defer", just for "enabled", so that particular worry > was unfounded. > > And

Re: [PATCH 3/3] mfd: arizona: Use regmap_read_poll_timeout instead of hard coding it

On Thu, 05 Jan 2017, Charles Keepax wrote: > On Thu, Jan 05, 2017 at 08:07:01AM +, Lee Jones wrote: > > On Wed, 04 Jan 2017, Charles Keepax wrote: > > > > > arizona_poll_reg essentially hard-codes regmap_read_poll_timeout, this > > > patch updates the implementation to use

[tip:x86/urgent] x86/cpu: Fix bootup crashes by sanitizing the argument of the 'clearcpuid=' command-line option

Commit-ID: dd853fd216d1485ed3045ff772079cc8689a9a4a Gitweb: http://git.kernel.org/tip/dd853fd216d1485ed3045ff772079cc8689a9a4a Author: Lukasz Odzioba AuthorDate: Wed, 28 Dec 2016 14:55:40 +0100 Committer: Ingo Molnar CommitDate: Thu, 5 Jan

Re: [PATCH] mm: Respect FOLL_FORCE/FOLL_COW for thp

On Thu, Jan 05, 2017 at 12:36:58AM -0500, Keno Fischer wrote: > In 19be0eaff ("mm: remove gup_flags FOLL_WRITE games from > __get_user_pages()"), > the mm code was changed from unsetting FOLL_WRITE after a COW was resolved to > setting the (newly introduced) FOLL_COW instead. Simultaneously, the

Re: x86: warning in unwind_get_return_address

On Thu, Jan 5, 2017 at 3:49 PM, Josh Poimboeuf wrote: > On Tue, Dec 27, 2016 at 05:38:59PM +0100, Dmitry Vyukov wrote: >> On Thu, Dec 22, 2016 at 6:17 AM, Josh Poimboeuf wrote: >> > On Wed, Dec 21, 2016 at 01:46:36PM +0100, Andrey Konovalov wrote: >> >>

[tip:perf/urgent] perf/x86: Set pmu->module in Intel PMU modules

Commit-ID: 74545f63890e38520eb4d1dbedcadaa9c0dbc824 Gitweb: http://git.kernel.org/tip/74545f63890e38520eb4d1dbedcadaa9c0dbc824 Author: David Carrillo-Cisneros AuthorDate: Thu, 22 Dec 2016 17:17:40 -0800 Committer: Ingo Molnar CommitDate: Thu, 5 Jan

Re: [PATCH v6 05/14] ACPI: platform-msi: retrieve dev id from IORT

On Thu, Jan 05, 2017 at 08:45:37PM +0800, Hanjun Guo wrote: > Hi Lorenzo, > > On 2017/1/5 3:18, Lorenzo Pieralisi wrote: > >On Mon, Jan 02, 2017 at 09:31:36PM +0800, Hanjun Guo wrote: > >>For devices connecting to ITS, it needs dev id to identify > >>itself, and this dev id is represented in the

Re: x86: warning in unwind_get_return_address

On Thu, Jan 05, 2017 at 03:59:52PM +0100, Dmitry Vyukov wrote: > On Thu, Jan 5, 2017 at 3:49 PM, Josh Poimboeuf wrote: > > On Tue, Dec 27, 2016 at 05:38:59PM +0100, Dmitry Vyukov wrote: > >> On Thu, Dec 22, 2016 at 6:17 AM, Josh Poimboeuf > >> wrote: >

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On 01/05/2017 03:16 AM, Pan Xinhui wrote: > > > 在 2017/1/4 17:41, Peter Zijlstra 写道: >> On Tue, Jan 03, 2017 at 05:07:54PM -0500, Waiman Long wrote: >>> On 01/03/2017 11:18 AM, Peter Zijlstra wrote: On Sun, Dec 25, 2016 at 03:26:01PM -0500, Waiman Long wrote: > A number of cmpxchg calls

[tip:x86/urgent] x86/platform/intel-mid: Rename 'spidev' to 'mrfld_spidev'

Commit-ID: 159d3726db12b3476bc59ea0ab0a702103d466b5 Gitweb: http://git.kernel.org/tip/159d3726db12b3476bc59ea0ab0a702103d466b5 Author: Andy Shevchenko AuthorDate: Mon, 2 Jan 2017 11:24:50 +0200 Committer: Ingo Molnar CommitDate: Thu,

[tip:x86/urgent] x86/cpu: Fix typo in the comment for Anniedale

Commit-ID: 754c73cf4d2463022b2c9ae208026bf22564ed06 Gitweb: http://git.kernel.org/tip/754c73cf4d2463022b2c9ae208026bf22564ed06 Author: Andy Shevchenko AuthorDate: Mon, 2 Jan 2017 11:22:29 +0200 Committer: Ingo Molnar CommitDate: Thu,

[PATCH 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code carefully. However, we found that it's very hard to handle the routines that are

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On Thu, Jan 05, 2017 at 10:17:46AM -0500, Waiman Long wrote: > On 01/05/2017 03:16 AM, Pan Xinhui wrote: > > > > > > 在 2017/1/4 17:41, Peter Zijlstra 写道: > >> On Tue, Jan 03, 2017 at 05:07:54PM -0500, Waiman Long wrote: > >>> On 01/03/2017 11:18 AM, Peter Zijlstra wrote: > On Sun, Dec 25,

Re: [PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current state is too deep

On Thu, 2017-01-05 at 23:29 +0800, Alex Shi wrote: > The obsolete commit 71abbbf85 want to introduce a dynamic cstates, > but it was removed for long time. Just left the nonsense deeper > cstate > checking. > > Since all target_residency and exit_latency are going longer in > deeper > idle state,

Re: [PATCH v2] mfd:rtsx: do retry when dma transfer error

On Thu, 05 Jan 2017, 冯伟linux wrote: > > + err = -EILSEQ; > > Why are you using this error code? > > > > when kernel receive the error number is EILSEQ, the SD card requeset > will be retried for some times, instead of dropping it directly. > so we use EILSEQ and frequency reduction to

Re: [PATCH 4/7] mm, vmscan: show LRU name in mm_vmscan_lru_isolate tracepoint

On Thu, Jan 05, 2017 at 11:16:13AM +0100, Michal Hocko wrote: > > > diff --git a/include/trace/events/vmscan.h b/include/trace/events/vmscan.h > > > index 36c999f806bf..7ec59e0432c4 100644 > > > --- a/include/trace/events/vmscan.h > > > +++ b/include/trace/events/vmscan.h > > > @@ -277,9 +277,9 @@

Re: Need information on handling legacy interrupts

On 05/01/17 14:40, Bharat Kumar Gogada wrote: > Hi, > > In pcie-xilinx-nwl.c, the bridge has legacy status read only register where > the status bit is set when > Assert_INTx is received and cleared only when Deassert_INTx is received. > The above scenario is causing issue if an EP takes more

[PATCH] ARM64: dts: meson-gxbb-odroidc2: Disable SCPI DVFS

The current hardware is not able to run with all cores enabled at a cluster frequency superior at 1536MHz. But the currently shipped u-boot for the platform still reports an OPP table with possible DVFS frequency up to 2GHz, and will not change since the off-tree linux tree supports limiting the

Re: [GIT PULL 00/12] perf/urgent fixes

Em Thu, Jan 05, 2017 at 08:36:36AM +0100, Ingo Molnar escreveu: > > * Arnaldo Carvalho de Melo wrote: > > > Hi Ingo, > > > > Please consider pulling, > > > > - Arnaldo > > > > Test results at the end of this message, as usual, news about it: > > > > Has two new targets,

[tip:x86/asm] selftests/x86: Add a selftest for SYSRET to noncanonical addresses

Commit-ID: 6606021401032919c559a829a5d273ba1741b434 Gitweb: http://git.kernel.org/tip/6606021401032919c559a829a5d273ba1741b434 Author: Andy Lutomirski AuthorDate: Mon, 26 Dec 2016 19:20:50 -0800 Committer: Ingo Molnar CommitDate: Thu, 5 Jan 2017

[PATCH v2] perf/x86/intel/uncore: Remove hardcoded socket 0 in Haswell init code

In case anyone finds the actual panic interesting ... BUG: unable to handle kernel paging request at 006563a1 IP: [] hswep_uncore_cpu_init+0x52/0xa0 PGD 0 [2.313897] Oops: [#1] SMP Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0 #1 Hardware name: NEC

Re: linux-next: failure fetching the sunxi tree

Hi Stephen, On Wed, Jan 04, 2017 at 09:31:24AM +1100, Stephen Rothwell wrote: > Hi Maxime, > > On Wed, 21 Dec 2016 09:24:13 +1100 Stephen Rothwell > wrote: > > > > Trying to fetch the sunxi tree > >

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

On 1/5/2017 12:11 AM, Ingo Molnar wrote: * Thomas Garnier wrote: Each processor holds a GDT in its per-cpu structure. The sgdt instruction gives the base address of the current GDT. This address can be used to bypass KASLR memory randomization. With another bug, an

Re: [RFC PATCH v3] sparc64: Add support for Application Data Integrity (ADI)

On 01/05/2017 02:37 AM, Jerome Marchand wrote: On 01/04/2017 11:46 PM, Khalid Aziz wrote: ADI is a new feature supported on sparc M7 and newer processors to allow hardware to catch rogue accesses to memory. ADI is supported for data fetches only and not instruction fetches. An app can enable

[tip:x86/irq] x86/irq, trace: Add __irq_entry annotation to x86's platform IRQ handlers

Commit-ID: c4158ff536439619fa342810cc575ae2c809f03f Gitweb: http://git.kernel.org/tip/c4158ff536439619fa342810cc575ae2c809f03f Author: Daniel Bristot de Oliveira AuthorDate: Wed, 4 Jan 2017 12:20:33 +0100 Committer: Ingo Molnar CommitDate: Thu, 5

Re: [PATCH 4/7] mm, vmscan: show LRU name in mm_vmscan_lru_isolate tracepoint

On Thu 05-01-17 14:56:23, Mel Gorman wrote: > On Thu, Jan 05, 2017 at 11:16:13AM +0100, Michal Hocko wrote: > > > > diff --git a/include/trace/events/vmscan.h > > > > b/include/trace/events/vmscan.h > > > > index 36c999f806bf..7ec59e0432c4 100644 > > > > --- a/include/trace/events/vmscan.h > > >

Re: [PATCH v2,7/9] irqchip/ls-scfg-msi: add LS1046a MSI support

On 05/01/17 08:10, Minghuan Lian wrote: > LS1046a includes 4 MSIRs, each MSIR is assigned a dedicate GIC > SPI interrupt and provides 32 MSI interrupts. Compared to previous > MSI, LS1046a's IBS(interrupt bit select) shift is changed to 2 and > total MSI interrupt number is changed to 128. > >

Re: [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats

On 01/05/2017 06:30 PM, Sakari Ailus wrote: Hi Randy, Thanks for the update. On Thu, Jan 05, 2017 at 12:29:11AM +0800, Randy Li wrote: The formats added by this patch are: V4L2_PIX_FMT_P010 V4L2_PIX_FMT_P010M V4L2_PIX_FMT_P016 V4L2_PIX_FMT_P016M Currently,

Re: [PATCH v5 0/6] inherit dma configuration from parent dev

Hi, On 17/11/16 13:43, Sriram Dash wrote: > For xhci-hcd platform device, all the DMA parameters are not > configured properly, notably dma ops for dwc3 devices. > > The idea here is that you pass in the parent of_node along > with the child device pointer, so it would behave exactly > like the

Re: [PATCH 15/20] ARM/hw_breakpoint: Convert to hotplug state machine

On Wed, Jan 4, 2017 at 2:56 PM, Mark Rutland wrote: > I've just reproduced this locally on my dragonboard APQ8060. Sweet! > It looks like the write_wb_reg() call that's exploding is from > get_max_wp_len(), which we call immediately after registering the >

[PATCH 0/2] fix deadlock caused by recursive cluster locking

This is a formal patch set to solve the deadlock issue on which I previously started a RFC (draft patch), and the discussion happened here: [https://oss.oracle.com/pipermail/ocfs2-devel/2016-October/012455.html] Compared to the previous draft patch, this one is much simple and neat. It neither

Re: [PATCH] [linux-next] bus:qcom : Fix typo in qcom,ebi2.txt

n Thu, Jan 5, 2017 at 3:43 PM, Masanari Iida wrote: > This patch fix 2 spelling typos found in qcom,ebi2.txt > > Signed-off-by: Masanari Iida Reviewed-by: Linus Walleij Rob can you apply this fix to the devicetree git

Re: [PATCH perf/core 3/3] perf-probe: Fix to probe on gcc generated functions in modules

Em Thu, Jan 05, 2017 at 08:20:19PM +0900, Masami Hiramatsu escreveu: > On Wed, 4 Jan 2017 11:48:56 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Wed, Jan 04, 2017 at 12:31:39PM +0900, Masami Hiramatsu escreveu: > > > Fix to probe on gcc generated functions on modules. Since >

Re: [PATCH v2 9/9] ARM: sunxi: Convert pinctrl nodes to generic bindings

On Wed, Jan 04, 2017 at 02:16:23AM +, André Przywara wrote: > So can I ask that we start taking this seriously and stop doing things > which prevent Allwinner boards from being supported properly? > Which would first involve dropping this very patch? The driver still supports the old binding.

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On 01/04/2017 04:41 AM, Peter Zijlstra wrote: > On Tue, Jan 03, 2017 at 05:07:54PM -0500, Waiman Long wrote: >> On 01/03/2017 11:18 AM, Peter Zijlstra wrote: >>> On Sun, Dec 25, 2016 at 03:26:01PM -0500, Waiman Long wrote: A number of cmpxchg calls in qspinlock_paravirt.h were replaced by

Re: [PATCH v2 2/2] nsfs: Add an ioctl() to return owner UID of a userns

Hello Andrei, On 24 December 2016 at 14:16, Andrei Vagin wrote: > On Fri, Dec 23, 2016 at 10:54:53AM +0100, Michael Kerrisk (man-pages) wrote: >> I'd like to write code that discovers the user namespace hierarchy on >> a running system, and also shows who owns the various

VT switch broken with docking station DP

Hi, recently I noticed that VT console doesn't work any longer when I dock a Dell E7270 laptop with a DP monitor. The bug detail is like this: At first, I boot the laptop without dock. I can switch between X and VT via ctrl-alt-F1, so far. Then I dock it to a docking station connected with a

Re: [PATCH 4.4 00/60] 4.4.40-stable review

On Wed, Jan 04, 2017 at 09:46:45PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.40 release. > There are 60 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

Re: [PATCH 0/3] per cpu resume latency

Sorry for missing the mailing list. Add linux-kernel and linux-pm. On 01/05/2017 11:29 PM, Alex Shi wrote: > cpu_dma_latency is designed to keep all cpu awake from deep c-state. > That is good keep system with short response latency. But sometime we > don't need all cpu power especially in a

[PATCH] serial/8250: remove comment about schedule_timeout

Ted T'so has added the function size_fifo in 1999 for the 2.3 series [1], a long time ago. During the 2.5 cycle, Russell King has restructured the serial drivers and, in that process, has suggested using schedule_timeout instead of mdelay in size_fifo. [2] It was only at 2.6.7 that Greg

Re: stack unwinder warning.

On Thu, Jan 05, 2017 at 08:52:49AM -0600, Josh Poimboeuf wrote: > On Tue, Dec 27, 2016 at 02:00:30PM -0500, Dave Jones wrote: > > I'm not sure what to make of this. Josh ? (4.10-rc1) > > > > WARNING: kernel stack frame pointer at c93e7858 in trinity-c6:29122 > > has bad value

Re: [PATCH v3 1/9] arm64: cpufeature: treat unknown fields as RES0

On Wed, Jan 04, 2017 at 05:48:59PM +, Suzuki K. Poulose wrote: > From: Mark Rutland > > Any fields not defined in an arm64_ftr_bits entry are propagated to the > system-wide register value in init_cpu_ftr_reg(), and while we require > that these strictly match for the

Re: x86: warning in unwind_get_return_address

On Thu, Jan 05, 2017 at 09:17:00AM -0600, Josh Poimboeuf wrote: > On Thu, Jan 05, 2017 at 03:59:52PM +0100, Dmitry Vyukov wrote: > > On Thu, Jan 5, 2017 at 3:49 PM, Josh Poimboeuf wrote: > > > On Tue, Dec 27, 2016 at 05:38:59PM +0100, Dmitry Vyukov wrote: > > >> On Thu, Dec

Re: [Patch V7 4/4] irqchip/qeic: remove PPCisms for QEIC

On 26/12/16 08:32, Zhao Qiang wrote: > QEIC was supported on PowerPC, and dependent on PPC, > Now it is supported on other platforms, so remove PPCisms. > > Signed-off-by: Zhao Qiang > --- > Changes for v6: > - new added > Changes for v7: > - fix warning > >

Re: stack unwinder warning.

On Thu, Jan 05, 2017 at 11:02:14AM -0600, Josh Poimboeuf wrote: > On Thu, Jan 05, 2017 at 08:52:49AM -0600, Josh Poimboeuf wrote: > > On Tue, Dec 27, 2016 at 02:00:30PM -0500, Dave Jones wrote: > > > I'm not sure what to make of this. Josh ? (4.10-rc1) > > > > > > WARNING: kernel stack

Re: [RFC PATCH 0/7] locking/rtqspinlock: Realtime queued spinlocks

On 01/05/2017 11:08 AM, Peter Zijlstra wrote: > On Thu, Jan 05, 2017 at 10:55:55AM -0500, Waiman Long wrote: >> What I am saying that we don't need to change spinlock to rtmutex in a >> -RT kernel. Instead, we can use rtqspinlock for this purpose. All the >> sleeping locks will still be converted

Re: [PATCH] serial/8250: remove comment about schedule_timeout

On Thu, Jan 05, 2017 at 04:40:16PM +, One Thousand Gnomes wrote: > On Thu, 5 Jan 2017 13:48:40 -0200 > Thadeu Lima de Souza Cascardo wrote: > > > Ted T'so has added the function size_fifo in 1999 for the 2.3 series > > [1], a long time ago. > > > > During the 2.5

Re: [PATCH 5/5] arm64: dts: add BananaPi-M64 support

On Mon, Jan 02, 2017 at 11:03:46PM +, Andre Przywara wrote: > The Banana Pi M64 board is a typical single board computer based on the > Allwinner A64 SoC. Aside from the usual peripherals it features eMMC > storage, which is connected to the 8-bit capable SDHC2 controller. > Also it has a

Re: [PATCH] ACPI / DMAR: Avoid passing NULL to acpi_put_table()

On Thu, Jan 5, 2017 at 2:24 AM, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Linus reported that commit 174cc7187e6f "ACPICA: Tables: Back port > acpi_get_table_with_size() and early_acpi_os_unmap_memory() from > Linux kernel" added a new

Re: [PATCH net-next 0/3] rxrpc: Update tracing and proc interfaces

org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20170105 Pulled, thanks.

Re: [PATCH v7 3/4] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On Thu, Jan 5, 2017 at 12:20 PM, Hoegeun Kwon wrote: > This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel > driver. This panel has 1440x2560 resolution in 5.7-inch physical > panel in the TM2 device. > > Signed-off-by: Donghwa Lee >

[PATCH] ACPI/IORT: Fix iort_node_get_id() mapping entries indexing

Commit 618f535a6062 ("ACPI/IORT: Add single mapping function") introduced a function (iort_node_get_id()) to retrieve ids for IORT named components. iort_node_get_id() takes an index as input to refer to a specific mapping entry in the mapping array to retrieve the id at a specific index provided

Re: [tip:perf/urgent] perf/x86: Set pmu->module in Intel PMU modules

On Thu, Jan 5, 2017 at 7:52 AM, Peter Zijlstra wrote: > > The first time I saw this I thought about doing something like the > below, but never got around to testing if that works and subsequently > forgot about things again. > > Does this make sense and or work? I'd argue

Question: read-only file access in kernel module (verify checksums)

Good day, I'm going over some code in a kernel module to implement file access functionality in an LKM. I've gone through Grek KH's lengthy article on it, and noted the pitfalls (interpreting data, how one should go through sysfs instead, etc): all good points and duly noted. I have also

Re: [RFC PATCH 0/7] locking/rtqspinlock: Realtime queued spinlocks

On Thu, 5 Jan 2017 12:07:21 -0500 Waiman Long wrote: > I do make the assumption that spinlock critical sections are behaving > well enough. Apparently, that is not a valid assumption. I sent these > RFC patches out to see if it was an idea worth pursuing. If not, I can >

[PATCH v6 16/18] vfio/type1: Allow transparent MSI IOVA allocation

When attaching a group to the container, check the group's reserved regions and test whether the IOMMU translates MSI transactions. If yes, we initialize an IOVA allocator through the iommu_get_msi_cookie API. This will allow the MSI IOVAs to be transparently allocated on MSI controller's

[PATCH] HID: remove use of DRIVER_LICENSE

Local "#define DRIVER_LICENSE" obfuscates which license is used in MODULE_LICENSE(). "fgrep -R MODULE_LICENSE" is more informative when the string is hard coded in MODULE_LICENSE. Signed-off-by: Grant Grundler --- Most of the kernel already uses hard coded strings. The few

[PATCH v6 18/18] iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP anymore

IOMMU_CAP_INTR_REMAP has been advertised in arm-smmu(-v3) although on ARM this property is not attached to the IOMMU but rather is implemented in the MSI controller (GICv3 ITS). Now vfio_iommu_type1 checks MSI remapping capability at MSI controller level, let's correct this. Signed-off-by: Eric

[PATCH v6 12/18] irqdomain: Add irq domain MSI and MSI_REMAP flags

We introduce two new enum values for the irq domain flag: - IRQ_DOMAIN_FLAG_MSI indicates the irq domain corresponds to an MSI domain - IRQ_DOMAIN_FLAG_MSI_REMAP indicates the irq domain has MSI remapping capabilities. Those values will be useful to check all MSI irq domains have MSI

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On 01/05/2017 11:29 AM, Kirill A. Shutemov wrote: > On Thu, Jan 05, 2017 at 11:13:57AM -0800, Dave Hansen wrote: >> On 12/26/2016 05:54 PM, Kirill A. Shutemov wrote: >>> MM would use min(RLIMIT_VADDR, TASK_SIZE) as upper limit of virtual >>> address available to map by userspace. >> >> What

Re: [PATCH v3 1/3] x86/64: Make kernel text mapping always take one whole page table in early boot code

On Thu, Jan 5, 2017 at 6:01 AM, Borislav Petkov wrote: > On Thu, Jan 05, 2017 at 11:28:00AM +0800, Baoquan He wrote: >> Possibly people worry more that no enough space left for kernel modules >> mapping whthin 1G, just a guess. I am fine with making text mapping size >> 1G by

[PATCH 10/10] vtime: Rename vtime_account_user() to vtime_flush()

CONFIG_VIRT_CPU_ACCOUNTING_NATIVE used to accumulate user time and account it on ticks and context switches only through the vtime_account_user() function. Now this model has been generalized on the 3 archs for all kind of cputime (system, irq, ...) and all the cputime flushing happens under

[PATCH 00/10] vtime: Delay cputime accounting to tick / context switch

This version is a rebase on top of latest Linus tree which includes the fix 8f2b468aadc ("s390/vtime: correct system time accounting"). Also a small change: I have moved account_system_index_scaled() to s390 in patch "s390/cputime: delayed accounting of system time" because it is the only user of

Re: [PATCH v3 2/9] arm64: cpufeature: remove explicit RAZ fields

On Wed, Jan 04, 2017 at 05:49:00PM +, Suzuki K. Poulose wrote: > From: Mark Rutland > > We currently have some RAZ fields described explicitly in our > arm64_ftr_bits arrays. These are inconsistently commented, grouped, > and/or applied, and maintaining these is

Re: [PATCH v2 4/4] ARM: dts: keystone: Add "ti,da830-uart" compatible string

On 1/5/2017 1:04 AM, Sekhar Nori wrote: Hi Santosh, On Thursday 05 January 2017 03:30 AM, Santosh Shilimkar wrote: On 1/4/2017 12:30 PM, David Lechner wrote: The TI Keystone SoCs have extra UART registers beyond the standard 8250 registers, so we need a new compatible string to indicate this.

[PATCH v2] drivers: char: mem: Fix thinkos in kmem address checks

When borrowing the pfn_valid() check from mmap_kmem(), somebody managed to get physical and virtual addresses spectacularly muddled up, such that we've ended up with checks for one being the other. Whilst this does indeed prevent out-of-bounds accesses crashing, on most systems it also prevents

Re: [PATCH 2/2] media: rc: add driver for IR remote receiver on MT7623 SoC

Hi Sean, Some review comments. On Fri, Jan 06, 2017 at 12:06:24AM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > This patch adds driver for IR controller on > Mediatek MT7623 SoC. Currently testing successfully > on NEC and SONY remote controller only but it

Re: [PATCH] Update Nanobone dts file to add external FRAM chip

* Mark Jackson [170104 02:56]: > On 15/12/16 10:52, Mark Jackson wrote: > >>From v4.2+ the GPMC code has been changed to reset all the bootloader > > GPMC settings when the kernel starts. > > > > As such, this DTS file now needs the external FRAM defined. > > > >

[PATCH 01/10] powerpc32: Fix stale scaled stime on context switch

On context switch with powerpc32, the cputime is accumulated in the thread_info struct. So the switching-in task must move forward its start time snapshot to the current time in order to later compute the delta spent in system mode. This is what we do for the normal cputime by initializing the

Re: [PATCH] ARM: dts: sunxi: Use axp209.dtsi for Olinuxino Lime2

On Tue, Dec 27, 2016 at 11:22:38AM +0100, Emmanuel Vadot wrote: > Use axp209.dtsi in sun7i-a20-olinuxino-lime2.dts and correct > some regulators. > > DCDC2 is used for vdd-cpu so it should never be bellow 1V and above 1.4V > DCDC3 is used for VDD_INT so same as above. > LD01 is used for the RTC,

Re: [PATCH v3] ARM: dts: sunxi: Add num-cs for A20 spi nodes

On Tue, Dec 27, 2016 at 11:28:07AM +0100, Emmanuel Vadot wrote: > The spi0 controller on the A20 have up to 4 CS (Chip Select) while the > others three only have 1. > Add the num-cs property to each node. > The current driver doesn't read this property but this is useful for > downstream user of

Re: [PATCH] ARM: dts: sunxi: Enable spi1 and spi2 for Olimex A20 SOM EVB

Hi, On Mon, Dec 26, 2016 at 06:53:49PM +0100, Emmanuel Vadot wrote: > Enable the spi1 and spi2 node since the pins are exposed on the UEXT > connectors. > > Signed-off-by: Emmanuel Vadot > --- > arch/arm/boot/dts/sun7i-a20-olimex-som-evb.dts | 2 ++ > 1 file changed, 2

[PATCH net-next] net: make ndo_get_stats64 a void function

The network device operation for reading statistics is only called in one place, and it ignores the return value. Having a structure return value is potentially confusing because some future driver could incorrectly assume that the return value was used. Fix all drivers with ndo_get_stats64 to

[PATCH v4 1/5] crash: move crashkernel parsing and vmcore related code under CONFIG_CRASH_CORE

Traditionally, kdump is used to save vmcore in case of a crash. Some architectures like powerpc can save vmcore using architecture specific support instead of kexec/kdump mechanism. Such architecture specific support also needs to reserve memory, to be used by dump capture kernel. crashkernel

[PATCH v4 2/5] ia64: reuse append_elf_note() and final_note() functions

Get rid of multiple definitions of append_elf_note() & final_note() functions. Reuse these functions compiled under CONFIG_CRASH_CORE Also, define Elf_Word and use it instead of generic u32 or the more specific Elf64_Word. Signed-off-by: Hari Bathini --- Changes

[PATCH v5 0/2] iio: adc: hx711: Add IIO driver for AVIA HX711 ADC

This series adds IIO driver support for the AVIA HX711 ADC which is mostly used in weighting cells. The first patch adds the new DT binding for which a new vendor avia was also added. The second patch is the simple IIO driver implemented as ADC. The protocol is specific to this device and

Re: [PATCH 2/5] drivers: mmc: sunxi: limit A64 MMC2 to 8K DMA buffer

Hi Rob, On Wed, Jan 04, 2017 at 08:07:50AM -0600, Rob Herring wrote: > On Mon, Jan 02, 2017 at 11:03:43PM +, Andre Przywara wrote: > > From: Maxime Ripard > > > > Unlike the A64 user manual reports, the third MMC controller on the > > A64 (and the only one

  1   2   3   4   5   6   7   8   9   10   >