[RFC tip/locking/lockdep v5 12/17] lockdep/selftest: Unleash irq_read_recursion2 and add more

Now since we can handle recursive read related irq inversion deadlocks correctly, uncomment the irq_read_recursion2 and add more testcases. Signed-off-by: Boqun Feng --- lib/locking-selftest.c | 59 -- 1 file changed, 47

[RFC tip/locking/lockdep v5 10/17] lockdep/selftest: Add a R-L/L-W test case specific to chain cache behavior

As our chain cache doesn't differ read/write locks, so even we can detect a read-lock/lock-write deadlock in check_noncircular(), we can still be fooled if a read-lock/lock-read case(which is not a deadlock) comes first. So introduce this test case to test specific to the chain cache behavior on

[RFC tip/locking/lockdep v5 09/17] lockdep: Add recursive read locks into dependency graph

Since we have all the fundamental to handle recursive read locks, we now add them into the dependency graph. Signed-off-by: Boqun Feng --- kernel/locking/lockdep.c | 16 +--- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/kernel/locking/lockdep.c

[RFC tip/locking/lockdep v5 14/17] Revert "locking/lockdep/selftests: Fix mixed read-write ABBA tests"

This reverts commit d82fed75294229abc9d757f08a4817febae6c4f4. Since we now could handle mixed read-write deadlock detection well, the self tests could be detected as expected, no need to use this work-around. Signed-off-by: Boqun Feng --- lib/locking-selftest.c | 8

[RFC tip/locking/lockdep v5 12/17] lockdep/selftest: Unleash irq_read_recursion2 and add more

Now since we can handle recursive read related irq inversion deadlocks correctly, uncomment the irq_read_recursion2 and add more testcases. Signed-off-by: Boqun Feng --- lib/locking-selftest.c | 59 -- 1 file changed, 47 insertions(+), 12

[RFC tip/locking/lockdep v5 10/17] lockdep/selftest: Add a R-L/L-W test case specific to chain cache behavior

As our chain cache doesn't differ read/write locks, so even we can detect a read-lock/lock-write deadlock in check_noncircular(), we can still be fooled if a read-lock/lock-read case(which is not a deadlock) comes first. So introduce this test case to test specific to the chain cache behavior on

[RFC tip/locking/lockdep v5 14/17] Revert "locking/lockdep/selftests: Fix mixed read-write ABBA tests"

This reverts commit d82fed75294229abc9d757f08a4817febae6c4f4. Since we now could handle mixed read-write deadlock detection well, the self tests could be detected as expected, no need to use this work-around. Signed-off-by: Boqun Feng --- lib/locking-selftest.c | 8 1 file changed, 8

[RFC tip/locking/lockdep v5 09/17] lockdep: Add recursive read locks into dependency graph

Since we have all the fundamental to handle recursive read locks, we now add them into the dependency graph. Signed-off-by: Boqun Feng --- kernel/locking/lockdep.c | 16 +--- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/kernel/locking/lockdep.c

[RFC tip/locking/lockdep v5 11/17] lockdep: Take read/write status in consideration when generate chainkey

