[PATCH v3 2/5] thermal: of: implement .set_trips for device tree thermal zones

From: Sascha Hauer This patch implemnets .set_trips for device tree thermal zones. As the hardware-tracked trip points is supported by thermal core patch[0]. patch[0] "thermal: Add support for hardware-tracked trip points". Signed-off-by: Sascha Hauer

[PATCH v3 4/5] thermal: bang-bang governor: act on lower trip boundary

From: Sascha Hauer With interrupt driven thermal zones we pass the lower and upper temperature on which shall be acted, so in the governor we have to act on the exact lower temperature to be consistent. Otherwise an interrupt maybe generated on the exact lower

[PATCH v3 5/5] thermal: rockchip: add the set_trips function

Whenever the current temperature is updated, the trip points immediately below and above the current temperature are found. A sensor driver callback `set_trips' is then called with the temperatures. Lastly, The sensor will trigger the hardware high temperature interrupts to increase the sampleing

RE: fsl-dcu not works on latest "drm-next"

I found that its regmap endianness issue, so I want to replace the "regmap". Hi Stefan, Do you have any idea about this? Hi Mark, Regmap endianness issue had caused some other drivers not work, like SPI etc. Or this is fixed and I just don't know? Thanks, Meng

[PATCH 21/24] staging: unisys: Move vbushelper.h to visorbus directory

Only visorbus needs this header file so move it to visorbus directory. Signed-off-by: David Kershner --- drivers/staging/unisys/{include => visorbus}/vbushelper.h | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename drivers/staging/unisys/{include =>

[PATCH 15/24] staging: unisys: visorbus: make function descriptions more kerneldoc-like

From: David Binder Per audit feedback from Thomas Gleixner, function descriptions in visorbus_main.c now utilize a more kerneldoc-like formatting. The affected comments do not implement other kerneldoc requirements. Signed-off-by: David Binder

[PATCH v3 1/5] thermal: Add support for hardware-tracked trip points

From: Sascha Hauer This adds support for hardware-tracked trip points to the device tree thermal sensor framework. The framework supports an arbitrary number of trip points. Whenever the current temperature is updated, the trip points immediately below and above the

[PATCH 08/24] staging: unisys: visorbus: use kernel timer instead of workqueue

From: Tim Sell A kernel timer is now used as the vehicle to periodically call the channel_interrupt function of registered visor drivers, instead of a workqueue. This simplifies a lot of things by making periodic_work.c and periodic_work.h no longer necessary. This

[PATCH v3 0/5] Thermal: Support for hardware-tracked trip points

. This series does exactly that. This series patches rebase the conflicts. Note that the hardware-tracked trip points are very well tested currently. Verified and tested on https://github.com/Caesar-github/rockchip/tree/wip/fixes-thermal-0525 That's based on linux-kernel 20160524. Changes in v3: - as Javi

[PATCH 20/24] staging: unisys: visorbus: Add kerneldoc-style comments for visorbus API

From: David Binder Adds kerneldoc-style comments for those functions which may be used outside of the visorbus driver. Signed-off-by: David Binder Signed-off-by: David Kershner ---

[PATCH 16/24] staging: unisys: visorbus: make visorbus_private.h function descriptions more kerneldoc-like

From: David Binder Per audit feedback from Thomas Gleixner, function descriptions in visorbus_private.h now utilize a more kerneldoc-like formatting. The affected comments do not implement other kerneldoc requirements. Signed-off-by: David Binder

[PATCH 12/24] staging: unisys: visorbus: Remove unused functions

From: Bryan Thompson Remove visorbus_clear_channel, visorchannel_signalqueue_slots_avail, visorchannel_signalqueue_max_slots, visorchannel_clear, and visorchannel_debug which are no longer called by any driver. Signed-off-by: Bryan Thompson

[PATCH 06/24] staging: unisys: visorbus: removed unused periodic_test_workqueue

From: Tim Sell periodic_test_workqueue was an unused relic from the past, and was removed. Signed-off-by: Tim Sell Signed-off-by: David Kershner --- drivers/staging/unisys/visorbus/visorbus_main.c | 15

[PATCH 17/24] staging: unisys: visorbus: make visorchannel function descriptions more kerneldoc-like

From: David Binder Per audit feedback from Thomas Gleixner, function descriptions in visorchannel.c now utilize a more kerneldoc-like formatting. The affected comments do not implement other kerneldoc requirements. Signed-off-by: David Binder

[PATCH 13/24] staging: unisys: Remove reference to unused STANDALONE_CLIENT

From: Bryan Thompson The STANDALONE_CLIENT define is no longer used by Unisys driver code. Signed-off-by: Bryan Thompson Signed-off-by: David Kershner --- drivers/staging/unisys/include/visorbus.h | 2 -- 1 file

[PATCH 19/24] staging: unisys: visorbus: Move visorbus-unique functions to private header

From: David Binder Moves function prototypes that are unique to visorbus from include/visorbus.h to visorbus/visorbus_private.h. Signed-off-by: David Binder Signed-off-by: David Kershner ---

RE: [PATCH v8 08/14] usb: otg: add OTG/dual-role core

> -Original Message- > From: Peter Chen [mailto:hzpeterc...@gmail.com] > Sent: Wednesday, May 25, 2016 10:44 AM > To: Roger Quadros > Cc: peter.c...@freescale.com; ba...@kernel.org; t...@atomide.com; > gre...@linuxfoundation.org; dan.j.willi...@intel.com; >

[PATCH 05/24] staging: unisys: include: Remove thread-related enum members

From: David Binder Code relating to ktheads was previously removed from s-Par driver code. This patch cleans up lingering remnants of kthreads by removing thread- related enum types. Signed-off-by: David Binder Signed-off-by: David Kershner

[PATCH 00/24] Fixes comments made by tglx, then move visorbus to drivers/virt

tglx: The following patchset fixes issues you raised during your code review of visorbus on 5/18. Greg: I understand that you aren't currently accepting new patces for staging-next, I just wanted to get the following patches out for review. This patchset requires additiional patches that have

[PATCH 01/24] staging: unisys: visorbus: remove unused module parameters

From: David Binder Removes unused module parameters from visorbus_main.c, in response to findings by SonarQube. Signed-off-by: David Binder Signed-off-by: David Kershner ---

[PATCH 07/24] staging: unisys: visorinput: remove unnecessary locking

From: Tim Sell Locking in the _interrupt() function is NOT necessary so long as we ensure that interrupts have been stopped whenever we need to pause or resume the device, which we now do. While a device is paused, we ensure that interrupts stay disabled, i.e. that the

[PATCH 23/24] Documentation: Move visorbus documentation from staging to Documentation/

This patch simple does a git mv of the drivers/staging/unisys/Documentation directory to Documentation. Renames overview.txt to visorbus.txt and renames sysfs-platform-visorchipset to the correct name sysfs-bus-visorbus. Signed-off-by: David Kershner ---

Re: [PATCH 0/7] x86: uaccess hardening, easy part

On Tue, May 24, 2016 at 6:48 PM, Andy Lutomirski wrote: > This series hardens x86's uaccess code a bit. It adds warnings for > some screwups, adds an OOPS for a major exploitable screwup, and it > improves debuggability a bit by indicating non-default fs in oopses. > > It

[PATCH 03/24] staging: unisys: visorbus: modify format string to match argument

From: David Binder Modifies the format string of snprintf to expect an unsigned int instead of a signed one, per the supplied argument. Signed-off-by: David Binder Signed-off-by: David Kershner ---

[PATCH 02/24] staging: unisys: visorbus: remove unused struct

From: David Binder Removes unused struct definition, channel_size_info, in response to findings by SonarQube. Signed-off-by: David Binder Signed-off-by: David Kershner ---

RE:Custom bags

Hi, Ronta(Xiamen)Co.,LTD, is a well established company working with bags, lanyards and other textile products for many experiences. With many years in this industry, we can offer the right products as what you requested in a short time, no matter it is a big or small order. Please don't

[PATCH] ARM64: dts: rockchip: add thermal zone node for rk3399 SoCs

This adds thermal zone node to rk3399 dtsi, rk3399 thermal data is including the cpu and gpu sensor zone node. At the moment, remove the rk3368 thermal data from rk399 dtsi. The thermal zone node is the node containing all the required info for describing a thermal zone, including its cooling

Re: [PATCH v2 08/12] irqchip: add J-Core AIC driver

On Fri, May 20, 2016 at 09:15:56AM +0100, Marc Zyngier wrote: > On 20/05/16 03:53, Rich Felker wrote: > > Signed-off-by: Rich Felker > > --- > > My previous post of the patch series accidentally omitted omitted > > Cc'ing of subsystem maintainers for the necessary clocksource, >

[RESEND][PATCH] drivers: of: of_reserved_mem: fixup the CMA alignment not to affect dma-coherent

From: Jaewon There was an alignment mismatch issue for CMA and it was fixed by commit 1cc8e3458b51 ("drivers: of: of_reserved_mem: fixup the alignment with CMA setup"). However the way of the commit considers not only dma-contiguous(CMA) but also dma-coherent which has

Re: [RFC][PATCH 1/3] locking: Introduce smp_acquire__after_ctrl_dep

On Tue, May 24, 2016 at 11:01:21PM -0400, Waiman Long wrote: > On 05/24/2016 10:27 AM, Peter Zijlstra wrote: > >Introduce smp_acquire__after_ctrl_dep(), this construct is not > >uncommen, but the lack of this barrier is. > > > >Signed-off-by: Peter Zijlstra (Intel) > >--- > >

Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

Hi Len, On Wed, May 25, 2016 at 12:09 AM, Len Brown wrote: > +mjg59, who may be seeing this issue on a skylake laptop > > Chen-yu, > > Great debugging, but I think there is a more general fix possible than > this DMI quirk. > > I agree that in this example, a grantley server, it

Re: [RFC][PATCH 1/3] locking: Introduce smp_acquire__after_ctrl_dep

On Tue, May 24, 2016 at 09:53:29PM -0700, Paul E. McKenney wrote: > On Tue, May 24, 2016 at 11:01:21PM -0400, Waiman Long wrote: > > On 05/24/2016 10:27 AM, Peter Zijlstra wrote: > > >Introduce smp_acquire__after_ctrl_dep(), this construct is not > > >uncommen, but the lack of this barrier is. > >

Re: [PATCH] net: alx: use custom skb allocator

Hi Jarod, On Fri, May 20, 2016 at 02:26:57PM -0400, Jarod Wilson wrote: > On Fri, May 20, 2016 at 03:56:23PM +0800, Feng Tang wrote: > > Hi, > > > > Please ignore this patch. > > > > I found the problem and made the patch with kernel 4.4 with Ubuntu 12.04 > > on Lenovo Y580. > > > > After

[PATCH v3 01/12] of: add vendor prefix for J-Core

The J-Core project (j-core.org) produces open source cpu and SoC peripheral cores synthesizable as FPGA bitstreams or ASICs. Signed-off-by: Rich Felker --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 07/12] sh: add AT_HWCAP flag for J-Core cas.l instruction

Signed-off-by: Rich Felker --- arch/sh/include/uapi/asm/cpu-features.h | 1 + arch/sh/kernel/cpu/sh2/probe.c | 2 ++ 2 files changed, 3 insertions(+) diff --git a/arch/sh/include/uapi/asm/cpu-features.h b/arch/sh/include/uapi/asm/cpu-features.h index 694abe4..2f1bc85

[PATCH v3 10/12] spi: add driver for J-Core SPI controller

The J-Core "spi2" device is a PIO-based SPI master controller. It differs from "bitbang" devices in that that it's clocked in hardware rather than via soft clock modulation over gpio, and performs byte-at-a-time transfers between the cpu and SPI controller. This driver will be extended to support

[PATCH v3 12/12] sh: add device tree source for J2 FPGA on Mimas v2 board

Signed-off-by: Rich Felker --- arch/sh/boot/dts/j2_mimas_v2.dts | 87 1 file changed, 87 insertions(+) create mode 100755 arch/sh/boot/dts/j2_mimas_v2.dts diff --git a/arch/sh/boot/dts/j2_mimas_v2.dts b/arch/sh/boot/dts/j2_mimas_v2.dts

[PATCH v3 11/12] sh: add defconfig for J-Core J2

This defconfig is intended not to be specific to a particular board; it enables drivers for all currently-supported hardware, and should be updated to include additional drivers as they are added. Signed-off-by: Rich Felker --- arch/sh/configs/j2_defconfig | 38

[PATCH v3 08/12] irqchip: add J-Core AIC driver

There are two versions of the J-Core interrupt controller in use, aic1 which generates interrupts with programmable priorities, but only supports 8 irq lines and maps them to cpu traps in the range 17 to 24, and aic2 which uses traps in the range 64-127 and supports up to 128 irqs, with priorities

[PATCH v3 05/12] of: add J-Core SPI master bindings

Signed-off-by: Rich Felker --- .../devicetree/bindings/spi/jcore,spi.txt | 23 ++ 1 file changed, 23 insertions(+) create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt diff --git

[PATCH v3 00/12] J-core J2 cpu and SoC peripherals support

The following patchset adds support for the J-core J2, an open-source VHDL reimplementation of the SH-2 ISA, and drivers for the associated SoC devices (interrupt controller, clocksource, and SPI). As arch/sh co-maintainer my intent is to include as much as possible in my pull request for the

[PATCH v3 03/12] of: add J-Core interrupt controller bindings

Signed-off-by: Rich Felker --- .../bindings/interrupt-controller/jcore,aic.txt| 29 ++ 1 file changed, 29 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt diff --git

Re: [PATCH 1/5] PCI: Add a new PCI_BUS_FLAGS_MSI_REMAP flag

On 2016/5/25 4:55, Bjorn Helgaas wrote: On Wed, Apr 27, 2016 at 08:43:26PM +0800, Yongji Xie wrote: We introduce a new pci_bus_flags, PCI_BUS_FLAGS_MSI_REMAP which indicates all devices on the bus are protected by the hardware which supports IRQ remapping(intel naming). This changelog is

[PATCH v3 06/12] sh: add support for J-Core J2 processor

At the CPU/ISA level, the J2 is compatible with SH-2, and thus the changes to add J2 support build on existing SH-2 support. However, J2 does not duplicate the memory-mapped SH-2 features like the cache interface. Instead, the cache interfaces is described in the device tree, and new code is added

[PATCH v3 02/12] of: add J-Core cpu bindings

Signed-off-by: Rich Felker --- Documentation/devicetree/bindings/jcore/cpus.txt | 92 1 file changed, 92 insertions(+) create mode 100644 Documentation/devicetree/bindings/jcore/cpus.txt diff --git a/Documentation/devicetree/bindings/jcore/cpus.txt

[PATCH v3 09/12] clocksource: add J-Core timer/clocksource driver

At the hardware level, the J-Core PIT is integrated with the interrupt controller, but it is represented as its own device and has an independent programming interface. It provides a 12-bit countdown timer, which is not presently used, and a periodic timer. The interval length for the latter is

[PATCH v3 04/12] of: add J-Core timer bindings

Signed-off-by: Rich Felker --- .../devicetree/bindings/timer/jcore,pit.txt| 28 ++ 1 file changed, 28 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt diff --git

Re: [PATCH 3/5] PCI: Set PCI_BUS_FLAGS_MSI_REMAP if MSI controller supports IRQ remapping

On 2016/5/25 5:04, Bjorn Helgaas wrote: On Wed, Apr 27, 2016 at 08:43:28PM +0800, Yongji Xie wrote: On ARM HW the capability of IRQ remapping is abstracted on MSI controller side. MSI_FLAG_IRQ_REMAPPING is used to advertise this [1]. To have a universal flag to test this capability for

Re: [PATCH 2/5] iommu: Set PCI_BUS_FLAGS_MSI_REMAP if IOMMU have capability of IRQ remapping

On 2016/5/25 5:11, Bjorn Helgaas wrote: On Wed, Apr 27, 2016 at 08:43:27PM +0800, Yongji Xie wrote: The capability of IRQ remapping is abstracted on IOMMU side on some archs. There is a existing flag IOMMU_CAP_INTR_REMAP for this. To have a universal flag to test this capability for different

Re: [PATCH v2 05/10] drm/rockchip: analogix_dp: add rk3399 eDP support

On 05/25/2016 02:23 AM, Heiko Stuebner wrote: Am Dienstag, 24. Mai 2016, 11:12:20 schrieb Doug Anderson: Hi, On Tue, May 24, 2016 at 3:17 AM, Heiko Stuebner wrote: --- a/Documentation/devicetree/bindings/display/bridge/analogix_dp.txt +++

Re: [PATCH v2 05/10] drm/rockchip: analogix_dp: add rk3399 eDP support

On 05/24/2016 06:17 PM, Heiko Stuebner wrote: Am Dienstag, 24. Mai 2016, 14:57:23 schrieb Yakir Yang: [] diff --git a/drivers/gpu/drm/rockchip/analogix_dp-rockchip.c b/drivers/gpu/drm/rockchip/analogix_dp-rockchip.c index 29c4105..d5d4e04 100644 ---

Re: hwmon.c as a kernel module in 3.18

Never mind. I figured it out. The commit that changed the behavior is : commit de0a41484c47d783dd4d442914815076aa2caac2 Author: Paul Gortmaker Date: Mon Oct 1 11:43:49 2012 -0400 tg3: unconditionally select HWMON support when tg3 is enabled. So I had exactly

Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c

> On May 24, 2016, at 2:36 PM, Larry Finger wrote: > > On 05/24/2016 02:25 PM, Matthew McClintock wrote: >> On May 24, 2016, at 2:16 PM, Larry Finger wrote: >>> >>> On 05/24/2016 02:13 PM, Matthew McClintock wrote: I’m seeing this

[PATCH v7 03/15] acpi, numa: remove duplicate NULL check

From: Hanjun Guo The argument "header" for acpi_table_print_srat_entry() is always checked before the function is called, it's duplicate to check it again, remove it. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter

Re: [PATCH] iommu/vt-d: reduce extra first level entry in iommu->domains

Hi, Joerg Not sure whether you think this calculation is correct. If I missed something for this " + 1" in your formula, I am glad to hear your explanation. So that I could learn something from you :-) Have a good day~ On Sat, May 21, 2016 at 02:41:51AM +, Wei Yang wrote: >In commit

Re: [PATCH v1 1/3] Add the latent_entropy gcc plugin

On 24 May 2016 at 10:32, Kees Cook wrote: > On Mon, May 23, 2016 at 3:15 PM, Emese Revfy wrote: > > This plugin mitigates the problem of the kernel having too little entropy > > during > > and after boot for generating crypto keys. > > > I'm excited to see this! This looks

Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c

On Tue, May 24, 2016 at 05:31:51PM -0500, Matthew McClintock wrote: > > > On May 24, 2016, at 2:36 PM, Larry Finger wrote: > > > > On 05/24/2016 02:25 PM, Matthew McClintock wrote: > >> On May 24, 2016, at 2:16 PM, Larry Finger > >> wrote:

Re: [rcutorture] 8704baab9b: WARNING: CPU: 0 PID: 30 at kernel/rcu/rcuperf.c:363 rcu_perf_writer

On Tue, May 24, 2016 at 11:06:52AM -0700, Paul E. McKenney wrote: > On Mon, May 23, 2016 at 12:35:35PM +0800, Boqun Feng wrote: > > On Sun, May 22, 2016 at 08:28:06AM -0700, Paul E. McKenney wrote: > > > On Sun, May 22, 2016 at 02:26:49PM +0800, Boqun Feng wrote: > > > > Hi Paul, > > > > > > > >

Re: [PATCH] f2fs: introduce on-disk layout version checking functionality

On Tue, 2016-05-24 at 01:53 -0700, Christoph Hellwig wrote: [snipped] > > That goes on to the next question: why do we even need a config option > for 16TB+ volume support? > I believe that it makes sense to have config option during implementation phase. I mean that it needs to protect this

Re: [PATCH] f2fs: introduce on-disk layout version checking functionality

On Tue, 2016-05-24 at 01:52 -0700, Christoph Hellwig wrote: > On Mon, May 23, 2016 at 01:08:05PM -0700, Viacheslav Dubeyko wrote: > > I think that it's some confusion. I didn't introduce any new fields in > > struct f2fs_super_block. The "major_ver" and "minor_ver" fields exist in > > F2FS

Re: [x86/cpufeature] 7b5e74e637: BUG: unable to handle kernel paging request at 6b636170

75f253e8b # 01:56 27+ > 0 Merge > 'linux-review/Rajneesh-Bhardwaj/platform-x86-Add-PMC-Driver-for-Intel-Core-SoC/20160524-222735' > into devel-catchup-201605250104 > > git bisect bad 5c7f53f3c9182146efd37be1989f8e23e3b796ff # 02:01 0- > 1 Merge >

Re: [PATCH] f2fs: introduce on-disk layout version checking functionality

Hi Jaegeuk, On Mon, 2016-05-23 at 14:13 -0700, Jaegeuk Kim wrote: > Hi Slava, > > On Thu, May 19, 2016 at 10:46:06AM -0700, Viacheslav Dubeyko wrote: > ... > > > > +#ifdef CONFIG_F2FS_16TB_VOLUME_SUPPORT > > +#define F2FS_MAX_SUPP_MAJOR_VERSION(2) > > +#define

[PATCH] rcuperf: Don't treat gp_exp mis-setting as a WARN

0day found a boot warning triggered in rcu_perf_writer() on !SMP kernel: WARN_ON(rcu_gp_is_normal() && gp_exp); , the root cause of which is trying to measure expedited grace periods(by setting gp_exp to true by default) when all the grace periods are normal(TINY RCU only has normal

Re: [PATCH v3 7/9] powerpc/powernv: Add platform support for stop instruction

On 05/24/2016 02:17 PM, Madhavan Srinivasan wrote: > > > On Monday 23 May 2016 08:48 PM, Shreyas B. Prabhu wrote: >> POWER ISA v3 defines a new idle processor core mechanism. In summary, >> a) new instruction named stop is added. This instruction replaces >> instructions like nap, sleep,

Re: [PATCH v2 03/12] of: add J-Core interrupt controller bindings

On Tue, May 24, 2016 at 09:09:41AM +0100, Marc Zyngier wrote: > On 23/05/16 22:13, Rich Felker wrote: > > On Mon, May 23, 2016 at 03:53:20PM -0500, Rob Herring wrote: > >> On Fri, May 20, 2016 at 02:53:04AM +, Rich Felker wrote: > >>> Signed-off-by: Rich Felker > >>> --- >

[PATCH 1/4] samples/kprobe: convert the printk to pr_info/pr_err

We prefer to use the pr_* to print out the log now, this patch converts the printk to pr_info. In the error path, use the pr_err to replace the printk. Signed-off-by: Huang Shijie --- samples/kprobes/kprobe_example.c | 29 - 1 file changed, 12

Re: [PATCH] rcuperf: Don't treat gp_exp mis-setting as a WARN

On Wed, May 25, 2016 at 09:25:33AM +0800, Boqun Feng wrote: > 0day found a boot warning triggered in rcu_perf_writer() on !SMP kernel: > > WARN_ON(rcu_gp_is_normal() && gp_exp); > > , the root cause of which is trying to measure expedited grace > periods(by setting gp_exp to true by

linux-next: Tree for May 25

Hi all, Please do not add any v4.8 destined material to your linux-next included branches until after v4.7-rc1 has been released. Changes since 20160524: Non-merge commits (relative to Linus' tree): 978 876 files changed, 29717 insertions(+), 8810 deletions

[PATCH] pinctrl: copy per-pin driver private data to struct pin_desc

Currently, struct pinctrl_pin_desc can have per-pin driver private data, but it is not copied to struct pin_desc. For a driver with sparse pin space, for-loop search like below would be necessary in order to get the driver-specific data for a desired pin number. for (i = 0; i <

Re: [PATCH] ACPI / Thermal / video: fix max_level incorrect value

Valdis, can you please give the patch a try? Thanks. -Aaron On Sat, May 21, 2016 at 03:55:00PM +0800, Aaron Lu wrote: > I think I have found the problem, please give the patch a test, thanks. > > From: Aaron Lu > Date: Sat, 21 May 2016 15:30:46 +0800 > Subject: [PATCH] ACPI

Re: zone_reclaimable() leads to livelock in __alloc_pages_slowpath()

On 05/24, Michal Hocko wrote: > > On Mon 23-05-16 17:14:19, Oleg Nesterov wrote: > > On 05/23, Michal Hocko wrote: > [...] > > > Could you add some tracing and see what are the numbers > > > above? > > > > with the patch below I can press Ctrl-C when it hangs, this breaks the > > endless loop and

Re: [GIT PULL] y2038 changes for vfs

On Tue, May 24, 2016 at 3:23 PM, Linus Torvalds wrote: > > Just as an example: code that does > > dir->i_mtime = dir->i_ctime = CURRENT_TIME_SEC; > > could pretty mechanically be converted to > > dir->i_mtime = dir->i_ctime = current_fs_time(sb);

Re: [PATCH v4] KVM: halt-polling: poll for the upcoming fire timers

2016-05-25 1:15 GMT+08:00 Christian Borntraeger : > On 05/24/2016 09:57 AM, Wanpeng Li wrote: >> From: Wanpeng Li >> >> If an emulated lapic timer will fire soon(in the scope of 10us the >> base of dynamic halt-polling, lower-end of message passing

Re: x86: A process doesn't stop on hw breakpoints sometimes

On 05/23, Andy Lutomirski wrote: > > I'm guessing you're either hitting a subtle bug in the mess that is > breakpoint handling or you're hitting a bug in perf's context switch > code. yes, same feeling... > Given that the breakpoint gets missed many times in a row, yes, the child specially

Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c

On Tue, May 24, 2016 at 08:20:46PM -0500, Matthew McClintock wrote: > > > On May 24, 2016, at 8:10 PM, Al Viro wrote: > > > > Slap the WARN_ON(!size); in the very beginning of iov_iter_advance(), see > > where it's triggered... > > diff --git a/lib/iov_iter.c

Re: [PATCH v3] sched/cputime: add steal time support to full dynticks CPU time accounting

Ping Paolo or Peterz. 2016-05-25 3:22 GMT+08:00 Rik van Riel : > On Wed, 2016-05-18 at 20:27 +0800, Wanpeng Li wrote: >> From: Wanpeng Li >> >> This patch adds steal guest time support to full dynticks CPU >> time accounting. After 'commit ff9a9b4c4334

[PATCH v5] KVM: halt-polling: poll for the upcoming fire timers

From: Wanpeng Li If an emulated lapic timer will fire soon(in the scope of 10us the base of dynamic halt-polling, lower-end of message passing workload latency TCP_RR's poll time < 10us) we can treat it as a short halt, and poll to wait it fire, the fire callback

[PATCH 11/24] staging: unisys: visorbus: Remove unnecessary EXPORT_SYMBOL statements

From: Bryan Thompson The driver that is now visorbus started out as multiple separate drivers, and when they were merged the EXPORT_SYMBOL statements that were required for separate drivers were left in the code. This patch removes those now unnecessary exports.

[PATCH 14/24] staging: unisys: visorbus: vbusdeviceinfo function descriptions more kerneldoc-like

From: David Binder Per audit feedback from Thomas Gleixner, function descriptions in vbusdeviceinfo.h now utilize a more kerneldoc-like formatting. The affected comments do not implement other kerneldoc requirements. Signed-off-by: David Binder

[PATCH 04/24] staging: unisys: visornic: Correct comment spelling mistake

From: David Binder Fixes a comment spelling mistake in visornic. Signed-off-by: David Binder Signed-off-by: David Kershner --- drivers/staging/unisys/visornic/visornic_main.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 09/24] staging: unisys: visorbus: remove periodic_work.h/.c

From: Tim Sell These files were made no-longer-necessary by recent commits. Signed-off-by: Tim Sell Signed-off-by: David Kershner --- drivers/staging/unisys/include/periodic_work.h | 40 -

[PATCH v5 4/8] perf record: Introduce rec->overwrite_evlist for overwritable events

Create an auxiliary evlist for overwritable events. Before mmap, build this evlist and set 'overwrite' and 'backward' attribute. Since perf_evlist__mmap_ex() only maps events when evsel->overwrite matches evlist's corresponding attributes, with these two evlists an event goes to either

[PATCH v5 3/8] perf tests: Add testcase for auxiliary evlist

Improve test backward-ring-buffer, trace both enter and exit event of prctl() syscall, utilize auxiliary evlist to mmap enter and exit event into separated mmaps. Signed-off-by: Wang Nan Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc:

[PATCH v5 8/8] perf tools: Check write_backward during evlist config

Before this patch, when using overwritable ring buffer on an old kernel, error message is misleading: # ~/perf record -m 1 -e raw_syscalls:*/overwrite/ -a Error: The raw_syscalls:sys_enter event is not supported. This patch output clear error message to tell user his/her kernel is too old:

[PATCH v5 1/8] perf tools: Check 'base' pointer before checking refcnt when put a mmap

evlist->mmap[i]->refcnt could be 0 if an evlist has no evsel or all evsels don't match the evlist during mmap. For example, when all evsels are overwritable but the evlist itself is normal. To avoid crashing, perf should check 'base' pointer before checking refcnt, and raise bug only when base is

[PATCH v5 6/8] perf tools: Enable overwrite settings

This patch allows following config terms and option: Globally setting events to overwrite; # perf record --overwrite ... Set specific events to be overwrite or no-overwrite. # perf record --event cycles/overwrite/ ... # perf record --event cycles/no-overwrite/ ... Add missing config terms

[PATCH v5 0/8] perf tools: Support overwritable ring buffer

This patch set enables daemonized perf recording by utilizing overwritable backward ring buffer. With this feature one can put perf background, and dump ring buffer records by a SIGUSR2 when he/she find something unusual. For example, following command record system calls, schedule events and

[PATCH v5 5/8] perf record: Toggle overwrite ring buffer for reading

overwrite_evt_state is introduced to reflect the state of overwritable ring buffers. It is a state machine with 3 states: RUNNING --(1)--> DATA_PENDING --(2)--> EMPTY ^ ^ | | |___(disallow)___/| ||

Re: [PATCH v4 08/10] powerpc/powernv: Add platform support for stop instruction

Hi Shreyas, On Tue, May 24, 2016 at 06:45:12PM +0530, Shreyas B. Prabhu wrote: > POWER ISA v3 defines a new idle processor core mechanism. In summary, > a) new instruction named stop is added. This instruction replaces > instructions like nap, sleep, rvwinkle. > b) new per thread SPR

Re: [PATCH 4/4] MAINTAINERS: mark bcache as orphan

On Tue, 24 May 2016, Joe Perches wrote: > > The submitted patches are not being reacted upon, and Jens is only picking  > > up stable fixes on an rather ad-hoc basis. > > > > Link: lkml.kernel.org/r/574462c5.40...@kernel.dk > > Signed-off-by: Jiri Kosina > > --- > >  

[PATCH v5 7/8] perf tools: Don't warn about out of order event if write_backward is used

If write_backward attribute is set, records are written into kernel ring buffer from end to beginning, but read from beginning to end. To avoid 'XX out of order events recorded' warning message (timestamps of records is in reverse order when using write_backward), suppress the warning message if

[PATCH v5 2/8] perf tools: Choose correct reading direction according to evlist->backward

Now we have evlist->backward to indicate the mmap direction. Make perf_evlist__mmap_read() choose right direction automatically. Signed-off-by: Wang Nan Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Masami Hiramatsu

Re: [PATCH v6 11/12] zsmalloc: page migration support

Hello Sergey, On Tue, May 24, 2016 at 03:28:01PM +0900, Minchan Kim wrote: > > hm... zsmalloc is getting sooo complex now. > > > > `system_wq' -- can we have problems here when the system is getting > > low on memory and workers are getting increasingly busy trying to > > allocate the memory

