RE: [PATCH v5 6/7] iommu/exynos: Add runtime pm support

2016-10-21 Thread Sricharan
Hi Marek, >This patch adds runtime pm implementation, which is based on previous >suspend/resume code. SYSMMU controller is now being enabled/disabled mainly >from the runtime pm callbacks. System sleep callbacks relies on generic >pm_runtime_force_suspend/pm_runtime_force_resume helpers. To

RE: [PATCH v5 6/7] iommu/exynos: Add runtime pm support

2016-10-21 Thread Sricharan
Hi Marek, >This patch adds runtime pm implementation, which is based on previous >suspend/resume code. SYSMMU controller is now being enabled/disabled mainly >from the runtime pm callbacks. System sleep callbacks relies on generic >pm_runtime_force_suspend/pm_runtime_force_resume helpers. To

Re: [PATCH 0/4] IIO wrapper drivers, dpot-dac and envelope-detector

2016-10-21 Thread Peter Rosin
On 2016-10-21 09:17, ji...@kernel.org wrote: > On 20.10.2016 19:17, Peter Rosin wrote: >> On 2016-10-20 19:37, Jonathan Cameron wrote: >>> On 20 October 2016 18:30:19 BST, Jonathan Cameron >>> wrote: On 20 October 2016 13:55:12 BST, Lars-Peter Clausen

Re: [PATCH 0/4] IIO wrapper drivers, dpot-dac and envelope-detector

2016-10-21 Thread Peter Rosin
On 2016-10-21 09:17, ji...@kernel.org wrote: > On 20.10.2016 19:17, Peter Rosin wrote: >> On 2016-10-20 19:37, Jonathan Cameron wrote: >>> On 20 October 2016 18:30:19 BST, Jonathan Cameron >>> wrote: On 20 October 2016 13:55:12 BST, Lars-Peter Clausen wrote: > On 10/20/2016 11:25

Re: [PATCH 2/2] drm/i915/gvt: fix compilation

2016-10-21 Thread Zhenyu Wang
On 2016.10.21 17:25:50 +0200, Arnd Bergmann wrote: > Two functions in the newly added gvt render code are obviously > broken, as they reference a variable without initialization and > don't reference another variable at all: > > drivers/gpu/drm/i915/gvt/render.c: In function >

Re: [PATCH 2/2] drm/i915/gvt: fix compilation

2016-10-21 Thread Zhenyu Wang
On 2016.10.21 17:25:50 +0200, Arnd Bergmann wrote: > Two functions in the newly added gvt render code are obviously > broken, as they reference a variable without initialization and > don't reference another variable at all: > > drivers/gpu/drm/i915/gvt/render.c: In function >

Re: why getrandom blocking does not work with /dev/urandom

2016-10-21 Thread Theodore Ts'o
On Sat, Oct 22, 2016 at 05:43:36AM +0200, Stephan Mueller wrote: > Hi Ted, > > as mentioned, I looked a bit deeper into the issue of adding the blocking > behavior of getrandom to /dev/urandom. > > As you and I already identified, moving that blocking behavior to > /dev/urandom > simply does

Re: why getrandom blocking does not work with /dev/urandom

2016-10-21 Thread Theodore Ts'o
On Sat, Oct 22, 2016 at 05:43:36AM +0200, Stephan Mueller wrote: > Hi Ted, > > as mentioned, I looked a bit deeper into the issue of adding the blocking > behavior of getrandom to /dev/urandom. > > As you and I already identified, moving that blocking behavior to > /dev/urandom > simply does

Re: [PATCH 1/2] drm/i915/gvt: add ACPI and 64BIT dependencies

2016-10-21 Thread Zhenyu Wang
On 2016.10.21 17:25:49 +0200, Arnd Bergmann wrote: > The newly added gvt code produces lots of serious warnings and errors > when either built on 32-bit x86, or built with ACPI disabled, e.g. > > drivers/gpu/drm/i915/gvt/gtt.c: In function ???read_pte64???: > drivers/gpu/drm/i915/gvt/gtt.c:277:2:

Re: [PATCH 1/2] drm/i915/gvt: add ACPI and 64BIT dependencies

2016-10-21 Thread Zhenyu Wang
On 2016.10.21 17:25:49 +0200, Arnd Bergmann wrote: > The newly added gvt code produces lots of serious warnings and errors > when either built on 32-bit x86, or built with ACPI disabled, e.g. > > drivers/gpu/drm/i915/gvt/gtt.c: In function ???read_pte64???: > drivers/gpu/drm/i915/gvt/gtt.c:277:2:

Re: [PATCH] ARM: dts: rockchip: add i2c-bus subnode to edp

2016-10-21 Thread ayaka
On 10/21/2016 04:25 PM, Heiko Stuebner wrote: Am Donnerstag, 20. Oktober 2016, 15:47:56 CEST schrieb Tomeu Vizoso: On 10/20/2016 03:45 PM, Heiko Stübner wrote: Am Donnerstag, 20. Oktober 2016, 10:07:25 schrieb Tomeu Vizoso: Add an empty 'i2c-bus' subnode to the edp node just so that the I2C

Re: [PATCH] ARM: dts: rockchip: add i2c-bus subnode to edp