Currently, the chainkey of a lock chain is a hash sum of the class_idx of all the held locks, the read/write status are not taken in to consideration while generating the chainkey. This could result into a problem, if we have: P1() { read_lock(B);

[RFC tip/locking/lockdep v5 03/17] lockdep: Redefine LOCK_*_STATE* bits

There are three types of lock acquisitions: write, non-recursive read and recursive read, among which write locks and non-recursive read locks have no difference from a viewpoint for deadlock detections, because a write acquisition of the corresponding lock on an independent CPU or task makes a

[RFC tip/locking/lockdep v5 11/17] lockdep: Take read/write status in consideration when generate chainkey

Currently, the chainkey of a lock chain is a hash sum of the class_idx of all the held locks, the read/write status are not taken in to consideration while generating the chainkey. This could result into a problem, if we have: P1() { read_lock(B);

[RFC tip/locking/lockdep v5 03/17] lockdep: Redefine LOCK_*_STATE* bits

There are three types of lock acquisitions: write, non-recursive read and recursive read, among which write locks and non-recursive read locks have no difference from a viewpoint for deadlock detections, because a write acquisition of the corresponding lock on an independent CPU or task makes a

[RFC tip/locking/lockdep v5 00/17] lockdep: Support deadlock detection for recursive read locks

Hi Ingo and Peter, This is V5 for recursive read lock support in lockdep. The changes since V4 are quite trivial: * Fix some wording issues in patch #16 as pointed out by Randy Dunlap I added the explanation about reasoning in patch #16 in V4, which will help understand this whole

[RFC tip/locking/lockdep v5 00/17] lockdep: Support deadlock detection for recursive read locks

Hi Ingo and Peter, This is V5 for recursive read lock support in lockdep. The changes since V4 are quite trivial: * Fix some wording issues in patch #16 as pointed out by Randy Dunlap I added the explanation about reasoning in patch #16 in V4, which will help understand this whole

Re: [PATCH v2 1/8] [PATCH 1/8] drivers/peci: Add support for PECI bus driver core

Hi Jae, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.16-rc2 next-20180221] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

[RFC PATCH] drivers/peci: peci_match_id() can be static

Fixes: 99f5d2b99ecd ("drivers/peci: Add support for PECI bus driver core") Signed-off-by: Fengguang Wu --- peci-core.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/peci/peci-core.c b/drivers/peci/peci-core.c index d976c73..4709b8c

[RFC PATCH] drivers/peci: peci_match_id() can be static

Fixes: 99f5d2b99ecd ("drivers/peci: Add support for PECI bus driver core") Signed-off-by: Fengguang Wu --- peci-core.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/peci/peci-core.c b/drivers/peci/peci-core.c index d976c73..4709b8c 100644 ---

Re: [PATCH v2 1/8] [PATCH 1/8] drivers/peci: Add support for PECI bus driver core

Hi Jae, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.16-rc2 next-20180221] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: Use higher-order pages in vmalloc

On Wed 21-02-18 09:01:29, Matthew Wilcox wrote: > On Wed, Feb 21, 2018 at 08:16:22AM -0800, Dave Hansen wrote: > > On 02/21/2018 07:42 AM, Matthew Wilcox wrote: > > > This prompted me to write a patch I've been meaning to do for a while, > > > allocating large pages if they're available to satisfy

Re: Use higher-order pages in vmalloc

On Wed 21-02-18 09:01:29, Matthew Wilcox wrote: > On Wed, Feb 21, 2018 at 08:16:22AM -0800, Dave Hansen wrote: > > On 02/21/2018 07:42 AM, Matthew Wilcox wrote: > > > This prompted me to write a patch I've been meaning to do for a while, > > > allocating large pages if they're available to satisfy

Re: [PATCH 4.9 34/77] powerpc: fix build errors in stable tree

On Thu, Feb 22, 2018 at 12:01:21PM +1100, Michael Ellerman wrote: > Greg Kroah-Hartman writes: > > > 4.9-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Nicholas Piggin > > > > This

Re: [PATCH 4.9 34/77] powerpc: fix build errors in stable tree

On Thu, Feb 22, 2018 at 12:01:21PM +1100, Michael Ellerman wrote: > Greg Kroah-Hartman writes: > > > 4.9-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Nicholas Piggin > > > > This is just the first chunk of commit > >

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On Wed, Feb 21, 2018 at 09:42:08PM -0800, Daniel Lustig wrote: > On 2/21/2018 9:27 PM, Boqun Feng wrote: > > On Wed, Feb 21, 2018 at 08:13:57PM -0800, Paul E. McKenney wrote: > >> On Thu, Feb 22, 2018 at 11:23:49AM +0800, Boqun Feng wrote: > >>> On Tue, Feb 20, 2018 at 03:25:10PM -0800, Paul E.

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On Wed, Feb 21, 2018 at 09:42:08PM -0800, Daniel Lustig wrote: > On 2/21/2018 9:27 PM, Boqun Feng wrote: > > On Wed, Feb 21, 2018 at 08:13:57PM -0800, Paul E. McKenney wrote: > >> On Thu, Feb 22, 2018 at 11:23:49AM +0800, Boqun Feng wrote: > >>> On Tue, Feb 20, 2018 at 03:25:10PM -0800, Paul E.

Re: [PATCH v2 1/8] [PATCH 1/8] drivers/peci: Add support for PECI bus driver core

On Wed, Feb 21, 2018 at 12:42:30PM -0800, Jae Hyun Yoo wrote: > On 2/21/2018 9:58 AM, Greg KH wrote: > > On Wed, Feb 21, 2018 at 08:15:59AM -0800, Jae Hyun Yoo wrote: > > > This commit adds driver implementation for PECI bus into linux > > > driver framework. > > > > > > Signed-off-by: Jae Hyun