Re: [RFC PATCH] drivers/pinctrl: Add pinctrl-ast2400

Hi Linus, On Mon, 2016-05-23 at 14:38 +0200, Linus Walleij wrote: > Hi sorry for taking so long before reviewing. Too busy, what can I say. No worries, I expected as much. Thanks for taking the time! > > On Fri, May 6, 2016 at 8:20 AM, Andrew Jeffery wrote: > > > > > Add

[PATCH v7 10/15] acpi, numa: remove unneeded acpi_numa=1

From: Hanjun Guo acpi_numa is default to 0, it's set to -1 when disable acpi numa or when a bad SRAT is parsed, and it's only consumed in srat_disabled() (compare it with 0) to continue parse the SRAT or not, so we don't need to set acpi_numa to 1 when we get a valid SRAT

[PATCH v7 09/15] acpi, numa: move bad_srat() and srat_disabled() to drivers/acpi/numa.c

From: David Daney bad_srat() and srat_disabled() are shared by x86 and follow-on arm64 patches. Move them to drivers/acpi/numa.c in preparation for arm64 support. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter

[PATCH v7 01/15] acpi, numa: Use pr_fmt() instead of printk

From: Hanjun Guo Just do some cleanups to replace printk with pr_fmt(). Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney --- drivers/acpi/numa.c | 17

[PATCH v7 08/15] x86, acpi, numa: cleanup acpi_numa_processor_affinity_init()

From: Hanjun Guo Cleanup acpi_numa_processor_affinity_init() in preparation for its move to drivers/acpi/numa.c. It will be reused by arm64, this has no functional change. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter

Re: [PATCH] tracing: Choose static tp_printk buffer by explicit nesting count

On Tue, 24 May 2016 15:52:28 -0700 Andy Lutomirski wrote: > Currently, the trace_printk code chooses which static buffer to use based > on what type of atomic context (NMI, IRQ, etc) it's in. Simplify the > code and make it more robust: simply count the nesting depth and choose

Re: [PATCH v2] cpufreq: stats: Walk online CPUs with CPU offline/online locked

On Tuesday, May 24, 2016 05:47:17 PM Viresh Kumar wrote: > On 24-05-16, 14:13, Rafael J. Wysocki wrote: > > I don't really get it why you don't like get/put_online_cpus() so much. > > Not that I don't like them, I just wanted to see if its possible to > work without any additional locking. > >

  1   2   3   4   5   6   7   8   9   10   >