2016-10-21 Thread ayaka
On 10/21/2016 04:25 PM, Heiko Stuebner wrote: Am Donnerstag, 20. Oktober 2016, 15:47:56 CEST schrieb Tomeu Vizoso: On 10/20/2016 03:45 PM, Heiko Stübner wrote: Am Donnerstag, 20. Oktober 2016, 10:07:25 schrieb Tomeu Vizoso: Add an empty 'i2c-bus' subnode to the edp node just so that the I2C

why getrandom blocking does not work with /dev/urandom

2016-10-21 Thread Stephan Mueller
Hi Ted, as mentioned, I looked a bit deeper into the issue of adding the blocking behavior of getrandom to /dev/urandom. As you and I already identified, moving that blocking behavior to /dev/urandom simply does not work. The system does not boot. The reason to this issue is actually quite

why getrandom blocking does not work with /dev/urandom

2016-10-21 Thread Stephan Mueller
Hi Ted, as mentioned, I looked a bit deeper into the issue of adding the blocking behavior of getrandom to /dev/urandom. As you and I already identified, moving that blocking behavior to /dev/urandom simply does not work. The system does not boot. The reason to this issue is actually quite

Re: [PATCH v2 3/3] ARM: dts: imx6qdl-apalis: Use enable-gpios property for backlight

2016-10-21 Thread Shawn Guo
On Mon, Sep 19, 2016 at 10:41:53AM +0530, Sanchayan Maity wrote: > Use enable-gpios property of PWM backlight driver for backlight > control. > > Signed-off-by: Sanchayan Maity Applied, thanks.

Re: [PATCH v2 3/3] ARM: dts: imx6qdl-apalis: Use enable-gpios property for backlight

2016-10-21 Thread Shawn Guo
On Mon, Sep 19, 2016 at 10:41:53AM +0530, Sanchayan Maity wrote: > Use enable-gpios property of PWM backlight driver for backlight > control. > > Signed-off-by: Sanchayan Maity Applied, thanks.

Re: [PATCH v2 2/3] ARM: dts: imx6q-apalis-ixora: Remove use of pwm-leds

2016-10-21 Thread Shawn Guo
On Mon, Sep 19, 2016 at 10:41:52AM +0530, Sanchayan Maity wrote: > Remove use of pwm-leds and use the standard /sys/class/pwm > interface from PWM subsystem. > > Signed-off-by: Sanchayan Maity > Acked-by: Marcel Ziswiler Applied, thanks.

Re: [PATCH v2 2/3] ARM: dts: imx6q-apalis-ixora: Remove use of pwm-leds

2016-10-21 Thread Shawn Guo
On Mon, Sep 19, 2016 at 10:41:52AM +0530, Sanchayan Maity wrote: > Remove use of pwm-leds and use the standard /sys/class/pwm > interface from PWM subsystem. > > Signed-off-by: Sanchayan Maity > Acked-by: Marcel Ziswiler Applied, thanks.

Re: Re: [PATCH] pcie: aer: aerdrv: PCIe AER workaround and handling for ASR1K platforms.

2016-10-21 Thread David Singleton -X (davsingl - MONTA VISTA SOFTWARE INC at Cisco)
Bjorn, sorry for the delay in getting back to you. The first patch was incomplete. The patch was not a complete unit. There was a second patch that has the callers of the routines in question. Appended are the two patches merged into one new patch. And here is an explanation from

Re: Re: [PATCH] pcie: aer: aerdrv: PCIe AER workaround and handling for ASR1K platforms.

2016-10-21 Thread David Singleton -X (davsingl - MONTA VISTA SOFTWARE INC at Cisco)
Bjorn, sorry for the delay in getting back to you. The first patch was incomplete. The patch was not a complete unit. There was a second patch that has the callers of the routines in question. Appended are the two patches merged into one new patch. And here is an explanation from

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

2016-10-21 Thread Shawn Guo
On Mon, Sep 19, 2016 at 10:41:51AM +0530, Sanchayan Maity wrote: > Remove the use of DDC I2C bus bitbang to support reading of EDID > and rely on support from internal HDMI I2C master controller instead. > As a result remove the device tree property ddc-i2c-bus. > > Signed-off-by: Sanchayan Maity

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

2016-10-21 Thread Shawn Guo
On Mon, Sep 19, 2016 at 10:41:51AM +0530, Sanchayan Maity wrote: > Remove the use of DDC I2C bus bitbang to support reading of EDID > and rely on support from internal HDMI I2C master controller instead. > As a result remove the device tree property ddc-i2c-bus. > > Signed-off-by: Sanchayan Maity

Re: [PATCH] ARM: dts: imx6: Add support for Toradex Colibri iMX6 module

2016-10-21 Thread Shawn Guo
On Wed, Sep 21, 2016 at 04:54:38PM +0530, Sanchayan Maity wrote: > Add support for Toradex Colibri iMX6 module. > > Signed-off-by: Sanchayan Maity Applied, thanks.

Re: [PATCH] ARM: dts: imx6: Add support for Toradex Colibri iMX6 module