Re: [PATCH v2 1/8] [PATCH 1/8] drivers/peci: Add support for PECI bus driver core

On Wed, Feb 21, 2018 at 12:42:30PM -0800, Jae Hyun Yoo wrote: > On 2/21/2018 9:58 AM, Greg KH wrote: > > On Wed, Feb 21, 2018 at 08:15:59AM -0800, Jae Hyun Yoo wrote: > > > This commit adds driver implementation for PECI bus into linux > > > driver framework. > > > > > > Signed-off-by: Jae Hyun

[PATCH] srcu: remove never used variable

From: Zhouyi Zhou In function srcu_gp_end, the variable idxnext is never used after assign, remove it and its assign statement. Signed-off-by: Zhouyi Zhou --- kernel/rcu/srcutree.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH] srcu: remove never used variable

From: Zhouyi Zhou In function srcu_gp_end, the variable idxnext is never used after assign, remove it and its assign statement. Signed-off-by: Zhouyi Zhou --- kernel/rcu/srcutree.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c index

Re: [PATCH v2 01/17] tracing: probeevent: Fix to support minus offset from symbol

On Wed, 21 Feb 2018 20:53:41 -0500 Steven Rostedt wrote: > On Thu, 22 Feb 2018 08:41:53 +0900 > Masami Hiramatsu wrote: > > > Hi Steve, > > > > Could you pick this separately since this is a bugfix? > > > > Yes definitely. I'll have to run my tests

Re: [PATCH v2 01/17] tracing: probeevent: Fix to support minus offset from symbol

On Wed, 21 Feb 2018 20:53:41 -0500 Steven Rostedt wrote: > On Thu, 22 Feb 2018 08:41:53 +0900 > Masami Hiramatsu wrote: > > > Hi Steve, > > > > Could you pick this separately since this is a bugfix? > > > > Yes definitely. I'll have to run my tests on it too, and I'll send it > as urgent

[v2 0/3] Patches to address some limitations in OS microcode loading.

Patch series to address limitations of OS microcode loading. Review comments from Boris: Changes since v1: Patch 1/3 - Check for revision to avoid duplicate microcode load in early load - Added inline comments. Changes since v1: Patch 2/3 - Change to native_wbinvd for early load. Changes since

[v2 0/3] Patches to address some limitations in OS microcode loading.

Patch series to address limitations of OS microcode loading. Review comments from Boris: Changes since v1: Patch 1/3 - Check for revision to avoid duplicate microcode load in early load - Added inline comments. Changes since v1: Patch 2/3 - Change to native_wbinvd for early load. Changes since

[v2 2/3] x86/microcode/intel: Perform a cache flush before ucode update.

Microcode updates can be safer if the caches are clean. Some of the issues around in certain Broadwell parts can be addressed by doing a full cache flush. Signed-off-by: Ashok Raj Cc: X86 ML Cc: LKML Cc: Thomas Gleixner

[v2 2/3] x86/microcode/intel: Perform a cache flush before ucode update.

Microcode updates can be safer if the caches are clean. Some of the issues around in certain Broadwell parts can be addressed by doing a full cache flush. Signed-off-by: Ashok Raj Cc: X86 ML Cc: LKML Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Tony Luck Cc: Andi Kleen Cc: Boris Petkov Cc: Tom

[v2 3/3] x86/microcode: Quiesce all threads before a microcode update.

Microcode updates during OS load always assumed the other hyper-thread was "quiet", but Linux never really did this. We've recently received several issues on this, where things did not go well at scale deployments, and the Intel microcode team asked us to make sure the system is in a quiet state

[v2 3/3] x86/microcode: Quiesce all threads before a microcode update.

Microcode updates during OS load always assumed the other hyper-thread was "quiet", but Linux never really did this. We've recently received several issues on this, where things did not go well at scale deployments, and the Intel microcode team asked us to make sure the system is in a quiet state

[v2 1/3] x86/microcode/intel: Check microcode revision before updating sibling threads

After updating microcode on one of the threads in the core, the thread sibling automatically gets the update since the microcode resources are shared. Check the ucode revision on the CPU before performing a ucode update. Signed-off-by: Ashok Raj Cc: X86 ML

[v2 1/3] x86/microcode/intel: Check microcode revision before updating sibling threads

After updating microcode on one of the threads in the core, the thread sibling automatically gets the update since the microcode resources are shared. Check the ucode revision on the CPU before performing a ucode update. Signed-off-by: Ashok Raj Cc: X86 ML Cc: LKML Cc: Thomas Gleixner Cc:

