Re: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default

2017-10-18 Thread Ingo Molnar
* Byungchul Park wrote: > On Wed, Oct 18, 2017 at 12:09:44PM +0200, Ingo Molnar wrote: > > BTW., have you attempted limiting the depth of the stack traces? I suspect > > more > > than 2-4 are rarely required to disambiguate the calling context. > > I did it for you.

Re: [PATCH] checkpatch: Introduce check for format of Fixes line in commit log

2017-10-18 Thread Joe Perches
On Thu, 2017-10-19 at 05:52 +, Parav Pandit wrote: > Hi Joe, Hello Parav > > -Original Message- > > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > > ow...@vger.kernel.org] On Behalf Of Parav Pandit > > Sent: Tuesday, October 10, 2017 5:44 PM > > To: j...@perches.com;

Re: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default

2017-10-18 Thread Ingo Molnar
* Byungchul Park wrote: > On Wed, Oct 18, 2017 at 12:09:44PM +0200, Ingo Molnar wrote: > > BTW., have you attempted limiting the depth of the stack traces? I suspect > > more > > than 2-4 are rarely required to disambiguate the calling context. > > I did it for you. Let me show you the

Re: [PATCH] checkpatch: Introduce check for format of Fixes line in commit log

2017-10-18 Thread Joe Perches
On Thu, 2017-10-19 at 05:52 +, Parav Pandit wrote: > Hi Joe, Hello Parav > > -Original Message- > > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > > ow...@vger.kernel.org] On Behalf Of Parav Pandit > > Sent: Tuesday, October 10, 2017 5:44 PM > > To: j...@perches.com;

[PATCH v2 3/3] lockdep: Add a kernel parameter, crossrelease_fullstack

2017-10-18 Thread Byungchul Park
Make whether to allow recording full stack, in cross-release feature, switchable at boot time via a kernel parameter, 'crossrelease_fullstack'. In case of a splat with no stack trace, one could just reboot and set the kernel parameter to get the full data without having to recompile the kernel.

[PATCH v2 3/3] lockdep: Add a kernel parameter, crossrelease_fullstack

2017-10-18 Thread Byungchul Park
Make whether to allow recording full stack, in cross-release feature, switchable at boot time via a kernel parameter, 'crossrelease_fullstack'. In case of a splat with no stack trace, one could just reboot and set the kernel parameter to get the full data without having to recompile the kernel.

[tip:locking/core] locking/static_keys: Improve uninitialized key warning

2017-10-18 Thread tip-bot for Borislav Petkov
Commit-ID: 5cdda5117e125e0dbb020425cc55a4c143c6febc Gitweb: https://git.kernel.org/tip/5cdda5117e125e0dbb020425cc55a4c143c6febc Author: Borislav Petkov AuthorDate: Wed, 18 Oct 2017 17:24:28 +0200 Committer: Ingo Molnar CommitDate: Thu, 19 Oct 2017

[tip:locking/core] locking/static_keys: Improve uninitialized key warning

2017-10-18 Thread tip-bot for Borislav Petkov
Commit-ID: 5cdda5117e125e0dbb020425cc55a4c143c6febc Gitweb: https://git.kernel.org/tip/5cdda5117e125e0dbb020425cc55a4c143c6febc Author: Borislav Petkov AuthorDate: Wed, 18 Oct 2017 17:24:28 +0200 Committer: Ingo Molnar CommitDate: Thu, 19 Oct 2017 07:49:14 +0200 locking/static_keys:

[PATCH v2 0/3] crossrelease: make it not unwind by default

2017-10-18 Thread Byungchul Park
Change from v1 - Fix kconfig description as Ingo suggested - Fix commit message writing out CONFIG_ variable - Introduce a new kernel parameter, crossrelease_fullstack - Replace the number with the output of *perf* Byungchul Park (3): lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not

[PATCH v2 0/3] crossrelease: make it not unwind by default

2017-10-18 Thread Byungchul Park
Change from v1 - Fix kconfig description as Ingo suggested - Fix commit message writing out CONFIG_ variable - Introduce a new kernel parameter, crossrelease_fullstack - Replace the number with the output of *perf* Byungchul Park (3): lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not

RE: [PATCH 0/9] Intel Processor Trace virtulization enabling

2017-10-18 Thread Kang, Luwei
> Nested virtualization is interesting. We would like the nested > hypervisor to be forced to set the "use GPA for processor tracing" > secondary execution control whenever "enable EPT" is set and > RTIT_CTL is nonzero. There is no way to encode that in >

RE: [PATCH 0/9] Intel Processor Trace virtulization enabling

2017-10-18 Thread Kang, Luwei
> Nested virtualization is interesting. We would like the nested > hypervisor to be forced to set the "use GPA for processor tracing" > secondary execution control whenever "enable EPT" is set and > RTIT_CTL is nonzero. There is no way to encode that in >

[PATCH v2 2/3] lockdep: Remove BROKEN flag of LOCKDEP_CROSSRELEASE

2017-10-18 Thread Byungchul Park
Now the performance regression was fixed, re-enable CONFIG_LOCKDEP_CROSSRELEASE and CONFIG_LOCKDEP_COMPLETIONS. Signed-off-by: Byungchul Park --- lib/Kconfig.debug | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/Kconfig.debug