2016-10-21 Thread Shawn Guo
On Wed, Sep 21, 2016 at 04:54:38PM +0530, Sanchayan Maity wrote: > Add support for Toradex Colibri iMX6 module. > > Signed-off-by: Sanchayan Maity Applied, thanks.

perf: perf_fuzzer triggers vmalloc_fault (then crashes)

2016-10-21 Thread Vince Weaver
This is on an AMD a10 system. With paranoid=1. Think it's probably unrelated to the (unreseolved) AMD IBS issues. This is 4.9-rc0 just before rc1 (can't get actual rc1 to boot) Machine locks hard after this. [ 8098.085662] BAD LUCK: lost 42 message(s) from NMI context! [ 8098.085663]

perf: perf_fuzzer triggers vmalloc_fault (then crashes)

2016-10-21 Thread Vince Weaver
This is on an AMD a10 system. With paranoid=1. Think it's probably unrelated to the (unreseolved) AMD IBS issues. This is 4.9-rc0 just before rc1 (can't get actual rc1 to boot) Machine locks hard after this. [ 8098.085662] BAD LUCK: lost 42 message(s) from NMI context! [ 8098.085663]

Re: [PATCH][v12] PM / hibernate: Verify the consistent of e820 memory map by md5 digest

2016-10-21 Thread joeyli
Hi Chen Yu, On Thu, Oct 20, 2016 at 04:14:52PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when > trying to resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Re: [PATCH][v12] PM / hibernate: Verify the consistent of e820 memory map by md5 digest

2016-10-21 Thread joeyli
Hi Chen Yu, On Thu, Oct 20, 2016 at 04:14:52PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when > trying to resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Geschäftsvorschlag!!!

2016-10-21 Thread postmaster
-- Geschäftsvorschlag!!! Ich vermute das diese E-Mail eine Überraschung für Sie sein wird, aber es ist wahr.Ich bin bei einer routinen Überprüfung in meiner Bank (First National Bank von Süd Afrika) wo ich arbeite, auf einem Konto gestoßen,was nicht in anspruch genommen worden ist, wo

Geschäftsvorschlag!!!

2016-10-21 Thread postmaster
-- Geschäftsvorschlag!!! Ich vermute das diese E-Mail eine Überraschung für Sie sein wird, aber es ist wahr.Ich bin bei einer routinen Überprüfung in meiner Bank (First National Bank von Süd Afrika) wo ich arbeite, auf einem Konto gestoßen,was nicht in anspruch genommen worden ist, wo

[PATCH] arch/x86: Don't try to poke disabled/non-existent APIC

2016-10-21 Thread ville . syrjala
From: Ville Syrjälä Apparently trying to poke a disabled or non-existent APIC leads to a box that doesn't even boot. Let's not do that. No real clue if this is the right fix, but at least my P3 machine boots again. Cc: sta...@vger.kernel.org Cc: Ingo Molnar

[PATCH] arch/x86: Don't try to poke disabled/non-existent APIC

2016-10-21 Thread ville . syrjala
From: Ville Syrjälä Apparently trying to poke a disabled or non-existent APIC leads to a box that doesn't even boot. Let's not do that. No real clue if this is the right fix, but at least my P3 machine boots again. Cc: sta...@vger.kernel.org Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc:

Re: [PATCH] flow_dissector: avoid uninitialized variable access

2016-10-21 Thread Linus Torvalds
On Fri, Oct 21, 2016 at 9:31 AM, Jiri Pirko wrote: > > I don't see how vlan could be used uninitialized. But I understand that > this is impossible for gcc to track it. Please just use uninitialized_var() Actually, I think we should never use "uninitialized_var()" except

Re: [PATCH] flow_dissector: avoid uninitialized variable access

2016-10-21 Thread Linus Torvalds
On Fri, Oct 21, 2016 at 9:31 AM, Jiri Pirko wrote: > > I don't see how vlan could be used uninitialized. But I understand that > this is impossible for gcc to track it. Please just use uninitialized_var() Actually, I think we should never use "uninitialized_var()" except possibly for arrays or

RE: [PATCH V2]usb: dwc2: Clear GUSBCFG.UsbTrdTim before setting

2016-10-21 Thread Lipengcheng
> -Original Message- > From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] > Sent: Monday, October 17, 2016 5:37 PM > To: Lipengcheng; johny...@synopsys.com > Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org; Xuejiancheng; Lidongpo;

RE: [PATCH V2]usb: dwc2: Clear GUSBCFG.UsbTrdTim before setting

2016-10-21 Thread Lipengcheng
> -Original Message- > From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] > Sent: Monday, October 17, 2016 5:37 PM > To: Lipengcheng; johny...@synopsys.com > Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org; Xuejiancheng; Lidongpo;

Re: [PATCH 00/12] Fix and update HOWTO Korean translation

2016-10-21 Thread SeongJae Park
On Sat, Oct 22, 2016 at 5:47 AM, Jonathan Corbet wrote: > On Sat, 22 Oct 2016 00:19:45 +0900 > SeongJae Park wrote: > >> This patchset applies ReST conversion effort for HOWTO document to its Korean >> translation. It also contains fixup of trivial nitpicks

Re: [PATCH 00/12] Fix and update HOWTO Korean translation