[PATCH net v2 1/2] Revert "tuntap: add missing xdp flush"

This reverts commit 762c330d670e3d4b795cf7a8d761866fdd1eef49. The reason is we try to batch packets for devmap which causes calling xdp_do_flush() under the process context. Simply disable premmption may not work since process may move among processors which lead xdp_do_flush() to miss some

[PATCH net v2 2/2] tuntap: correctly add the missing xdp flush

Commit 762c330d670e ("tuntap: add missing xdp flush") tries to fix the devmap stall caused by missed xdp flush by counting the pending xdp redirected packets and flush when it exceeds NAPI_POLL_WEIGHT or MSG_MORE is clear. This may lead BUG() since xdp_do_flush() was called under process context

[PATCH net v2 1/2] Revert "tuntap: add missing xdp flush"

This reverts commit 762c330d670e3d4b795cf7a8d761866fdd1eef49. The reason is we try to batch packets for devmap which causes calling xdp_do_flush() under the process context. Simply disable premmption may not work since process may move among processors which lead xdp_do_flush() to miss some

[PATCH net v2 2/2] tuntap: correctly add the missing xdp flush

Commit 762c330d670e ("tuntap: add missing xdp flush") tries to fix the devmap stall caused by missed xdp flush by counting the pending xdp redirected packets and flush when it exceeds NAPI_POLL_WEIGHT or MSG_MORE is clear. This may lead BUG() since xdp_do_flush() was called under process context

[PATCH ipmi/kcs_bmc v4] ipmi: kcs_bmc: make the code be more clean

Modify the file read and write operation API's parameter declaration to meet the name convention. Rename the helper function by following the to_() name style. Update the poll API with the new type '__poll_t', this is new commit from linux-4.16-rc1. Correct the header file's comment style for

[PATCH ipmi/kcs_bmc v4] ipmi: kcs_bmc: make the code be more clean

Modify the file read and write operation API's parameter declaration to meet the name convention. Rename the helper function by following the to_() name style. Update the poll API with the new type '__poll_t', this is new commit from linux-4.16-rc1. Correct the header file's comment style for

Re: [PATCH v4 3/4] arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP

On 02/19/2018 10:06 PM, Marc Zyngier wrote: > On Fri, 16 Feb 2018 11:35:02 +0530 > Rajendra Nayak wrote: > >> Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files >> >> Signed-off-by: Rajendra Nayak >> Reviewed-by: Doug Anderson

Re: [PATCH v4 3/4] arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP

On 02/19/2018 10:06 PM, Marc Zyngier wrote: > On Fri, 16 Feb 2018 11:35:02 +0530 > Rajendra Nayak wrote: > >> Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files >> >> Signed-off-by: Rajendra Nayak >> Reviewed-by: Doug Anderson >> --- >> arch/arm64/boot/dts/qcom/Makefile | 1

Re: [PATCH] netlink: put module reference if dump start fails

Hi, On Wed, Feb 21, 2018 at 04:41:05PM +0100, Jason A. Donenfeld wrote: Fixes: 41c87425a1ac ("netlink: do not set cb_running if dump's start() errs") I think you Would better to resend it. Bo,

Re: [PATCH] netlink: put module reference if dump start fails

Hi, On Wed, Feb 21, 2018 at 04:41:05PM +0100, Jason A. Donenfeld wrote: Fixes: 41c87425a1ac ("netlink: do not set cb_running if dump's start() errs") I think you Would better to resend it. Bo,

Re: [PATCH v13 7/8] ARM: dts: imx: Add TDA19971 HDMI Receiver to GW54xx

On Thu, Feb 15, 2018 at 01:19:17PM -0800, Tim Harvey wrote: > On Thu, Feb 15, 2018 at 10:36 AM, Hans Verkuil wrote: > > On 15/02/18 18:55, Tim Harvey wrote: > >> The GW54xx has a front-panel microHDMI connector routed to a TDA19971 > >> which is connected the the IPU CSI when

[PATCH v5 2/4] dt-bindings: qcom: Add SDM845 bindings

Add a SoC string 'sdm845' for the qualcomm SDM845 SoC Signed-off-by: Rajendra Nayak Reviewed-by: Douglas Anderson Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/arm/qcom.txt | 1 + 1 file changed, 1 insertion(+)

Re: [PATCH v13 7/8] ARM: dts: imx: Add TDA19971 HDMI Receiver to GW54xx