[PATCH v2 1/3] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default

2017-10-18 Thread Byungchul Park
Johan Hovold reported a performance regression by crossrelease like: > Boot time (from "Linux version" to login prompt) had in fact doubled > since 4.13 where it took 17 seconds (with my current config) compared to > the 35 seconds I now see with 4.14-rc4. > > I quick bisect pointed to lockdep

[PATCH v2 2/3] lockdep: Remove BROKEN flag of LOCKDEP_CROSSRELEASE

2017-10-18 Thread Byungchul Park
Now the performance regression was fixed, re-enable CONFIG_LOCKDEP_CROSSRELEASE and CONFIG_LOCKDEP_COMPLETIONS. Signed-off-by: Byungchul Park --- lib/Kconfig.debug | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index

[PATCH v2 1/3] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default

2017-10-18 Thread Byungchul Park
Johan Hovold reported a performance regression by crossrelease like: > Boot time (from "Linux version" to login prompt) had in fact doubled > since 4.13 where it took 17 seconds (with my current config) compared to > the 35 seconds I now see with 4.14-rc4. > > I quick bisect pointed to lockdep

Re: [PATCH v5] printk: hash addresses printed with %p

2017-10-18 Thread Jason A. Donenfeld
A small detail carried over from the other thread: > > but a bigger problem might the following thing: > > vscnprintf() > pointer() > ptr_to_id() >initialize_ptr_secret() > get_random_bytes() > _get_random_bytes() > extract_crng() >_extract_crng() >

Re: [PATCH v5] printk: hash addresses printed with %p

2017-10-18 Thread Jason A. Donenfeld
A small detail carried over from the other thread: > > but a bigger problem might the following thing: > > vscnprintf() > pointer() > ptr_to_id() >initialize_ptr_secret() > get_random_bytes() > _get_random_bytes() > extract_crng() >_extract_crng() >

RE: [PATCH] checkpatch: Introduce check for format of Fixes line in commit log

2017-10-18 Thread Parav Pandit
Hi Joe, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Parav Pandit > Sent: Tuesday, October 10, 2017 5:44 PM > To: j...@perches.com; a...@canonical.com > Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org;

RE: [PATCH] checkpatch: Introduce check for format of Fixes line in commit log

2017-10-18 Thread Parav Pandit
Hi Joe, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Parav Pandit > Sent: Tuesday, October 10, 2017 5:44 PM > To: j...@perches.com; a...@canonical.com > Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org;

Re: [PATCH] powerpc: ipic - fix status get and status clear

2017-10-18 Thread Christophe LEROY
Le 19/10/2017 à 07:06, Michael Ellerman a écrit : Christophe Leroy writes: IPIC Status is provided by register IPIC_SERSR and not by IPIC_SERMR which is the mask register. This seems like it would be a bad bug. But I guess it hasn't mattered for some reason? As

Re: [PATCH] powerpc: ipic - fix status get and status clear

2017-10-18 Thread Christophe LEROY
Le 19/10/2017 à 07:06, Michael Ellerman a écrit : Christophe Leroy writes: IPIC Status is provided by register IPIC_SERSR and not by IPIC_SERMR which is the mask register. This seems like it would be a bad bug. But I guess it hasn't mattered for some reason? As far as I can see, this

[PATCH V2] bcma: Use bcma_debug and not pr_cont in MIPS driver