2016-10-21 Thread SeongJae Park
On Sat, Oct 22, 2016 at 5:47 AM, Jonathan Corbet wrote: > On Sat, 22 Oct 2016 00:19:45 +0900 > SeongJae Park wrote: > >> This patchset applies ReST conversion effort for HOWTO document to its Korean >> translation. It also contains fixup of trivial nitpicks in the document and >> the

[RFC][PATCH] cpufreq: intel_pstate: Use cpu load based algorithm for PM_MOBILE

2016-10-21 Thread Srinivas Pandruvada
Use get_target_pstate_use_cpu_load() to calculate target P-State for devices, which uses preferred power management profile as PM_MOBILE in ACPI FADT. This may help in resolving some thermal issues caused by low sustained cpu bound workloads. The current algorithm tend to over provision in this

[RFC][PATCH] cpufreq: intel_pstate: Use cpu load based algorithm for PM_MOBILE

2016-10-21 Thread Srinivas Pandruvada
Use get_target_pstate_use_cpu_load() to calculate target P-State for devices, which uses preferred power management profile as PM_MOBILE in ACPI FADT. This may help in resolving some thermal issues caused by low sustained cpu bound workloads. The current algorithm tend to over provision in this

Re: [PATCH] uapi: linux: acct: Remove redundant type comp2_t from kernel

2016-10-21 Thread Chen Gang
On 10/22/16 06:53, Chen Gang wrote: > > On 10/21/16 11:41, Andrew Morton wrote: >> On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote: >> >>> In api itself, kernel does not use it -- it is divided into ac_etime_hi >>> and ac_etime_lo. So kernel side only need generate the correct

Re: [PATCH] uapi: linux: acct: Remove redundant type comp2_t from kernel

2016-10-21 Thread Chen Gang
On 10/22/16 06:53, Chen Gang wrote: > > On 10/21/16 11:41, Andrew Morton wrote: >> On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote: >> >>> In api itself, kernel does not use it -- it is divided into ac_etime_hi >>> and ac_etime_lo. So kernel side only need generate the correct

Re: [RFC][PATCH 2/2] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220

2016-10-21 Thread Chen Yu
On 2016/10/22 4:00, John Youn wrote: > On 10/20/2016 5:43 PM, Chen Yu wrote: >> On 2016/10/19 6:21, John Youn wrote: >>> On 10/16/2016 7:42 PM, Chen Yu wrote: On 2016/10/15 3:37, John Youn wrote: > On 10/13/2016 4:36 PM, John Stultz wrote: >> From: Chen Yu

Re: [RFC][PATCH 2/2] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220

2016-10-21 Thread Chen Yu
On 2016/10/22 4:00, John Youn wrote: > On 10/20/2016 5:43 PM, Chen Yu wrote: >> On 2016/10/19 6:21, John Youn wrote: >>> On 10/16/2016 7:42 PM, Chen Yu wrote: On 2016/10/15 3:37, John Youn wrote: > On 10/13/2016 4:36 PM, John Stultz wrote: >> From: Chen Yu >> >> The

Re: [PATCH 1/2] net: phy: broadcom: Update Auxiliary Control Register macros

2016-10-21 Thread Joel Stanley
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote: > Add the RXD-to-RXC skew (delay) time bit in the Miscellaneous Control > shadow register and a mask for the shadow selector field. > > Remove a re-definition of MII_BCM54XX_AUXCTL_SHDWSEL_AUXCTL. > > Signed-off-by: Xo Wang

Re: [PATCH 1/2] net: phy: broadcom: Update Auxiliary Control Register macros

2016-10-21 Thread Joel Stanley
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote: > Add the RXD-to-RXC skew (delay) time bit in the Miscellaneous Control > shadow register and a mask for the shadow selector field. > > Remove a re-definition of MII_BCM54XX_AUXCTL_SHDWSEL_AUXCTL. > > Signed-off-by: Xo Wang Reviewed-by: Joel

Re: [PATCH 2/2] net: phy: broadcom: Add support for BCM54612E

2016-10-21 Thread Joel Stanley
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote: > This PHY has internal delays enabled after reset. This clears the > internal delay enables unless the interface specifically requests them. > > Signed-off-by: Xo Wang Reviewed-by: Joel Stanley

Re: [PATCH 2/2] net: phy: broadcom: Add support for BCM54612E

2016-10-21 Thread Joel Stanley
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote: > This PHY has internal delays enabled after reset. This clears the > internal delay enables unless the interface specifically requests them. > > Signed-off-by: Xo Wang Reviewed-by: Joel Stanley Cheers, Joel > --- > drivers/net/phy/broadcom.c

[PATCH] x86/cpufeatures: Enable new AVX512 cpu features

2016-10-21 Thread Gayatri Kammela
Modify cpufeatures.h to add new AVX512 instruction groups/features for enuermation in /proc/cpuinfo: AVX512IFMA and AVX512VBMI Also modify the xstate.c to clear the flags in fpu__xstate_clear_all_cpu_caps(). CPUID.(EAX=7,ECX=0):EBX[bit 21] AVX512IFMA CPUID.(Eax=7,ECX=0):ECX[bit 1] AVX512VBMI

[PATCH] x86/cpufeatures: Enable new AVX512 cpu features