On Thu, Feb 15, 2018 at 01:19:17PM -0800, Tim Harvey wrote: > On Thu, Feb 15, 2018 at 10:36 AM, Hans Verkuil wrote: > > On 15/02/18 18:55, Tim Harvey wrote: > >> The GW54xx has a front-panel microHDMI connector routed to a TDA19971 > >> which is connected the the IPU CSI when using IMX6Q. > > > >

[PATCH v5 2/4] dt-bindings: qcom: Add SDM845 bindings

Add a SoC string 'sdm845' for the qualcomm SDM845 SoC Signed-off-by: Rajendra Nayak Reviewed-by: Douglas Anderson Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/arm/qcom.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm/qcom.txt

Re: [PATCH v1] drm/simple_kms_helper: Fix NULL pointer dereference with no active CRTC

On 02/22/2018 08:09 AM, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko It is possible that drm_simple_kms_plane_atomic_check called with no CRTC set, e.g. when user-space application sets CRTC_ID/FB_ID to 0 before doing any actual drawing. This

Re: [PATCH v1] drm/simple_kms_helper: Fix NULL pointer dereference with no active CRTC

On 02/22/2018 08:09 AM, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko It is possible that drm_simple_kms_plane_atomic_check called with no CRTC set, e.g. when user-space application sets CRTC_ID/FB_ID to 0 before doing any actual drawing. This leads to NULL pointer dereference

[PATCH v5 4/4] arm64: dts: sdm845: Add serial console support

Add the qup uart node and geni se instance needed to support the serial console on the MTP. Signed-off-by: Rajendra Nayak --- arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 39 + arch/arm64/boot/dts/qcom/sdm845.dtsi| 39

[PATCH v5 4/4] arm64: dts: sdm845: Add serial console support

Add the qup uart node and geni se instance needed to support the serial console on the MTP. Signed-off-by: Rajendra Nayak --- arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 39 + arch/arm64/boot/dts/qcom/sdm845.dtsi| 39 + 2 files

[PATCH v5 3/4] arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP

Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files Signed-off-by: Rajendra Nayak Reviewed-by: Doug Anderson --- arch/arm64/boot/dts/qcom/Makefile | 1 + arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 15 ++

[PATCH v5 0/4] Add DTS for SDM845 SoC and MTP

These are basic device tree files needed to boot a SDM845 MTP board to a ramfs based serial console shell Bindings are based on whats proposed for pinctrl/serial/clock drivers for SDM845 SoC pinctrl: https://patchwork.kernel.org/patch/10157143/ (This is now pulled in by Linus Walleij for 4.17)

[PATCH v5 3/4] arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP

Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files Signed-off-by: Rajendra Nayak Reviewed-by: Doug Anderson --- arch/arm64/boot/dts/qcom/Makefile | 1 + arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 15 ++ arch/arm64/boot/dts/qcom/sdm845.dtsi| 277

[PATCH v5 0/4] Add DTS for SDM845 SoC and MTP

These are basic device tree files needed to boot a SDM845 MTP board to a ramfs based serial console shell Bindings are based on whats proposed for pinctrl/serial/clock drivers for SDM845 SoC pinctrl: https://patchwork.kernel.org/patch/10157143/ (This is now pulled in by Linus Walleij for 4.17)

[PATCH v5 1/4] dt-bindings: arm: Document kryo385 cpu

Document the compatible string for the Kryo385 cpus found in qualcomm SoCs. Signed-off-by: Rajendra Nayak Reviewed-by: Rob Herring Reviewed-by: Douglas Anderson --- Documentation/devicetree/bindings/arm/cpus.txt | 1 + 1 file

[PATCH v5 1/4] dt-bindings: arm: Document kryo385 cpu

Document the compatible string for the Kryo385 cpus found in qualcomm SoCs. Signed-off-by: Rajendra Nayak Reviewed-by: Rob Herring Reviewed-by: Douglas Anderson --- Documentation/devicetree/bindings/arm/cpus.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v1] drm/simple_kms_helper: Fix NULL pointer dereference with no active CRTC

From: Oleksandr Andrushchenko It is possible that drm_simple_kms_plane_atomic_check called with no CRTC set, e.g. when user-space application sets CRTC_ID/FB_ID to 0 before doing any actual drawing. This leads to NULL pointer dereference because in this case new

[PATCH v1] drm/simple_kms_helper: Fix NULL pointer dereference with no active CRTC