2017-10-18 Thread Joe Perches
Commit 66cc04424960 ("bcma: use bcma_debug and pr_cont in MIPS driver") converted a printk(KERN_DEBUG to bcma_debug. bcma_debug is guarded by a #define DEBUG via pr_debug. This means that the bcma_debug will generally not be emitted but any pr_cont following the bcma_debug will be emitted.

[PATCH V2] bcma: Use bcma_debug and not pr_cont in MIPS driver

2017-10-18 Thread Joe Perches
Commit 66cc04424960 ("bcma: use bcma_debug and pr_cont in MIPS driver") converted a printk(KERN_DEBUG to bcma_debug. bcma_debug is guarded by a #define DEBUG via pr_debug. This means that the bcma_debug will generally not be emitted but any pr_cont following the bcma_debug will be emitted.

Re: [PATCH] bcma: Use bcma_debug and not pr_cont in MIPS driver

2017-10-18 Thread James Cameron
On Wed, Oct 18, 2017 at 10:12:18PM -0700, Joe Perches wrote: > Commit 66cc04424960 ("bcma: use bcma_debug and pr_cont in MIPS driver") > converted a printk(KERN_DEBUG to bcma_debug. > > bcma_debug is guarded by a #define DEBUG via pr_debug. > > This means that the bcma_debug will generally not

Re: [PATCH] bcma: Use bcma_debug and not pr_cont in MIPS driver

2017-10-18 Thread James Cameron
On Wed, Oct 18, 2017 at 10:12:18PM -0700, Joe Perches wrote: > Commit 66cc04424960 ("bcma: use bcma_debug and pr_cont in MIPS driver") > converted a printk(KERN_DEBUG to bcma_debug. > > bcma_debug is guarded by a #define DEBUG via pr_debug. > > This means that the bcma_debug will generally not

Re: [PATCH] Documentation: Add myself to the enforcement statement list

2017-10-18 Thread Greg Kroah-Hartman
On Wed, Oct 18, 2017 at 04:20:47PM -0700, Laura Abbott wrote: > I already Acked the patch, add my name to the list as well. > > Signed-off-by: Laura Abbott > --- > Documentation/process/kernel-enforcement-statement.rst | 1 + > 1 file changed, 1 insertion(+) Thanks, now

Re: [PATCH] Documentation: Add myself to the enforcement statement list

2017-10-18 Thread Greg Kroah-Hartman
On Wed, Oct 18, 2017 at 04:20:47PM -0700, Laura Abbott wrote: > I already Acked the patch, add my name to the list as well. > > Signed-off-by: Laura Abbott > --- > Documentation/process/kernel-enforcement-statement.rst | 1 + > 1 file changed, 1 insertion(+) Thanks, now queued up. greg k-h

Re: [PATCH v2] static_key: Improve uninizialized key warning

2017-10-18 Thread Ingo Molnar
* Steven Rostedt wrote: > On Wed, 18 Oct 2017 12:06:59 -0400 > Steven Rostedt wrote: > > > > Signed-off-by: Borislav Petkov > > > Cc: Hannes Frederic Sowa > > > Cc: Ingo Molnar > > > Cc:

Re: [PATCH v2] static_key: Improve uninizialized key warning

2017-10-18 Thread Ingo Molnar
* Steven Rostedt wrote: > On Wed, 18 Oct 2017 12:06:59 -0400 > Steven Rostedt wrote: > > > > Signed-off-by: Borislav Petkov > > > Cc: Hannes Frederic Sowa > > > Cc: Ingo Molnar > > > Cc: Juergen Gross > > > Cc: "Steven Rostedt (VMware)" > > > > Reviewed-by: Steven Rostedt (VMware) >

Re: [PATCH v7 4/4] remoteproc: qcom: Add support for mss remoteproc on msm8996

2017-10-18 Thread Sricharan R
Hi Bjorn, On 10/17/2017 12:28 AM, Bjorn Andersson wrote: > On Mon 16 Oct 06:19 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote: >> On 10/12/2017 11:50 PM, Bjorn Andersson wrote: > [..] >>> Please fix this and add my Acked-by >> Sure will do, just want to ask, when i am sending updated patches,

Re: [PATCH v7 4/4] remoteproc: qcom: Add support for mss remoteproc on msm8996

2017-10-18 Thread Sricharan R
Hi Bjorn, On 10/17/2017 12:28 AM, Bjorn Andersson wrote: > On Mon 16 Oct 06:19 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote: >> On 10/12/2017 11:50 PM, Bjorn Andersson wrote: > [..] >>> Please fix this and add my Acked-by >> Sure will do, just want to ask, when i am sending updated patches,

Re: [PATCH] hwmon: (coretemp) remove duplicated coretemp for same core id

2017-10-18 Thread Guenter Roeck
On 10/18/2017 07:28 PM, Shu Wang wrote: From: "Guenter Roeck" To: "Shu Wang" Cc: "fenghua yu" , jdelv...@suse.com, linux-hw...@vger.kernel.org, linux-kernel@vger.kernel.org, ch...@redhat.com, yiz...@redhat.com Sent: Wednesday,

Re: [PATCH] hwmon: (coretemp) remove duplicated coretemp for same core id

2017-10-18 Thread Guenter Roeck
On 10/18/2017 07:28 PM, Shu Wang wrote: From: "Guenter Roeck" To: "Shu Wang" Cc: "fenghua yu" , jdelv...@suse.com, linux-hw...@vger.kernel.org, linux-kernel@vger.kernel.org, ch...@redhat.com, yiz...@redhat.com Sent: Wednesday, October 18, 2017 9:14:39 PM Subject: Re: [PATCH] hwmon: (coretemp)

Re: [PATCH v2 2/2] extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
On 2017년 10월 19일 13:59, Chanwoo Choi wrote: > Hi, > > On 2017년 10월 19일 12:26, Raveendra Padasalagi wrote: >> Add changes to capture optional dt attribute "debounce-timeout-ms" >> provided in extcon node and used the same value if provided otherwise >> default value of 20ms is used for id and vbus

Re: [PATCH v2 2/2] extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
On 2017년 10월 19일 13:59, Chanwoo Choi wrote: > Hi, > > On 2017년 10월 19일 12:26, Raveendra Padasalagi wrote: >> Add changes to capture optional dt attribute "debounce-timeout-ms" >> provided in extcon node and used the same value if provided otherwise >> default value of 20ms is used for id and vbus

Re: [PATCH v3 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

2017-10-18 Thread Sricharan R
Hi Bjorn, On 10/12/2017 11:56 PM, Bjorn Andersson wrote: > On Wed 30 Aug 21:45 PDT 2017, Sricharan R wrote: > >> qcom_mdt_load function loads the mdt type firmware and >> initialises the secure memory as well. Make the initialisation only >> when requested by the caller, so that the function can

Re: [PATCH v3 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

2017-10-18 Thread Sricharan R
Hi Bjorn, On 10/12/2017 11:56 PM, Bjorn Andersson wrote: > On Wed 30 Aug 21:45 PDT 2017, Sricharan R wrote: > >> qcom_mdt_load function loads the mdt type firmware and >> initialises the secure memory as well. Make the initialisation only >> when requested by the caller, so that the function can

Re: [PATCH v3 1/7] ACPI/PPTT: Add Processor Properties Topology Table parsing

2017-10-18 Thread Tomasz Nowicki
On 18.10.2017 19:30, Jeremy Linton wrote: On 10/18/2017 05:24 AM, Tomasz Nowicki wrote: On 18.10.2017 07:39, Tomasz Nowicki wrote: Hi, On 17.10.2017 17:22, Jeremy Linton wrote: Hi, On 10/17/2017 08:25 AM, Tomasz Nowicki wrote: Hi Jeremy, I did second round of review and have some more

Re: [PATCH v3 1/7] ACPI/PPTT: Add Processor Properties Topology Table parsing

2017-10-18 Thread Tomasz Nowicki
On 18.10.2017 19:30, Jeremy Linton wrote: On 10/18/2017 05:24 AM, Tomasz Nowicki wrote: On 18.10.2017 07:39, Tomasz Nowicki wrote: Hi, On 17.10.2017 17:22, Jeremy Linton wrote: Hi, On 10/17/2017 08:25 AM, Tomasz Nowicki wrote: Hi Jeremy, I did second round of review and have some more

[PATCH] bcma: Use bcma_debug and not pr_cont in MIPS driver

2017-10-18 Thread Joe Perches
Commit 66cc04424960 ("bcma: use bcma_debug and pr_cont in MIPS driver") converted a printk(KERN_DEBUG to bcma_debug. bcma_debug is guarded by a #define DEBUG via pr_debug. This means that the bcma_debug will generally not be emitted but any pr_cont following the bcma_debug will be emitted.

[PATCH] bcma: Use bcma_debug and not pr_cont in MIPS driver

2017-10-18 Thread Joe Perches
Commit 66cc04424960 ("bcma: use bcma_debug and pr_cont in MIPS driver") converted a printk(KERN_DEBUG to bcma_debug. bcma_debug is guarded by a #define DEBUG via pr_debug. This means that the bcma_debug will generally not be emitted but any pr_cont following the bcma_debug will be emitted.

Re: [PATCH] perf test shell: trace+probe_libc_inet_pton.sh: force to use /bin/bash to load this script

2017-10-18 Thread Li Zhijian
ignore this patch please, it will broken the test description which is read from the first line of this script Thanks On 10/19/2017 11:53 AM, Li Zhijian wrote: this script contains Array, but not all sh support Array. by default, dash provides sh at ubuntu/debian which can not support

Re: [PATCH] perf test shell: trace+probe_libc_inet_pton.sh: force to use /bin/bash to load this script

2017-10-18 Thread Li Zhijian
ignore this patch please, it will broken the test description which is read from the first line of this script Thanks On 10/19/2017 11:53 AM, Li Zhijian wrote: this script contains Array, but not all sh support Array. by default, dash provides sh at ubuntu/debian which can not support

Re: [RFC PATCH] can: m_can: Support higher speed CAN-FD bitrates

2017-10-18 Thread Sekhar Nori
On Wednesday 18 October 2017 07:47 PM, Franklin S Cooper Jr wrote: > > > On 10/18/2017 08:24 AM, Sekhar Nori wrote: >> Hi Marc, >> >> On Wednesday 18 October 2017 06:14 PM, Marc Kleine-Budde wrote: >>> On 09/21/2017 02:48 AM, Franklin S Cooper Jr wrote: On 09/20/2017 04:37 PM,

Re: [RFC PATCH] can: m_can: Support higher speed CAN-FD bitrates

2017-10-18 Thread Sekhar Nori
On Wednesday 18 October 2017 07:47 PM, Franklin S Cooper Jr wrote: > > > On 10/18/2017 08:24 AM, Sekhar Nori wrote: >> Hi Marc, >> >> On Wednesday 18 October 2017 06:14 PM, Marc Kleine-Budde wrote: >>> On 09/21/2017 02:48 AM, Franklin S Cooper Jr wrote: On 09/20/2017 04:37 PM,

Re: [PATCH] powerpc: ipic - fix status get and status clear

2017-10-18 Thread Michael Ellerman
Christophe Leroy writes: > IPIC Status is provided by register IPIC_SERSR and not by IPIC_SERMR > which is the mask register. This seems like it would be a bad bug. But I guess it hasn't mattered for some reason? cheers > diff --git a/arch/powerpc/sysdev/ipic.c

Re: [PATCH] powerpc: ipic - fix status get and status clear

2017-10-18 Thread Michael Ellerman
Christophe Leroy writes: > IPIC Status is provided by register IPIC_SERSR and not by IPIC_SERMR > which is the mask register. This seems like it would be a bad bug. But I guess it hasn't mattered for some reason? cheers > diff --git a/arch/powerpc/sysdev/ipic.c b/arch/powerpc/sysdev/ipic.c >

Re: [PATCH v2 1/2] Documentation: dt: extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
Hi, On 2017년 10월 19일 13:47, Chanwoo Choi wrote: > On 2017년 10월 19일 12:25, Raveendra Padasalagi wrote: >> Add documentation on optional dt attribute "debounce-timeout-ms" >> in extcon node to capture user specified timeout value for id >> and vbus gpio detection. >> >> Signed-off-by: Raveendra

Re: [PATCH v2 1/2] Documentation: dt: extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
Hi, On 2017년 10월 19일 13:47, Chanwoo Choi wrote: > On 2017년 10월 19일 12:25, Raveendra Padasalagi wrote: >> Add documentation on optional dt attribute "debounce-timeout-ms" >> in extcon node to capture user specified timeout value for id >> and vbus gpio detection. >> >> Signed-off-by: Raveendra

Re: [PATCH v2 2/2] extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
Hi, On 2017년 10월 19일 12:26, Raveendra Padasalagi wrote: > Add changes to capture optional dt attribute "debounce-timeout-ms" > provided in extcon node and used the same value if provided otherwise > default value of 20ms is used for id and vbus gpios debounce time. > > Signed-off-by: Raveendra

Re: [PATCH v2 2/2] extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
Hi, On 2017년 10월 19일 12:26, Raveendra Padasalagi wrote: > Add changes to capture optional dt attribute "debounce-timeout-ms" > provided in extcon node and used the same value if provided otherwise > default value of 20ms is used for id and vbus gpios debounce time. > > Signed-off-by: Raveendra

Re: [PATCH v2 1/2] Documentation: dt: extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
On 2017년 10월 19일 12:25, Raveendra Padasalagi wrote: > Add documentation on optional dt attribute "debounce-timeout-ms" > in extcon node to capture user specified timeout value for id > and vbus gpio detection. > > Signed-off-by: Raveendra Padasalagi >

Re: [PATCH v2 1/2] Documentation: dt: extcon: add optional debounce-timeout-ms attribute

2017-10-18 Thread Chanwoo Choi
On 2017년 10월 19일 12:25, Raveendra Padasalagi wrote: > Add documentation on optional dt attribute "debounce-timeout-ms" > in extcon node to capture user specified timeout value for id > and vbus gpio detection. > > Signed-off-by: Raveendra Padasalagi > Reviewed-by: Ray Jui > Reviewed-by: Srinath

Re: [V14,1/4] powerpc/vphn: Update CPU topology when VPHN enabled

2017-10-18 Thread Michael Ellerman
On Fri, 2017-09-08 at 20:47:27 UTC, Michael Bringmann wrote: > powerpc/vphn: On Power systems with shared configurations of CPUs > and memory, there are some issues with the association of additional > CPUs and memory to nodes when hot-adding resources. This patch > corrects the currently broken

Re: [V14,1/4] powerpc/vphn: Update CPU topology when VPHN enabled

2017-10-18 Thread Michael Ellerman
On Fri, 2017-09-08 at 20:47:27 UTC, Michael Bringmann wrote: > powerpc/vphn: On Power systems with shared configurations of CPUs > and memory, there are some issues with the association of additional > CPUs and memory to nodes when hot-adding resources. This patch > corrects the currently broken

Re: [PATCH 01/14] Documentation: Add SoundWire summary

2017-10-18 Thread Vinod Koul
Thanks for the quick review Randy, On Wed, Oct 18, 2017 at 08:33:08PM -0700, Randy Dunlap wrote: > On 10/18/17 20:03, Vinod Koul wrote: > > +SoundWire is a new interface ratified in 2015 by the MIPI Alliance. > > +SoundWire is used for transporting data typically related to audio > >

Re: [PATCH 01/14] Documentation: Add SoundWire summary

2017-10-18 Thread Vinod Koul
Thanks for the quick review Randy, On Wed, Oct 18, 2017 at 08:33:08PM -0700, Randy Dunlap wrote: > On 10/18/17 20:03, Vinod Koul wrote: > > +SoundWire is a new interface ratified in 2015 by the MIPI Alliance. > > +SoundWire is used for transporting data typically related to audio > >

Re: [PATCH v5 03/10] kexec_file: factor out arch_kexec_kernel_*() from x86, powerpc

2017-10-18 Thread AKASHI Takahiro
On Sat, Oct 14, 2017 at 07:37:04PM +0800, kbuild test robot wrote: > Hi AKASHI, > > [auto build test WARNING on arm64/for-next/core] > [also build test WARNING on v4.14-rc4 next-20171013] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > >

Re: [PATCH v5 03/10] kexec_file: factor out arch_kexec_kernel_*() from x86, powerpc

2017-10-18 Thread AKASHI Takahiro
On Sat, Oct 14, 2017 at 07:37:04PM +0800, kbuild test robot wrote: > Hi AKASHI, > > [auto build test WARNING on arm64/for-next/core] > [also build test WARNING on v4.14-rc4 next-20171013] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > >

Re: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default

2017-10-18 Thread Byungchul Park
On Wed, Oct 18, 2017 at 12:09:44PM +0200, Ingo Molnar wrote: > BTW., have you attempted limiting the depth of the stack traces? I suspect > more > than 2-4 are rarely required to disambiguate the calling context. I did it for you. Let me show you the result. 1. No lockdep Performance counter

Re: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default

2017-10-18 Thread Byungchul Park
On Wed, Oct 18, 2017 at 12:09:44PM +0200, Ingo Molnar wrote: > BTW., have you attempted limiting the depth of the stack traces? I suspect > more > than 2-4 are rarely required to disambiguate the calling context. I did it for you. Let me show you the result. 1. No lockdep Performance counter

Re: [PATCH] zswap: Same-filled pages handling

2017-10-18 Thread Andi Kleen
> Yes. Every 64-bit repeating pattern is also a 32-bit repeating pattern. > Supporting a 64-bit pattern on a 32-bit kernel is painful, but it makes > no sense to *not* support a 64-bit pattern on a 64-bit kernel. But a 32bit repeating pattern is not necessarily a 64bit pattern. >This is the

Re: [PATCH] zswap: Same-filled pages handling

2017-10-18 Thread Andi Kleen
> Yes. Every 64-bit repeating pattern is also a 32-bit repeating pattern. > Supporting a 64-bit pattern on a 32-bit kernel is painful, but it makes > no sense to *not* support a 64-bit pattern on a 64-bit kernel. But a 32bit repeating pattern is not necessarily a 64bit pattern. >This is the

Re: [PATCH v1] mm/mempolicy.c: Fix get_nodes() off-by-one error.

2017-10-18 Thread Andi Kleen
On Thu, Oct 19, 2017 at 03:48:09AM +, Sandoval Castro, Luis Felipe wrote: > On Tue 18-10-17 10:42:34, Luis Felipe Sandoval Castro wrote: > > Sorry for the delayed replay, from your feedback I don't think my > patch has any chances of being merged... I'm wondering though, > if a note in the

Re: [PATCH v1] mm/mempolicy.c: Fix get_nodes() off-by-one error.

2017-10-18 Thread Andi Kleen
On Thu, Oct 19, 2017 at 03:48:09AM +, Sandoval Castro, Luis Felipe wrote: > On Tue 18-10-17 10:42:34, Luis Felipe Sandoval Castro wrote: > > Sorry for the delayed replay, from your feedback I don't think my > patch has any chances of being merged... I'm wondering though, > if a note in the

[patch-rt] drivers/zram: pass num_pages to zram_meta_init_table_locks()

2017-10-18 Thread Mike Galbraith
zram cleanup forgot to adjust passed argument when changing zram_meta_init_table_locks() to expect page count instead of disk size. Doing so fixes ltp inspired explosions. Signed-off-by: Mike Galbraith --- drivers/block/zram/zram_drv.c |2 +- 1 file changed, 1 insertion(+),

[patch-rt] drivers/zram: pass num_pages to zram_meta_init_table_locks()

2017-10-18 Thread Mike Galbraith
zram cleanup forgot to adjust passed argument when changing zram_meta_init_table_locks() to expect page count instead of disk size. Doing so fixes ltp inspired explosions. Signed-off-by: Mike Galbraith --- drivers/block/zram/zram_drv.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] perf test shell: trace+probe_libc_inet_pton.sh: force to use /bin/bash to load this script

2017-10-18 Thread Li Zhijian
this script contains Array, but not all sh support Array. by default, dash provides sh at ubuntu/debian which can not support Array. so force to use /bin/bash it can fix following issue: lizhijian@localhost:~/lkp/linux/tools/perf/tests/shell$ sudo ./trace+probe_libc_inet_pton.sh [sudo] password

[PATCH] perf test shell: trace+probe_libc_inet_pton.sh: force to use /bin/bash to load this script

2017-10-18 Thread Li Zhijian
this script contains Array, but not all sh support Array. by default, dash provides sh at ubuntu/debian which can not support Array. so force to use /bin/bash it can fix following issue: lizhijian@localhost:~/lkp/linux/tools/perf/tests/shell$ sudo ./trace+probe_libc_inet_pton.sh [sudo] password

Re: [PATCH] KVM: X86: #GP when guest attempts to write MCi banks w/o 0

2017-10-18 Thread Jim Mattson
MCi_STATUS sounds fine, or any other Intel constraints that are guarded by checks for virtualizing an Intel CPU. On Wed, Oct 18, 2017 at 8:04 PM, Wanpeng Li wrote: > On 10/19/17 10:49 AM, Jim Mattson wrote: > > Right. I was side-tracked by the code above yours for

Re: [PATCH] KVM: X86: #GP when guest attempts to write MCi banks w/o 0

2017-10-18 Thread Jim Mattson
MCi_STATUS sounds fine, or any other Intel constraints that are guarded by checks for virtualizing an Intel CPU. On Wed, Oct 18, 2017 at 8:04 PM, Wanpeng Li wrote: > On 10/19/17 10:49 AM, Jim Mattson wrote: > > Right. I was side-tracked by the code above yours for MCi_CTL. > However, does

[PATCH v6 00/10] rockchip: kevin: Enable edp display

2017-10-18 Thread Jeffy Chen
Make edp display works on chromebook kevin(at least for boot animation). Also solve some issues i meet during the bringup. Changes in v6: Don't change order of rockchip_drm_psr_register(). Changes in v5: Call the destroy hook in the error handling path like in unbind(). Call the destroy hook

[PATCH v6 00/10] rockchip: kevin: Enable edp display

2017-10-18 Thread Jeffy Chen
Make edp display works on chromebook kevin(at least for boot animation). Also solve some issues i meet during the bringup. Changes in v6: Don't change order of rockchip_drm_psr_register(). Changes in v5: Call the destroy hook in the error handling path like in unbind(). Call the destroy hook

[PATCH v6 01/10] arm64: dts: rockchip: Enable edp disaplay on kevin

2017-10-18 Thread Jeffy Chen
Add edp panel and enable related nodes on kevin. Signed-off-by: Jeffy Chen Reviewed-by: Mark Yao --- Changes in v6: None Changes in v5: None arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts | 29 +++

[PATCH v6 01/10] arm64: dts: rockchip: Enable edp disaplay on kevin

2017-10-18 Thread Jeffy Chen
Add edp panel and enable related nodes on kevin. Signed-off-by: Jeffy Chen Reviewed-by: Mark Yao --- Changes in v6: None Changes in v5: None arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts | 29 +++ arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 16 +

[PATCH v6 04/10] drm/bridge: analogix_dp: Fix connector and encoder cleanup

2017-10-18 Thread Jeffy Chen
Since we are initing connector in the core driver and encoder in the plat driver, let's clean them up in the right places. Signed-off-by: Jeffy Chen Reviewed-by: Andrzej Hajda --- Changes in v6: Don't change order of rockchip_drm_psr_register().

[PATCH v6 04/10] drm/bridge: analogix_dp: Fix connector and encoder cleanup

2017-10-18 Thread Jeffy Chen
Since we are initing connector in the core driver and encoder in the plat driver, let's clean them up in the right places. Signed-off-by: Jeffy Chen Reviewed-by: Andrzej Hajda --- Changes in v6: Don't change order of rockchip_drm_psr_register(). Changes in v5: None

Re: [PATCH] KVM: PPC: Book3S HV: Delete an error message for a failed memory allocation in kvmppc_allocate_hpt()

2017-10-18 Thread Paul Mackerras
On Thu, Oct 05, 2017 at 01:23:30PM +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 5 Oct 2017 13:16:51 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle

Re: [PATCH] KVM: PPC: Book3S HV: Delete an error message for a failed memory allocation in kvmppc_allocate_hpt()

2017-10-18 Thread Paul Mackerras
On Thu, Oct 05, 2017 at 01:23:30PM +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 5 Oct 2017 13:16:51 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus

[PATCH v6 06/10] drm/rockchip: dw-mipi-dsi: Fix error handling path

2017-10-18 Thread Jeffy Chen
Add missing pm_runtime_disable() in bind()'s error handling path. Also cleanup encoder & connector in unbind(). Fixes: 80a9a059d4e4 ("drm/rockchip/dsi: add dw-mipi power domain support") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: Call the

Re: [PATCH 1/10] KVM: PPC: Book3S HV: Use ARRAY_SIZE macro

2017-10-18 Thread Paul Mackerras
On Sun, Sep 03, 2017 at 02:19:31PM +0200, Thomas Meyer wrote: > Use ARRAY_SIZE macro, rather than explicitly coding some variant of it > yourself. > Found with: find -type f -name "*.c" -o -name "*.h" | xargs perl -p -i -e > 's/\bsizeof\s*\(\s*(\w+)\s*\)\s*\ /\s*sizeof\s*\(\s*\1\s*\[\s*0\s*\]\s*\)

[PATCH v6 06/10] drm/rockchip: dw-mipi-dsi: Fix error handling path

2017-10-18 Thread Jeffy Chen
Add missing pm_runtime_disable() in bind()'s error handling path. Also cleanup encoder & connector in unbind(). Fixes: 80a9a059d4e4 ("drm/rockchip/dsi: add dw-mipi power domain support") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: Call the destroy hook in the error

Re: [PATCH 1/10] KVM: PPC: Book3S HV: Use ARRAY_SIZE macro

2017-10-18 Thread Paul Mackerras
On Sun, Sep 03, 2017 at 02:19:31PM +0200, Thomas Meyer wrote: > Use ARRAY_SIZE macro, rather than explicitly coding some variant of it > yourself. > Found with: find -type f -name "*.c" -o -name "*.h" | xargs perl -p -i -e > 's/\bsizeof\s*\(\s*(\w+)\s*\)\s*\ /\s*sizeof\s*\(\s*\1\s*\[\s*0\s*\]\s*\)

[PATCH v6 10/10] drm/rockchip: dw_hdmi: Fix error handling path

2017-10-18 Thread Jeffy Chen
Add missing clk_disable_unprepare() in bind()'s error handling path and unbind(). Also inline clk_prepare_enable() with bind(). Fixes: 12b9f204e804 ("drm: bridge/dw_hdmi: add rockchip rk3288 support") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5:

[PATCH v6 10/10] drm/rockchip: dw_hdmi: Fix error handling path

2017-10-18 Thread Jeffy Chen
Add missing clk_disable_unprepare() in bind()'s error handling path and unbind(). Also inline clk_prepare_enable() with bind(). Fixes: 12b9f204e804 ("drm: bridge/dw_hdmi: add rockchip rk3288 support") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: Add disable to unbind(), and

[PATCH v6 09/10] drm/bridge/synopsys: dw-hdmi: Do not use device's drvdata

2017-10-18 Thread Jeffy Chen
Let plat drivers own the drvdata, so that they could cleanup resources in their unbind(). Signed-off-by: Jeffy Chen Reviewed-by: Neil Armstrong --- Changes in v6: None Changes in v5: None drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 43

[PATCH v6 08/10] drm/bridge/synopsys: dw-hdmi: Add missing bridge detach

2017-10-18 Thread Jeffy Chen
We inited connector in attach(), so need a detach() to cleanup. Also fix wrong use of dw_hdmi_remove() in bind(). Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: None drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 10 +- 1 file changed, 9

[PATCH v6 09/10] drm/bridge/synopsys: dw-hdmi: Do not use device's drvdata

2017-10-18 Thread Jeffy Chen
Let plat drivers own the drvdata, so that they could cleanup resources in their unbind(). Signed-off-by: Jeffy Chen Reviewed-by: Neil Armstrong --- Changes in v6: None Changes in v5: None drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 43 ++---

[PATCH v6 08/10] drm/bridge/synopsys: dw-hdmi: Add missing bridge detach

2017-10-18 Thread Jeffy Chen
We inited connector in attach(), so need a detach() to cleanup. Also fix wrong use of dw_hdmi_remove() in bind(). Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: None drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-)

[PATCH v6 07/10] drm/rockchip: inno_hdmi: Fix error handling path

2017-10-18 Thread Jeffy Chen
Add missing error handling in bind(). Fixes: 412d4ae6b7a5 ("drm/rockchip: hdmi: add Innosilicon HDMI support") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: Call the destroy hook in the error handling path like in unbind(). Update cleanup order in

[PATCH v6 07/10] drm/rockchip: inno_hdmi: Fix error handling path

2017-10-18 Thread Jeffy Chen
Add missing error handling in bind(). Fixes: 412d4ae6b7a5 ("drm/rockchip: hdmi: add Innosilicon HDMI support") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: Call the destroy hook in the error handling path like in unbind(). Update cleanup order in unbind().

Re: [PATCH 6/7] KVM: PPC: Cocci spatch "vma_pages"

2017-10-18 Thread Paul Mackerras
On Thu, Sep 21, 2017 at 12:29:36AM +0200, Thomas Meyer wrote: > Use vma_pages function on vma object instead of explicit computation. > Found by coccinelle spatch "api/vma_pages.cocci" > > Signed-off-by: Thomas Meyer Thanks, applied to my kvm-ppc-next branch, with the headline

[PATCH v6 05/10] drm/rockchip: analogix_dp: Add a sanity check for rockchip_drm_psr_register()

2017-10-18 Thread Jeffy Chen
The rockchip_drm_psr_register() can fail, so add a sanity check for that. Also reorder the calls in unbind() to match bind(). Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: None drivers/gpu/drm/rockchip/analogix_dp-rockchip.c | 15 +++

[PATCH v6 05/10] drm/rockchip: analogix_dp: Add a sanity check for rockchip_drm_psr_register()

2017-10-18 Thread Jeffy Chen
The rockchip_drm_psr_register() can fail, so add a sanity check for that. Also reorder the calls in unbind() to match bind(). Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: None drivers/gpu/drm/rockchip/analogix_dp-rockchip.c | 15 +++ 1 file changed, 11

Re: [PATCH 6/7] KVM: PPC: Cocci spatch "vma_pages"

2017-10-18 Thread Paul Mackerras
On Thu, Sep 21, 2017 at 12:29:36AM +0200, Thomas Meyer wrote: > Use vma_pages function on vma object instead of explicit computation. > Found by coccinelle spatch "api/vma_pages.cocci" > > Signed-off-by: Thomas Meyer Thanks, applied to my kvm-ppc-next branch, with the headline "KVM: PPC: BookE:

[PATCH v6 02/10] drm/rockchip: analogix_dp: Remove unnecessary init code

2017-10-18 Thread Jeffy Chen
Remove unnecessary init code, since we would do it in the power_on() callback. Also move of parse code to probe(). Fixes: 9e32e16e9e98 ("drm: rockchip: dp: add rockchip platform dp driver") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: None

[PATCH v6 03/10] drm/bridge: analogix: Do not use device's drvdata

2017-10-18 Thread Jeffy Chen
The driver that instantiates the bridge should own the drvdata, as all driver model callbacks (probe, remove, shutdown, PM ops, etc.) are also owned by its driver struct. Moreover, storing two different pointer types in driver data depending on driver initialization status is barely a good

[PATCH v6 02/10] drm/rockchip: analogix_dp: Remove unnecessary init code

2017-10-18 Thread Jeffy Chen
Remove unnecessary init code, since we would do it in the power_on() callback. Also move of parse code to probe(). Fixes: 9e32e16e9e98 ("drm: rockchip: dp: add rockchip platform dp driver") Signed-off-by: Jeffy Chen --- Changes in v6: None Changes in v5: None

[PATCH v6 03/10] drm/bridge: analogix: Do not use device's drvdata

2017-10-18 Thread Jeffy Chen
The driver that instantiates the bridge should own the drvdata, as all driver model callbacks (probe, remove, shutdown, PM ops, etc.) are also owned by its driver struct. Moreover, storing two different pointer types in driver data depending on driver initialization status is barely a good

  1   2   3   4   5   6   7   8   9   10   >