2016-10-21 Thread Gayatri Kammela
Modify cpufeatures.h to add new AVX512 instruction groups/features for enuermation in /proc/cpuinfo: AVX512IFMA and AVX512VBMI Also modify the xstate.c to clear the flags in fpu__xstate_clear_all_cpu_caps(). CPUID.(EAX=7,ECX=0):EBX[bit 21] AVX512IFMA CPUID.(Eax=7,ECX=0):ECX[bit 1] AVX512VBMI

Re: [tip:x86/asm] x86/mm/64: Enable vmapped stacks (CONFIG_HAVE_ARCH_VMAP_STACK=y)

2016-10-21 Thread Andy Lutomirski
On Oct 21, 2016 5:32 AM, "Matt Fleming" wrote: > > On Wed, 24 Aug, at 06:03:04AM, tip-bot for Andy Lutomirski wrote: > > Commit-ID: e37e43a497d5a8b7c0cc1736d56986f432c394c9 > > Gitweb: > > http://git.kernel.org/tip/e37e43a497d5a8b7c0cc1736d56986f432c394c9 > >

Re: [tip:x86/asm] x86/mm/64: Enable vmapped stacks (CONFIG_HAVE_ARCH_VMAP_STACK=y)

2016-10-21 Thread Andy Lutomirski
On Oct 21, 2016 5:32 AM, "Matt Fleming" wrote: > > On Wed, 24 Aug, at 06:03:04AM, tip-bot for Andy Lutomirski wrote: > > Commit-ID: e37e43a497d5a8b7c0cc1736d56986f432c394c9 > > Gitweb: > > http://git.kernel.org/tip/e37e43a497d5a8b7c0cc1736d56986f432c394c9 > > Author: Andy Lutomirski >

Re: [PATCH 2/5] stop_machine: yield CPU during stop machine

2016-10-21 Thread Nicholas Piggin
On Fri, 21 Oct 2016 14:05:36 +0200 Peter Zijlstra wrote: > On Fri, Oct 21, 2016 at 01:58:55PM +0200, Christian Borntraeger wrote: > > stop_machine can take a very long time if the hypervisor does > > overcommitment for guest CPUs. When waiting for "the one", lets > > give

Re: [PATCH 2/5] stop_machine: yield CPU during stop machine

2016-10-21 Thread Nicholas Piggin
On Fri, 21 Oct 2016 14:05:36 +0200 Peter Zijlstra wrote: > On Fri, Oct 21, 2016 at 01:58:55PM +0200, Christian Borntraeger wrote: > > stop_machine can take a very long time if the hypervisor does > > overcommitment for guest CPUs. When waiting for "the one", lets > > give up our CPU by using the

Re: [RFC][PATCH] Add EXPORT_MACRO_SYMBOL() for asm

2016-10-21 Thread Nicholas Piggin
On Fri, 21 Oct 2016 12:17:59 -0400 Steven Rostedt wrote: > Commit 784d5699eddc5 ("x86: move exports to actual definitions") removed the > EXPORT_SYMBOL(__fentry__) and EXPORT_SYMBOL(mcount) from x8664_ksyms_64.c, > and added EXPORT_SYMBOL(function_hook) in mcount_64.S

Re: [RFC][PATCH] Add EXPORT_MACRO_SYMBOL() for asm

2016-10-21 Thread Nicholas Piggin
On Fri, 21 Oct 2016 12:17:59 -0400 Steven Rostedt wrote: > Commit 784d5699eddc5 ("x86: move exports to actual definitions") removed the > EXPORT_SYMBOL(__fentry__) and EXPORT_SYMBOL(mcount) from x8664_ksyms_64.c, > and added EXPORT_SYMBOL(function_hook) in mcount_64.S instead. The problem > is

Re: [PATCH] shmem: avoid huge pages for small files

2016-10-21 Thread Kirill A. Shutemov
On Sat, Oct 22, 2016 at 09:50:13AM +1100, Dave Chinner wrote: > On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote: > > On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote: > > > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote: > > > > > Ugh, no, please don't

Re: [PATCH] shmem: avoid huge pages for small files

2016-10-21 Thread Kirill A. Shutemov
On Sat, Oct 22, 2016 at 09:50:13AM +1100, Dave Chinner wrote: > On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote: > > On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote: > > > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote: > > > > > Ugh, no, please don't

Re: [PATCH v2] mailbox: PCC: Fix lockdep warning when request PCC channel

2016-10-21 Thread Hoan Tran
Hi Prashanth, On Fri, Oct 21, 2016 at 9:13 AM, Prakash, Prashanth wrote: > Hi Hoan, > > On 10/18/2016 1:00 AM, Hoan Tran wrote: >> This patch fixes the lockdep warning below >> >> [7.229767] DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags)) >> [7.229776]

Re: [PATCH v2] mailbox: PCC: Fix lockdep warning when request PCC channel