From: Oleksandr Andrushchenko It is possible that drm_simple_kms_plane_atomic_check called with no CRTC set, e.g. when user-space application sets CRTC_ID/FB_ID to 0 before doing any actual drawing. This leads to NULL pointer dereference because in this case new CRTC state is NULL and must be

Re: [PATCH v4 00/16] R-Car DU: Convert LVDS code to bridge driver

On 02/20/18 15:10, Laurent Pinchart wrote: > Hello, > > This patch series addresses a design mistake that dates back from the initial > DU support. Support for the LVDS encoders, which are IP cores separate from > the DU, was bundled in the DU driver. Worse, both the DU and LVDS were > described

Re: [PATCH v4 00/16] R-Car DU: Convert LVDS code to bridge driver

On 02/20/18 15:10, Laurent Pinchart wrote: > Hello, > > This patch series addresses a design mistake that dates back from the initial > DU support. Support for the LVDS encoders, which are IP cores separate from > the DU, was bundled in the DU driver. Worse, both the DU and LVDS were > described

Re: [PATCH] doc: process: Add "Root-caused-by" and "Suggested-by"

On Wed, Feb 21, 2018 at 8:43 PM, Randy Dunlap wrote: > On 02/21/2018 04:37 PM, Kees Cook wrote: >> As recently pointed out by Linus, "Root-caused-by" is a good tag to include >> since it can indicate significantly more work than "just" a Reported-by. >> This adds it and

Re: [PATCH] doc: process: Add "Root-caused-by" and "Suggested-by"

On Wed, Feb 21, 2018 at 8:43 PM, Randy Dunlap wrote: > On 02/21/2018 04:37 PM, Kees Cook wrote: >> As recently pointed out by Linus, "Root-caused-by" is a good tag to include >> since it can indicate significantly more work than "just" a Reported-by. >> This adds it and "Suggested-by" (which was

[PATCH 1/2] cpufreq: Reorder cpufreq_online() a bit

Ideally the de-allocation of resources should happen in the exact opposite order in which they were allocated. It helps maintain the code in long term, even if nothing really breaks with incorrect ordering. The same wasn't followed in cpufreq_online() and it has some inconsistencies. For example,

[PATCH 1/2] cpufreq: Reorder cpufreq_online() a bit

Ideally the de-allocation of resources should happen in the exact opposite order in which they were allocated. It helps maintain the code in long term, even if nothing really breaks with incorrect ordering. The same wasn't followed in cpufreq_online() and it has some inconsistencies. For example,

[PATCH 2/2] cpufreq: Validate cpufreq table from core

By design, it is responsibility of the cpufreq drivers to call cpufreq_frequency_table_cpuinfo() from their ->init() callback to validate the cpufreq table. But what if the cpufreq driver is buggy and fails to do so properly? It may then result in unexpected behavior from the driver or the

[PATCH 2/2] cpufreq: Validate cpufreq table from core

By design, it is responsibility of the cpufreq drivers to call cpufreq_frequency_table_cpuinfo() from their ->init() callback to validate the cpufreq table. But what if the cpufreq driver is buggy and fails to do so properly? It may then result in unexpected behavior from the driver or the

[PATCH] cpufreq: mediatek: Convert pr_warn() to pr_debug()

With multi-platform build images, this shows a message on non mediatek platforms, which is unnecessary. Convert pr_warn() to pr_debug() here. Signed-off-by: Viresh Kumar --- drivers/cpufreq/mediatek-cpufreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] cpufreq: mediatek: Convert pr_warn() to pr_debug()

With multi-platform build images, this shows a message on non mediatek platforms, which is unnecessary. Convert pr_warn() to pr_debug() here. Signed-off-by: Viresh Kumar --- drivers/cpufreq/mediatek-cpufreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v12 01/22] selftests/x86: Move protecton key selftest to arch neutral directory

* Ram Pai wrote: > cc: Dave Hansen > cc: Florian Weimer > Signed-off-by: Ram Pai > --- > tools/testing/selftests/vm/Makefile |1 + > tools/testing/selftests/vm/pkey-helpers.h | 223 >

Re: [PATCH v12 01/22] selftests/x86: Move protecton key selftest to arch neutral directory

* Ram Pai wrote: > cc: Dave Hansen > cc: Florian Weimer > Signed-off-by: Ram Pai > --- > tools/testing/selftests/vm/Makefile |1 + > tools/testing/selftests/vm/pkey-helpers.h | 223 > tools/testing/selftests/vm/protection_keys.c | 1407 > + >