2016-10-21 Thread Hoan Tran
Hi Prashanth, On Fri, Oct 21, 2016 at 9:13 AM, Prakash, Prashanth wrote: > Hi Hoan, > > On 10/18/2016 1:00 AM, Hoan Tran wrote: >> This patch fixes the lockdep warning below >> >> [7.229767] DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags)) >> [7.229776] [ cut here

[PATCH v3 3/4] arm64: dts: msm8996: Add SMEM DT nodes

2016-10-21 Thread Sarangdhar Joshi
From: Bjorn Andersson Add SMEM and TCSR DT nodes on MSM8996. Signed-off-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 17 + 1 file changed, 17

Re: 4.9-rc1 boot regression, ambiguous bisect result

2016-10-21 Thread Dan Williams
On Fri, Oct 21, 2016 at 1:20 PM, Matt Fleming wrote: > On Fri, 21 Oct, at 04:41:29PM, Matt Fleming wrote: >> >> FYI, I've been able to reproduce some crash when using your EFI memory >> map layout under Qemu and forcing the ESRT driver to reserve the space. > > Nope,

[PATCH v3 3/4] arm64: dts: msm8996: Add SMEM DT nodes

2016-10-21 Thread Sarangdhar Joshi
From: Bjorn Andersson Add SMEM and TCSR DT nodes on MSM8996. Signed-off-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 17 + 1 file changed, 17 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi

Re: 4.9-rc1 boot regression, ambiguous bisect result

2016-10-21 Thread Dan Williams
On Fri, Oct 21, 2016 at 1:20 PM, Matt Fleming wrote: > On Fri, 21 Oct, at 04:41:29PM, Matt Fleming wrote: >> >> FYI, I've been able to reproduce some crash when using your EFI memory >> map layout under Qemu and forcing the ESRT driver to reserve the space. > > Nope, that was a bug in my hack. I

[PATCH v3 2/4] arm64: dts: msm8996: Add reserve-memory nodes

2016-10-21 Thread Sarangdhar Joshi
Add reserve-memory nodes required for Qualcomm Peripheral Image Loaders Acked-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 25 + 1 file changed, 25 insertions(+) diff

[PATCH v3 1/4] arm64: dts: msm8996: Add SMEM reserve-memory node

2016-10-21 Thread Sarangdhar Joshi
Add DT node to carveout memory for shared memory region. Reviewed-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH v3 2/4] arm64: dts: msm8996: Add reserve-memory nodes

2016-10-21 Thread Sarangdhar Joshi
Add reserve-memory nodes required for Qualcomm Peripheral Image Loaders Acked-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 25 + 1 file changed, 25 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi

[PATCH v3 1/4] arm64: dts: msm8996: Add SMEM reserve-memory node

2016-10-21 Thread Sarangdhar Joshi
Add DT node to carveout memory for shared memory region. Reviewed-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi

[PATCH v3 4/4] arm64: dts: msm8996: Add SMP2P and APCS nodes

2016-10-21 Thread Sarangdhar Joshi
Add SMP2P and APCS DT nodes required for Qualcomm ADSP Peripheral Image Loader. Acked-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 29 + 1 file changed, 29

[PATCH v3 4/4] arm64: dts: msm8996: Add SMP2P and APCS nodes

2016-10-21 Thread Sarangdhar Joshi
Add SMP2P and APCS DT nodes required for Qualcomm ADSP Peripheral Image Loader. Acked-by: Bjorn Andersson Signed-off-by: Sarangdhar Joshi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 29 + 1 file changed, 29 insertions(+) diff --git

[PATCH v3 0/4] MSM8996 DT Support for ADSP PIL

2016-10-21 Thread Sarangdhar Joshi
Add various device tree nodes to lay the groundwork for Qualcomm ADSP Peripheral Image Loader. Sorry, I didn't send any cover letter for v1. Changes since v2: - Remove empty lines from smem DT node (Stephen) Changes since v1: - Move hwlock DT node under root (/) (Bjorn and Andy) - Rename

[PATCH v3 0/4] MSM8996 DT Support for ADSP PIL

2016-10-21 Thread Sarangdhar Joshi
Add various device tree nodes to lay the groundwork for Qualcomm ADSP Peripheral Image Loader. Sorry, I didn't send any cover letter for v1. Changes since v2: - Remove empty lines from smem DT node (Stephen) Changes since v1: - Move hwlock DT node under root (/) (Bjorn and Andy) - Rename

Re: [PATCH] remoteproc: Add support for xo clock

2016-10-21 Thread Sarangdhar Joshi
On 10/20/2016 04:54 PM, Stephen Boyd wrote: On 10/20, Sarangdhar Joshi wrote: Add xo clock support required for Qualcomm ADSP Peripheral Image Loader. Yes but why is xo needed? It is required to boot up the ADSP processor. The remoteproc driver keeps the xo clock enabled until the driver

Re: [PATCH] remoteproc: Add support for xo clock

2016-10-21 Thread Sarangdhar Joshi
On 10/20/2016 04:54 PM, Stephen Boyd wrote: On 10/20, Sarangdhar Joshi wrote: Add xo clock support required for Qualcomm ADSP Peripheral Image Loader. Yes but why is xo needed? It is required to boot up the ADSP processor. The remoteproc driver keeps the xo clock enabled until the driver

[PATCH v2] debug: More properly delay for secondary CPUs

2016-10-21 Thread Douglas Anderson
We've got a delay loop waiting for secondary CPUs. That loop uses loops_per_jiffy. However, loops_per_jiffy doesn't actually mean how many tight loops make up a jiffy on all architectures. It is quite common to see things like this in the boot log: Calibrating delay loop (skipped), value

[PATCH v2] debug: More properly delay for secondary CPUs

2016-10-21 Thread Douglas Anderson
We've got a delay loop waiting for secondary CPUs. That loop uses loops_per_jiffy. However, loops_per_jiffy doesn't actually mean how many tight loops make up a jiffy on all architectures. It is quite common to see things like this in the boot log: Calibrating delay loop (skipped), value

Re: [PATCH] pinctrl: qcom: Add msm8994 pinctrl driver

2016-10-21 Thread Jeremy McNicoll
On Fri, Oct 21, 2016 at 03:42:50PM -0700, Michael Scott wrote: > Initial pinctrl driver for QCOM msm8994 platforms. > > In order to continue the initial board support for QCOM msm8994/msm8992 > presented in patches from Jeremy McNicoll , let's put > a proper pinctrl driver in

Re: [PATCH] pinctrl: qcom: Add msm8994 pinctrl driver

2016-10-21 Thread Jeremy McNicoll
On Fri, Oct 21, 2016 at 03:42:50PM -0700, Michael Scott wrote: > Initial pinctrl driver for QCOM msm8994 platforms. > > In order to continue the initial board support for QCOM msm8994/msm8992 > presented in patches from Jeremy McNicoll , let's put > a proper pinctrl driver in place. > >

[PATCH] MAINTAINERS: add drivers/pinctrl/qcom to ARM/QUALCOMM SUPPORT

2016-10-21 Thread Michael Scott
When running checkpatch.pl on a new pinctrl driver in drivers/pinctrl/qcom, I noticed a warning about creating a new maintainer. The drivers/pinctrl/qcom folder doesn't have anyone assigned in the MAINTAINERS file. Let's assign it to ARM/QUALCOMM SUPPORT. Signed-off-by: Michael Scott

[PATCH] MAINTAINERS: add drivers/pinctrl/qcom to ARM/QUALCOMM SUPPORT

2016-10-21 Thread Michael Scott
When running checkpatch.pl on a new pinctrl driver in drivers/pinctrl/qcom, I noticed a warning about creating a new maintainer. The drivers/pinctrl/qcom folder doesn't have anyone assigned in the MAINTAINERS file. Let's assign it to ARM/QUALCOMM SUPPORT. Signed-off-by: Michael Scott ---

Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix

2016-10-21 Thread Borislav Petkov
On Sat, Oct 22, 2016 at 12:51:32AM +0300, sonofa...@openmailbox.org wrote: > Thank you for your time! I have chosen reply to list and all recipients, it > must work now. Yes, exactly what I had in mind. > My brother rejected the proposed patch because it does not provide > equivalent

Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix

2016-10-21 Thread Borislav Petkov
On Sat, Oct 22, 2016 at 12:51:32AM +0300, sonofa...@openmailbox.org wrote: > Thank you for your time! I have chosen reply to list and all recipients, it > must work now. Yes, exactly what I had in mind. > My brother rejected the proposed patch because it does not provide > equivalent

Re: [RFC] put more pressure on proc/sysfs slab shrink

2016-10-21 Thread Dave Chinner
On Fri, Oct 21, 2016 at 01:35:14PM -0700, Shaohua Li wrote: > In our systems, proc/sysfs inode/dentry cache use more than 1G memory > even memory pressure is high sometimes. Since proc/sysfs is in-memory > filesystem, rebuilding the cache is fast. There is no point proc/sysfs > and disk fs have

Re: [RFC] put more pressure on proc/sysfs slab shrink

2016-10-21 Thread Dave Chinner
On Fri, Oct 21, 2016 at 01:35:14PM -0700, Shaohua Li wrote: > In our systems, proc/sysfs inode/dentry cache use more than 1G memory > even memory pressure is high sometimes. Since proc/sysfs is in-memory > filesystem, rebuilding the cache is fast. There is no point proc/sysfs > and disk fs have

Re: [PATCH v4 4/9] clk: sunxi-ng: Add minimums for all the relevant structures and clocks

2016-10-21 Thread André Przywara
Salut, On 11/10/16 15:28, Maxime Ripard wrote: > Modify the current clocks we have to be able to specify the minimum for > each clocks we support, just like we support the max. > > Signed-off-by: Maxime Ripard > --- > drivers/clk/sunxi-ng/ccu_mult.c | 7

Re: [PATCH v4 4/9] clk: sunxi-ng: Add minimums for all the relevant structures and clocks

2016-10-21 Thread André Przywara
Salut, On 11/10/16 15:28, Maxime Ripard wrote: > Modify the current clocks we have to be able to specify the minimum for > each clocks we support, just like we support the max. > > Signed-off-by: Maxime Ripard > --- > drivers/clk/sunxi-ng/ccu_mult.c | 7 ++- >

Re: [PATCH] uapi: linux: acct: Remove redundant type comp2_t from kernel