[PATCH v1 1/5] dt-bindings: soc: update MT2712 power dt-bindings

Add new power domains(MFG_SC1/MFG_SC2/MFG_SC3) for MT2712 according to ECO design change. Signed-off-by: Weiyi Lu --- include/dt-bindings/power/mt2712-power.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/include/dt-bindings/power/mt2712-power.h

[PATCH v1 1/5] dt-bindings: soc: update MT2712 power dt-bindings

Add new power domains(MFG_SC1/MFG_SC2/MFG_SC3) for MT2712 according to ECO design change. Signed-off-by: Weiyi Lu --- include/dt-bindings/power/mt2712-power.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/include/dt-bindings/power/mt2712-power.h

[PATCH v1 3/5] dt-bindings: clock: add clocks for MT2712

add new clocks according to ECO design change Signed-off-by: Weiyi Lu --- include/dt-bindings/clock/mt2712-clk.h | 294 + 1 file changed, 151 insertions(+), 143 deletions(-) diff --git a/include/dt-bindings/clock/mt2712-clk.h

[PATCH v1 3/5] dt-bindings: clock: add clocks for MT2712

add new clocks according to ECO design change Signed-off-by: Weiyi Lu --- include/dt-bindings/clock/mt2712-clk.h | 294 + 1 file changed, 151 insertions(+), 143 deletions(-) diff --git a/include/dt-bindings/clock/mt2712-clk.h

[PATCH v1 4/5] arm64: dts: add clock device nodes of MT2712

add new clocks according to ECO design change Signed-off-by: Weiyi Lu --- arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 28 1 file changed, 28 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi

[PATCH v1 4/5] arm64: dts: add clock device nodes of MT2712

add new clocks according to ECO design change Signed-off-by: Weiyi Lu --- arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 28 1 file changed, 28 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi index

[PATCH v1 0/5] update Mediatek MT2712 clock and scpsys support

This series is based on v4.16-rc1 and composed of scpsys control (PATCH 1-2) and clock control (PATCH 3-5). Basically, all changes are for the ECO design change of MT2712. Weiyi Lu (5): dt-bindings: soc: update MT2712 power dt-bindings soc: mediatek: update power domain data of MT2712

[PATCH v1 2/5] soc: mediatek: update power domain data of MT2712

1. split MFG power domain into MFG/MFG_SC1/MFG_SC2/MFG_SC3 according to MT2712 ECO design change 2. add subdomain support for MT2712 Signed-off-by: Weiyi Lu --- drivers/soc/mediatek/mtk-scpsys.c | 42 +-- 1 file changed, 40

[PATCH v1 0/5] update Mediatek MT2712 clock and scpsys support

This series is based on v4.16-rc1 and composed of scpsys control (PATCH 1-2) and clock control (PATCH 3-5). Basically, all changes are for the ECO design change of MT2712. Weiyi Lu (5): dt-bindings: soc: update MT2712 power dt-bindings soc: mediatek: update power domain data of MT2712

[PATCH v1 2/5] soc: mediatek: update power domain data of MT2712

1. split MFG power domain into MFG/MFG_SC1/MFG_SC2/MFG_SC3 according to MT2712 ECO design change 2. add subdomain support for MT2712 Signed-off-by: Weiyi Lu --- drivers/soc/mediatek/mtk-scpsys.c | 42 +-- 1 file changed, 40 insertions(+), 2 deletions(-) diff

[PATCH v1 0/5] update Mediatek MT2712 clock and scpsys support

This series is based on v4.16-rc1 and composed of scpsys control (PATCH 1-2) and clock control (PATCH 3-5). Basically, all changes are for the ECO design change of MT2712. Weiyi Lu (5): dt-bindings: soc: update MT2712 power dt-bindings soc: mediatek: update power domain data of MT2712

[PATCH v1 0/5] update Mediatek MT2712 clock and scpsys support

This series is based on v4.16-rc1 and composed of scpsys control (PATCH 1-2) and clock control (PATCH 3-5). Basically, all changes are for the ECO design change of MT2712. Weiyi Lu (5): dt-bindings: soc: update MT2712 power dt-bindings soc: mediatek: update power domain data of MT2712

[PATCH v1 5/5] clk: mediatek: update clock driver of MT2712

According to ECO design change, 1. add new clock mux data and change some 2. add new clock gate data and clock factor data 3. change status register offset of infra subsystem Signed-off-by: Weiyi Lu --- drivers/clk/mediatek/clk-mt2712.c | 69