2016-10-21 Thread Chen Gang
On 10/21/16 11:41, Andrew Morton wrote: > On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote: > >> In api itself, kernel does not use it -- it is divided into ac_etime_hi >> and ac_etime_lo. So kernel side only need generate the correct >> ac_etime_hi and ac_etime_lo, but need

Re: [PATCH] uapi: linux: acct: Remove redundant type comp2_t from kernel

2016-10-21 Thread Chen Gang
On 10/21/16 11:41, Andrew Morton wrote: > On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote: > >> In api itself, kernel does not use it -- it is divided into ac_etime_hi >> and ac_etime_lo. So kernel side only need generate the correct >> ac_etime_hi and ac_etime_lo, but need

Re: [PATCH] shmem: avoid huge pages for small files

2016-10-21 Thread Dave Chinner
On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote: > On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote: > > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote: > > > > Ugh, no, please don't use mount options for file specific behaviours > > > > in filesystems

Re: [PATCH] shmem: avoid huge pages for small files

2016-10-21 Thread Dave Chinner
On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote: > On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote: > > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote: > > > > Ugh, no, please don't use mount options for file specific behaviours > > > > in filesystems

Re: [PATCHv4] shmem: avoid huge pages for small files

2016-10-21 Thread Kirill A. Shutemov
On Fri, Oct 21, 2016 at 09:51:03PM +0300, Kirill A. Shutemov wrote: > + case SHEME_HUGE_ALWAYS: Oops. Forgot to commit the fixup :-/ >From 79b0a3bf4503225d0e6ba553b8496f0c4d55514e Mon Sep 17 00:00:00 2001 From: "Kirill A. Shutemov" Date: Mon, 17 Oct

Re: [PATCHv4] shmem: avoid huge pages for small files

2016-10-21 Thread Kirill A. Shutemov
On Fri, Oct 21, 2016 at 09:51:03PM +0300, Kirill A. Shutemov wrote: > + case SHEME_HUGE_ALWAYS: Oops. Forgot to commit the fixup :-/ >From 79b0a3bf4503225d0e6ba553b8496f0c4d55514e Mon Sep 17 00:00:00 2001 From: "Kirill A. Shutemov" Date: Mon, 17 Oct 2016 14:44:47 +0300 Subject:

[PATCH] pinctrl: qcom: Add msm8994 pinctrl driver

2016-10-21 Thread Michael Scott
Initial pinctrl driver for QCOM msm8994 platforms. In order to continue the initial board support for QCOM msm8994/msm8992 presented in patches from Jeremy McNicoll , let's put a proper pinctrl driver in place. Currently, the DT for these platforms uses the msm8x74 pinctrl

[PATCH] pinctrl: qcom: Add msm8994 pinctrl driver

2016-10-21 Thread Michael Scott
Initial pinctrl driver for QCOM msm8994 platforms. In order to continue the initial board support for QCOM msm8994/msm8992 presented in patches from Jeremy McNicoll , let's put a proper pinctrl driver in place. Currently, the DT for these platforms uses the msm8x74 pinctrl driver to enable basic

Re: [PATCH 1/2] pinctrl: pm8994: add pad voltage regulator defines

2016-10-21 Thread Andy Gross
On Sun, Sep 18, 2016 at 01:38:30PM +0200, Linus Walleij wrote: > On Fri, Sep 16, 2016 at 7:41 PM, Srinivas Kandagatla > wrote: > > > This patch adds defines for internal voltage regulators used > > to switch voltage levels on gpio/mpp pads. > > > > Signed-off-by:

Re: [PATCH 1/2] pinctrl: pm8994: add pad voltage regulator defines

2016-10-21 Thread Andy Gross
On Sun, Sep 18, 2016 at 01:38:30PM +0200, Linus Walleij wrote: > On Fri, Sep 16, 2016 at 7:41 PM, Srinivas Kandagatla > wrote: > > > This patch adds defines for internal voltage regulators used > > to switch voltage levels on gpio/mpp pads. > > > > Signed-off-by: Srinivas Kandagatla > >

[GIT PULL] Please pull powerpc/linux.git powerpc-4.9-3 tag

2016-10-21 Thread Michael Ellerman
Hi Linus, Please pull some more powerpc fixes for 4.9: The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git

[GIT PULL] Please pull powerpc/linux.git powerpc-4.9-3 tag

2016-10-21 Thread Michael Ellerman
Hi Linus, Please pull some more powerpc fixes for 4.9: The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git

Re: [PATCH 26/26] ubifs: Raise write version to 5

2016-10-21 Thread Theodore Ts'o
On Fri, Oct 21, 2016 at 11:19:31AM -0700, Eric Biggers wrote: > > I don't think it's reasonable to require require changes to filesystems > whenever > someone introduces a new encryption mode --- contents, filenames, or both. > Filesystems need to be able to handle unsupported encryption modes

Re: [PATCH 26/26] ubifs: Raise write version to 5

2016-10-21 Thread Theodore Ts'o
On Fri, Oct 21, 2016 at 11:19:31AM -0700, Eric Biggers wrote: > > I don't think it's reasonable to require require changes to filesystems > whenever > someone introduces a new encryption mode --- contents, filenames, or both. > Filesystems need to be able to handle unsupported encryption modes

  1   2   3   4   5   6   7   8   9   10   >