[PATCH v1 5/5] clk: mediatek: update clock driver of MT2712

According to ECO design change, 1. add new clock mux data and change some 2. add new clock gate data and clock factor data 3. change status register offset of infra subsystem Signed-off-by: Weiyi Lu --- drivers/clk/mediatek/clk-mt2712.c | 69 +++ 1 file

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On 2/21/2018 9:27 PM, Boqun Feng wrote: > On Wed, Feb 21, 2018 at 08:13:57PM -0800, Paul E. McKenney wrote: >> On Thu, Feb 22, 2018 at 11:23:49AM +0800, Boqun Feng wrote: >>> On Tue, Feb 20, 2018 at 03:25:10PM -0800, Paul E. McKenney wrote: From: Alan Stern

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On 2/21/2018 9:27 PM, Boqun Feng wrote: > On Wed, Feb 21, 2018 at 08:13:57PM -0800, Paul E. McKenney wrote: >> On Thu, Feb 22, 2018 at 11:23:49AM +0800, Boqun Feng wrote: >>> On Tue, Feb 20, 2018 at 03:25:10PM -0800, Paul E. McKenney wrote: From: Alan Stern This commit adds a

Re: [PATCH 4/4] fs/dcache: Avoid the try_lock loops in dentry_kill()

On Fri, Feb 16, 2018 at 10:03:15AM -0800, Linus Torvalds wrote: > On Fri, Feb 16, 2018 at 7:09 AM, John Ogness > wrote: > > dentry_kill() holds dentry->d_lock and needs to acquire both > > dentry->d_inode->i_lock and dentry->d_parent->d_lock. This cannot be > > done

Re: [PATCH 4/4] fs/dcache: Avoid the try_lock loops in dentry_kill()

On Fri, Feb 16, 2018 at 10:03:15AM -0800, Linus Torvalds wrote: > On Fri, Feb 16, 2018 at 7:09 AM, John Ogness > wrote: > > dentry_kill() holds dentry->d_lock and needs to acquire both > > dentry->d_inode->i_lock and dentry->d_parent->d_lock. This cannot be > > done with spin_lock() operations

RE: [PATCH] efivarfs: Limit the rate for non-root to read files

> - just make it return -EAGAIN instead of sleeping (which probably > just works fine and doesn't break anything and is simple) It is very simple. But it does break things :-(. If I read one of these files using "dd bs=1", that used to read the whole file (while generating lots of SMI). With the

RE: [PATCH] efivarfs: Limit the rate for non-root to read files

> - just make it return -EAGAIN instead of sleeping (which probably > just works fine and doesn't break anything and is simple) It is very simple. But it does break things :-(. If I read one of these files using "dd bs=1", that used to read the whole file (while generating lots of SMI). With the

Re: [PATCH] ocxl: Add get_metadata IOCTL to share OCXL information to userspace

On Thu, Feb 22, 2018 at 2:51 PM, Alastair D'Silva wrote: > On Thu, 2018-02-22 at 14:46 +1100, Balbir Singh wrote: > >> lpc_size could be added. It's currently useless to the library, but >> > doesn't >> > hurt. The one which was giving me troubles on a previous version of

Re: [PATCH] ocxl: Add get_metadata IOCTL to share OCXL information to userspace

On Thu, Feb 22, 2018 at 2:51 PM, Alastair D'Silva wrote: > On Thu, 2018-02-22 at 14:46 +1100, Balbir Singh wrote: > >> lpc_size could be added. It's currently useless to the library, but >> > doesn't >> > hurt. The one which was giving me troubles on a previous version of >> > this >> > patch

Re: [PATCH 4/4] fs/dcache: Avoid the try_lock loops in dentry_kill()

On Tue, Feb 20, 2018 at 12:34:57AM +0100, John Ogness wrote: > Implementation 3: The same as implementation 2 but using if's to > support branch prediction. This approach is probably the most > complicated to understand but will be the fastest. > > /* >* Lock the

Re: [PATCH 4/4] fs/dcache: Avoid the try_lock loops in dentry_kill()

On Tue, Feb 20, 2018 at 12:34:57AM +0100, John Ogness wrote: > Implementation 3: The same as implementation 2 but using if's to > support branch prediction. This approach is probably the most > complicated to understand but will be the fastest. > > /* >* Lock the

<    1   2   3   4   5   6   7   8   9   10   >