Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On Fri, 28 Jul 2017, Tomi Sarvela wrote: > On 28/07/17 00:08, Thomas Gleixner wrote: > The patch didn't apply cleanly: can you tell exact commit or tag it has been > created against? Linus head > I tried to hand-wrangle the changes in, but then I got compilation > errors: Sorry, forgot to

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On Fri, 28 Jul 2017, Tomi Sarvela wrote: > On 28/07/17 00:08, Thomas Gleixner wrote: > The patch didn't apply cleanly: can you tell exact commit or tag it has been > created against? Linus head > I tried to hand-wrangle the changes in, but then I got compilation > errors: Sorry, forgot to

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: expose /sys/fs/f2fs/features

Hi Jaegeuk, On 2017/7/27 5:44, Jaegeuk Kim wrote: > Change log from v1: > - add /sys/fs/f2fs/dev/features > > This patch exposes what features are supported by current f2fs build to sysfs > entry via: > > /sys/fs/f2fs/features/> /sys/fs/f2fs/dev/features > > Signed-off-by: Jaegeuk Kim

Re: [PATCH v3 1/7] integrity: Introduce struct evm_hmac_xattr

Hi Thiago, On Thu, 2017-07-06 at 19:17 -0300, Thiago Jung Bauermann wrote: > Even though struct evm_ima_xattr_data includes a fixed-size array to hold a > SHA1 digest, most of the code ignores the array and uses the struct to mean > "type indicator followed by data of unspecified size" and tracks

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: expose /sys/fs/f2fs/features

Hi Jaegeuk, On 2017/7/27 5:44, Jaegeuk Kim wrote: > Change log from v1: > - add /sys/fs/f2fs/dev/features > > This patch exposes what features are supported by current f2fs build to sysfs > entry via: > > /sys/fs/f2fs/features/> /sys/fs/f2fs/dev/features > > Signed-off-by: Jaegeuk Kim > ---

Re: [PATCH v3 1/7] integrity: Introduce struct evm_hmac_xattr

Hi Thiago, On Thu, 2017-07-06 at 19:17 -0300, Thiago Jung Bauermann wrote: > Even though struct evm_ima_xattr_data includes a fixed-size array to hold a > SHA1 digest, most of the code ignores the array and uses the struct to mean > "type indicator followed by data of unspecified size" and tracks

Re: [PATCH v3 0/2] media: Add Amlogic Meson AO CEC Controller support

On 07/28/2017 02:35 PM, Hans Verkuil wrote: > Hi Neil, > > On 07/27/2017 05:20 PM, Neil Armstrong wrote: >> The Amlogic SoC embeds a standalone CEC controller, this patch adds a driver >> for such controller. >> The controller does not need HPD to be active, and could support up to max >> 5

Re: [PATCH v3 0/2] media: Add Amlogic Meson AO CEC Controller support

On 07/28/2017 02:35 PM, Hans Verkuil wrote: > Hi Neil, > > On 07/27/2017 05:20 PM, Neil Armstrong wrote: >> The Amlogic SoC embeds a standalone CEC controller, this patch adds a driver >> for such controller. >> The controller does not need HPD to be active, and could support up to max >> 5

Re: [PATCH v2 4/4] gfs2: convert to errseq_t based writeback error reporting for fsync

Hi, On 27/07/17 13:47, Bob Peterson wrote: - Original Message - | On Wed, 2017-07-26 at 12:21 -0700, Matthew Wilcox wrote: | > On Wed, Jul 26, 2017 at 01:55:38PM -0400, Jeff Layton wrote: | > > @@ -668,12 +668,14 @@ static int gfs2_fsync(struct file *file, loff_t | > > start, loff_t

Re: [PATCH v2 4/4] gfs2: convert to errseq_t based writeback error reporting for fsync

Hi, On 27/07/17 13:47, Bob Peterson wrote: - Original Message - | On Wed, 2017-07-26 at 12:21 -0700, Matthew Wilcox wrote: | > On Wed, Jul 26, 2017 at 01:55:38PM -0400, Jeff Layton wrote: | > > @@ -668,12 +668,14 @@ static int gfs2_fsync(struct file *file, loff_t | > > start, loff_t

Re: [PATCH v3 0/2] media: Add Amlogic Meson AO CEC Controller support

Hi Neil, On 07/27/2017 05:20 PM, Neil Armstrong wrote: > The Amlogic SoC embeds a standalone CEC controller, this patch adds a driver > for such controller. > The controller does not need HPD to be active, and could support up to max > 5 logical addresses, but only 1 is handled since the Suspend

Re: [PATCH v3 0/2] media: Add Amlogic Meson AO CEC Controller support

Hi Neil, On 07/27/2017 05:20 PM, Neil Armstrong wrote: > The Amlogic SoC embeds a standalone CEC controller, this patch adds a driver > for such controller. > The controller does not need HPD to be active, and could support up to max > 5 logical addresses, but only 1 is handled since the Suspend

Re: [PATCH] cpufreq: x86: Make scaling_cur_freq behave more as expected

On Thursday, July 27, 2017 11:01:39 PM Doug Smythies wrote: > On 2017.07.27 17:13 Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > After commit f8475cef9008 "x86: use common aperfmperf_khz_on_cpu() to > > calculate KHz using APERF/MPERF" the

Re: [PATCH] cpufreq: x86: Make scaling_cur_freq behave more as expected

On Thursday, July 27, 2017 11:01:39 PM Doug Smythies wrote: > On 2017.07.27 17:13 Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > After commit f8475cef9008 "x86: use common aperfmperf_khz_on_cpu() to > > calculate KHz using APERF/MPERF" the scaling_cur_freq policy attribute > > in

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On 27/07/17 10:36, Tomi Sarvela wrote: On 26/07/17 17:26, Thomas Gleixner wrote: On Wed, 26 Jul 2017, Martin Peres wrote: On 25/07/17 10:01, Tomi Sarvela wrote: On 24/07/17 19:37, Martin Peres wrote: On 24/07/17 19:35, Thomas Gleixner wrote: On Mon, 24 Jul 2017, Martin Peres wrote: On

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On 27/07/17 10:36, Tomi Sarvela wrote: On 26/07/17 17:26, Thomas Gleixner wrote: On Wed, 26 Jul 2017, Martin Peres wrote: On 25/07/17 10:01, Tomi Sarvela wrote: On 24/07/17 19:37, Martin Peres wrote: On 24/07/17 19:35, Thomas Gleixner wrote: On Mon, 24 Jul 2017, Martin Peres wrote: On

[PATCH] fuse: convert to errseq_t based error tracking for fsync

From: Jeff Layton Change to file_write_and_wait_range and file_check_and_advance_wb_err. Signed-off-by: Jeff Layton --- fs/fuse/file.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) This patch is untested, mostly because I have no idea how

[PATCH] fuse: convert to errseq_t based error tracking for fsync

From: Jeff Layton Change to file_write_and_wait_range and file_check_and_advance_wb_err. Signed-off-by: Jeff Layton --- fs/fuse/file.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) This patch is untested, mostly because I have no idea how to test it. Based on my experience with

Re: Possible race condition in oom-killer

[CC linux-mm] On Fri 28-07-17 17:22:25, Manish Jaggi wrote: > was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap > > Hi Michal, > On 7/27/2017 2:54 PM, Michal Hocko wrote: > >On Thu 27-07-17 13:59:09, Manish Jaggi wrote: > >[...] > >>With 4.11.6 I was getting random kernel panics

Re: Possible race condition in oom-killer

[CC linux-mm] On Fri 28-07-17 17:22:25, Manish Jaggi wrote: > was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap > > Hi Michal, > On 7/27/2017 2:54 PM, Michal Hocko wrote: > >On Thu 27-07-17 13:59:09, Manish Jaggi wrote: > >[...] > >>With 4.11.6 I was getting random kernel panics

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On 28/07/17 00:08, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Tomi Sarvela wrote: On 27/07/17 10:42, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Tomi Sarvela wrote: On 26/07/17 17:26, Thomas Gleixner

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On 28/07/17 00:08, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Tomi Sarvela wrote: On 27/07/17 10:42, Thomas Gleixner wrote: On Thu, 27 Jul 2017, Tomi Sarvela wrote: On 26/07/17 17:26, Thomas Gleixner

Re: [RESEND PATCH] ARM: dts: stm32: Add DMA support for STM32H743 SoC

Hi, On 07/11/2017 08:56 AM, Pierre-Yves MORDRET wrote: This patch adds DMA support for STM32H743 SoC. Signed-off-by: Pierre-Yves MORDRET --- arch/arm/boot/dts/stm32h743.dtsi | 32 1 file changed, 32 insertions(+) diff --git

Re: [RESEND PATCH] ARM: dts: stm32: Add DMA support for STM32H743 SoC

Hi, On 07/11/2017 08:56 AM, Pierre-Yves MORDRET wrote: This patch adds DMA support for STM32H743 SoC. Signed-off-by: Pierre-Yves MORDRET --- arch/arm/boot/dts/stm32h743.dtsi | 32 1 file changed, 32 insertions(+) diff --git

Re: [PATCH -tip v6] irq: Make irqentry text section unconditional

Sorry, please ignore this patch. I missed to send 2nd patch... On Fri, 28 Jul 2017 21:20:22 +0900 Masami Hiramatsu wrote: > Generate irqentry and softirqentry text sections without > any configs. This will add above extra sections, but > no performace impact. > >

Re: [PATCH -tip v6] irq: Make irqentry text section unconditional

Sorry, please ignore this patch. I missed to send 2nd patch... On Fri, 28 Jul 2017 21:20:22 +0900 Masami Hiramatsu wrote: > Generate irqentry and softirqentry text sections without > any configs. This will add above extra sections, but > no performace impact. > > Signed-off-by: Masami

Re: [PATCH 2/2] init/main.c: Fixes quoted string split across lines & missing blank line after declaration

On Fri, 28 Jul 2017 11:56:46 +0530 janani-sankarababu wrote: > Signed-off-by: Janani S > --- > init/main.c | 5 - > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/init/main.c b/init/main.c > index f8eb4966..920b829 100644 > ---

Re: [PATCH 2/2] init/main.c: Fixes quoted string split across lines & missing blank line after declaration

On Fri, 28 Jul 2017 11:56:46 +0530 janani-sankarababu wrote: > Signed-off-by: Janani S > --- > init/main.c | 5 - > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/init/main.c b/init/main.c > index f8eb4966..920b829 100644 > --- a/init/main.c > +++ b/init/main.c > @@

Re: [RESEND PATCH] ARM: dts: stm32: Add DMA support for STM32F746 SoC

Hi Pierre-Yves, On 07/11/2017 08:54 AM, Pierre-Yves MORDRET wrote: This patch adds DMA support for STM32F746 SoC. Signed-off-by: Pierre-Yves MORDRET --- arch/arm/boot/dts/stm32f746.dtsi | 31 +++ 1 file changed, 31 insertions(+) diff

Re: [RESEND PATCH] ARM: dts: stm32: Add DMA support for STM32F746 SoC

Hi Pierre-Yves, On 07/11/2017 08:54 AM, Pierre-Yves MORDRET wrote: This patch adds DMA support for STM32F746 SoC. Signed-off-by: Pierre-Yves MORDRET --- arch/arm/boot/dts/stm32f746.dtsi | 31 +++ 1 file changed, 31 insertions(+) diff --git

[PATCH -tip v6 2/2] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Since the kernel segment registers are not prepared at the entry of irq-entry code, if a kprobe on such code is jump-optimized, accessing per-cpu variables may cause kernel panic. However, if the kprobe is not optimized, it kicks int3 exception and set segment registers correctly. This checks

[PATCH -tip v6 2/2] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Since the kernel segment registers are not prepared at the entry of irq-entry code, if a kprobe on such code is jump-optimized, accessing per-cpu variables may cause kernel panic. However, if the kprobe is not optimized, it kicks int3 exception and set segment registers correctly. This checks

[PATCH -tip v6 1/2] irq: Make irqentry text section unconditional

Generate irqentry and softirqentry text sections without any configs. This will add above extra sections, but no performace impact. Signed-off-by: Masami Hiramatsu Suggested-by: Ingo Molnar --- arch/arm/include/asm/traps.h |7 ---

[PATCH -tip v6 1/2] irq: Make irqentry text section unconditional

Generate irqentry and softirqentry text sections without any configs. This will add above extra sections, but no performace impact. Signed-off-by: Masami Hiramatsu Suggested-by: Ingo Molnar --- arch/arm/include/asm/traps.h |7 --- arch/arm64/include/asm/traps.h|7 ---

Re: [PATCH] init:main.c: Fixed issues in Block comments and removed braces in single statement if block

On Fri, 28 Jul 2017 11:37:33 +0530 janani-sankarababu wrote: > Signed-off-by: Janani S > > --- > init/main.c | 7 --- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff --git a/init/main.c b/init/main.c > index 052481f..f8eb4966 100644 >

Re: [PATCH] init:main.c: Fixed issues in Block comments and removed braces in single statement if block

On Fri, 28 Jul 2017 11:37:33 +0530 janani-sankarababu wrote: > Signed-off-by: Janani S > > --- > init/main.c | 7 --- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff --git a/init/main.c b/init/main.c > index 052481f..f8eb4966 100644 > --- a/init/main.c > +++ b/init/main.c > @@

[PATCH -tip v6] irq: Make irqentry text section unconditional

Generate irqentry and softirqentry text sections without any configs. This will add above extra sections, but no performace impact. Signed-off-by: Masami Hiramatsu Suggested-by: Ingo Molnar --- arch/arm/include/asm/traps.h |7 ---

[PATCH -tip v6] irq: Make irqentry text section unconditional

Generate irqentry and softirqentry text sections without any configs. This will add above extra sections, but no performace impact. Signed-off-by: Masami Hiramatsu Suggested-by: Ingo Molnar --- arch/arm/include/asm/traps.h |7 --- arch/arm64/include/asm/traps.h|7 ---

Re: [RFC PATCH 0/5] mm, memory_hotplug: allocate memmap from hotadded memory

On Thu 27-07-17 08:56:52, Michal Hocko wrote: > On Wed 26-07-17 17:06:59, Jerome Glisse wrote: > [...] > > This does not seems to be an opt-in change ie if i am reading patch 3 > > correctly if an altmap is not provided to __add_pages() you fallback > > to allocating from begining of zone. This

Re: [RFC PATCH 0/5] mm, memory_hotplug: allocate memmap from hotadded memory

On Thu 27-07-17 08:56:52, Michal Hocko wrote: > On Wed 26-07-17 17:06:59, Jerome Glisse wrote: > [...] > > This does not seems to be an opt-in change ie if i am reading patch 3 > > correctly if an altmap is not provided to __add_pages() you fallback > > to allocating from begining of zone. This

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

On Thu, 27 Jul 2017 20:22:32 -0700 "Paul E. McKenney" wrote: > On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > > On Mon, 24 Jul 2017 14:44:36 -0700 > > "Paul E. McKenney" wrote: > > > > > There is currently event

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

On Thu, 27 Jul 2017 20:22:32 -0700 "Paul E. McKenney" wrote: > On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > > On Mon, 24 Jul 2017 14:44:36 -0700 > > "Paul E. McKenney" wrote: > > > > > There is currently event tracing to track when a task is preempted > > > within a

Re: [PATCH V6] sched/fair: Remove group imbalance from calculate_imbalance()

On 26/07/17 15:54, Peter Zijlstra wrote: > On Tue, Jul 18, 2017 at 08:48:53PM +0100, Dietmar Eggemann wrote: >> Hi Jeffrey, >> >> On 13/07/17 20:55, Jeffrey Hugo wrote: [...] >>> Since the group imbalance path in calculate_imbalance() is at best a NOP >>> but otherwise harmful, remove it. > >

Re: [PATCH V6] sched/fair: Remove group imbalance from calculate_imbalance()

On 26/07/17 15:54, Peter Zijlstra wrote: > On Tue, Jul 18, 2017 at 08:48:53PM +0100, Dietmar Eggemann wrote: >> Hi Jeffrey, >> >> On 13/07/17 20:55, Jeffrey Hugo wrote: [...] >>> Since the group imbalance path in calculate_imbalance() is at best a NOP >>> but otherwise harmful, remove it. > >

Re: [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection

On Fri, 2017-07-28 at 13:53 +0200, Paolo Bonzini wrote: > On 28/07/2017 10:24, Mike Galbraith wrote: > > On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote: > >> With these two patches, KVM does not blindly pass the exit interruption > >> info and exit qualification from the vmcs02 and vmcs12

Re: [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection

On Fri, 2017-07-28 at 13:53 +0200, Paolo Bonzini wrote: > On 28/07/2017 10:24, Mike Galbraith wrote: > > On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote: > >> With these two patches, KVM does not blindly pass the exit interruption > >> info and exit qualification from the vmcs02 and vmcs12

Re: [RFC PATCH 0/5] mm, memory_hotplug: allocate memmap from hotadded memory

On Wed 26-07-17 10:33:28, Michal Hocko wrote: [...] > There is also one potential drawback, though. If somebody uses memory > hotplug for 1G (gigantic) hugetlb pages then this scheme will not work > for them obviously because each memory section will contain 2MB reserved > area. Actually I am

Re: [RFC PATCH 0/5] mm, memory_hotplug: allocate memmap from hotadded memory

On Wed 26-07-17 10:33:28, Michal Hocko wrote: [...] > There is also one potential drawback, though. If somebody uses memory > hotplug for 1G (gigantic) hugetlb pages then this scheme will not work > for them obviously because each memory section will contain 2MB reserved > area. Actually I am

Re: [PATCH 02/37] binder: use group leader instead of open thread

I took the time to look at what else is different between common and upstream, and just sent 3 patches to LKML to reconcile. One of the 3 fixes this particular problem. On Thu, Jul 27, 2017 at 3:42 PM, Amit Pundir wrote: > On 27 July 2017 at 18:53, Greg Kroah-Hartman

Re: [PATCH 02/37] binder: use group leader instead of open thread

I took the time to look at what else is different between common and upstream, and just sent 3 patches to LKML to reconcile. One of the 3 fixes this particular problem. On Thu, Jul 27, 2017 at 3:42 PM, Amit Pundir wrote: > On 27 July 2017 at 18:53, Greg Kroah-Hartman > wrote: >> On Thu, Jul

[PATCH 1/3] ANDROID: binder: add padding to binder_fd_array_object.

binder_fd_array_object starts with a 4-byte header, followed by a few fields that are 8 bytes when ANDROID_BINDER_IPC_32BIT=N. This can cause alignment issues in a 64-bit kernel with a 32-bit userspace, as on x86_32 an 8-byte primitive may be aligned to a 4-byte address. Pad with a __u32 to fix

[PATCH 1/3] ANDROID: binder: add padding to binder_fd_array_object.

binder_fd_array_object starts with a 4-byte header, followed by a few fields that are 8 bytes when ANDROID_BINDER_IPC_32BIT=N. This can cause alignment issues in a 64-bit kernel with a 32-bit userspace, as on x86_32 an 8-byte primitive may be aligned to a 4-byte address. Pad with a __u32 to fix

[PATCH 0/3] ANDROID: binder: reconcile with android common tree

When comparing the android common kernel branch with upstream, I found several differences. The "add padding" patch has long been applied in common, and shipping versions of Android userspace depends on this particular alignment; so while it does change UAPI, we have never shipped a userspace

[PATCH 3/3] ANDROID: binder: fix proc->tsk check.

Commit c4ea41ba195d ("binder: use group leader instead of open thread")' was incomplete and didn't update a check in binder_mmap(), causing all mmap() calls into the binder driver to fail. Signed-off-by: Martijn Coenen --- drivers/android/binder.c | 2 +- 1 file changed, 1

[PATCH 0/3] ANDROID: binder: reconcile with android common tree

When comparing the android common kernel branch with upstream, I found several differences. The "add padding" patch has long been applied in common, and shipping versions of Android userspace depends on this particular alignment; so while it does change UAPI, we have never shipped a userspace

[PATCH 3/3] ANDROID: binder: fix proc->tsk check.

Commit c4ea41ba195d ("binder: use group leader instead of open thread")' was incomplete and didn't update a check in binder_mmap(), causing all mmap() calls into the binder driver to fail. Signed-off-by: Martijn Coenen --- drivers/android/binder.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [RFC PATCH v2] membarrier: expedited private command

On Fri, Jul 28, 2017 at 10:55:32AM +0200, Peter Zijlstra wrote: > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > index e9785f7aed75..33f34a201255 100644 > --- a/kernel/sched/core.c > +++ b/kernel/sched/core.c > @@ -2641,8 +2641,18 @@ static struct rq *finish_task_switch(struct >

Re: [RFC PATCH v2] membarrier: expedited private command

On Fri, Jul 28, 2017 at 10:55:32AM +0200, Peter Zijlstra wrote: > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > index e9785f7aed75..33f34a201255 100644 > --- a/kernel/sched/core.c > +++ b/kernel/sched/core.c > @@ -2641,8 +2641,18 @@ static struct rq *finish_task_switch(struct >

[PATCH 2/3] ANDROID: binder: add hwbinder,vndbinder to BINDER_DEVICES.

These will be required going forward. Signed-off-by: Martijn Coenen --- drivers/android/Kconfig| 2 +- kernel/configs/android-base.config | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/android/Kconfig b/drivers/android/Kconfig index

[PATCH 2/3] ANDROID: binder: add hwbinder,vndbinder to BINDER_DEVICES.

These will be required going forward. Signed-off-by: Martijn Coenen --- drivers/android/Kconfig| 2 +- kernel/configs/android-base.config | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/android/Kconfig b/drivers/android/Kconfig index

Re: [PATCH] turbostat: Running on virtual machine is not supported

On 07/26/2017 11:09 PM, Len Brown wrote: > Henrique, > > I like your suggestion, thanks! > > BTW. let's discuss (and patch) turbostat on linux-pm, rather than on lkml. > > thanks, > -Len > > > On Tue, Jul 25, 2017 at 11:59 AM, Henrique de Moraes Holschuh > wrote: >> On

Re: [PATCH] turbostat: Running on virtual machine is not supported

On 07/26/2017 11:09 PM, Len Brown wrote: > Henrique, > > I like your suggestion, thanks! > > BTW. let's discuss (and patch) turbostat on linux-pm, rather than on lkml. > > thanks, > -Len > > > On Tue, Jul 25, 2017 at 11:59 AM, Henrique de Moraes Holschuh > wrote: >> On Tue, 25 Jul 2017,

RE: [PATCH V4 net-next 2/8] net: hns3: Add support of the HNAE3 framework

Hi Leon, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Leon Romanovsky > Sent: Friday, July 28, 2017 5:42 AM > To: Salil Mehta > Cc: da...@davemloft.net; Zhuangyuzeng (Yisen); huangdaode; lipeng (Y); >

RE: [PATCH V4 net-next 2/8] net: hns3: Add support of the HNAE3 framework

Hi Leon, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Leon Romanovsky > Sent: Friday, July 28, 2017 5:42 AM > To: Salil Mehta > Cc: da...@davemloft.net; Zhuangyuzeng (Yisen); huangdaode; lipeng (Y); >

Re: [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection

On 28/07/2017 10:24, Mike Galbraith wrote: > On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote: >> With these two patches, KVM does not blindly pass the exit interruption >> info and exit qualification from the vmcs02 and vmcs12 when injecting >> an exception. There were two spots where this

Re: [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection

On 28/07/2017 10:24, Mike Galbraith wrote: > On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote: >> With these two patches, KVM does not blindly pass the exit interruption >> info and exit qualification from the vmcs02 and vmcs12 when injecting >> an exception. There were two spots where this

Possible race condition in oom-killer

was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap Hi Michal, On 7/27/2017 2:54 PM, Michal Hocko wrote: On Thu 27-07-17 13:59:09, Manish Jaggi wrote: [...] With 4.11.6 I was getting random kernel panics (Out of memory - No process left to kill), when running LTP oom01 /oom02

Possible race condition in oom-killer

was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap Hi Michal, On 7/27/2017 2:54 PM, Michal Hocko wrote: On Thu 27-07-17 13:59:09, Manish Jaggi wrote: [...] With 4.11.6 I was getting random kernel panics (Out of memory - No process left to kill), when running LTP oom01 /oom02

[PATCH v5 2/2] arm64: dts: Add Mediatek SoC MT2712 and evaluation board dts and Makefile

This adds basic chip support for Mediatek 2712 Signed-off-by: YT Shen --- arch/arm64/boot/dts/mediatek/Makefile | 1 + arch/arm64/boot/dts/mediatek/mt2712-evb.dts | 32 + arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 178 3 files

[PATCH v5 2/2] arm64: dts: Add Mediatek SoC MT2712 and evaluation board dts and Makefile

This adds basic chip support for Mediatek 2712 Signed-off-by: YT Shen --- arch/arm64/boot/dts/mediatek/Makefile | 1 + arch/arm64/boot/dts/mediatek/mt2712-evb.dts | 32 + arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 178 3 files changed, 211

[PATCH v5 0/2] Add basic support for Mediatek MT2712 SoC

MT2712 is a SoC based on 64bit ARMv8 architecture. MT2712 share many HW IP with MT8173. This patchset was tested on MT2712 evaluation board, and boot to shell ok. This series contains document bindings, device tree including interrupt and uart. Changes compared to v4: - rebase to 4.13-rc1 -

[PATCH v5 1/2] dt-bindings: arm: Add bindings for Mediatek MT2712 SoC Platform

This adds dt-binding documentation for Mediatek MT2712. Only include very basic items: cpu, gic and uart. Signed-off-by: YT Shen Acked-by: Rob Herring --- Documentation/devicetree/bindings/arm/mediatek.txt| 4

[PATCH v5 0/2] Add basic support for Mediatek MT2712 SoC

MT2712 is a SoC based on 64bit ARMv8 architecture. MT2712 share many HW IP with MT8173. This patchset was tested on MT2712 evaluation board, and boot to shell ok. This series contains document bindings, device tree including interrupt and uart. Changes compared to v4: - rebase to 4.13-rc1 -

[PATCH v5 1/2] dt-bindings: arm: Add bindings for Mediatek MT2712 SoC Platform

This adds dt-binding documentation for Mediatek MT2712. Only include very basic items: cpu, gic and uart. Signed-off-by: YT Shen Acked-by: Rob Herring --- Documentation/devicetree/bindings/arm/mediatek.txt| 4

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On 07/28/17 at 01:18pm, Joerg Roedel wrote: > On Fri, Jul 28, 2017 at 07:15:53PM +0800, Baoquan He wrote: > > On 07/28/17 at 01:14pm, Joerg Roedel wrote: > > > Yes, exactly, the first device table also needs to be allocated with > > > GFP_DMA32 so that it ends up below 4GB. > > > > Got it, will

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On 07/28/17 at 01:18pm, Joerg Roedel wrote: > On Fri, Jul 28, 2017 at 07:15:53PM +0800, Baoquan He wrote: > > On 07/28/17 at 01:14pm, Joerg Roedel wrote: > > > Yes, exactly, the first device table also needs to be allocated with > > > GFP_DMA32 so that it ends up below 4GB. > > > > Got it, will

Re: [RFC PATCH 3/5] mm, memory_hotplug: allocate memmap from the added memory range for sparse-vmemmap

On Wed 26-07-17 19:20:39, Gerald Schaefer wrote: > On Wed, 26 Jul 2017 14:30:41 +0200 > Michal Hocko wrote: > > > On Wed 26-07-17 13:45:39, Heiko Carstens wrote: > > [...] > > > In general I do like your idea, however if I understand your patches > > > correctly we might have

Re: [RFC PATCH 3/5] mm, memory_hotplug: allocate memmap from the added memory range for sparse-vmemmap

On Wed 26-07-17 19:20:39, Gerald Schaefer wrote: > On Wed, 26 Jul 2017 14:30:41 +0200 > Michal Hocko wrote: > > > On Wed 26-07-17 13:45:39, Heiko Carstens wrote: > > [...] > > > In general I do like your idea, however if I understand your patches > > > correctly we might have an ordering problem

Re: [PATCH v6 RESEND] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions

Hi Matt, On 07/28/17 at 11:55am, Ingo Molnar wrote: > > * Matt Fleming wrote: > > > On Fri, 21 Jul, at 09:19:56PM, Baoquan He wrote: > > > > > > There are places where the efi map is getting and used like this. E.g > > > in efi_high_alloc() of

Re: [PATCH v6 RESEND] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions

Hi Matt, On 07/28/17 at 11:55am, Ingo Molnar wrote: > > * Matt Fleming wrote: > > > On Fri, 21 Jul, at 09:19:56PM, Baoquan He wrote: > > > > > > There are places where the efi map is getting and used like this. E.g > > > in efi_high_alloc() of drivers/firmware/efi/libstub/efi-stub-helper.c. >

two more objtool warnings: lib/ubsan.o and fs/fs_pin.o

Hi Josh, I ran into two more warnings with the two patches you sent me in private, using gcc-7.1.1: lib/ubsan.o: warning: objtool: val_to_string.constprop.7()+0x97: leave instruction with modified stack frame .config: https://pastebin.com/dl/g04Dwdwx fs/fs_pin.o: warning: objtool:

two more objtool warnings: lib/ubsan.o and fs/fs_pin.o

Hi Josh, I ran into two more warnings with the two patches you sent me in private, using gcc-7.1.1: lib/ubsan.o: warning: objtool: val_to_string.constprop.7()+0x97: leave instruction with modified stack frame .config: https://pastebin.com/dl/g04Dwdwx fs/fs_pin.o: warning: objtool:

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On Fri, Jul 28, 2017 at 07:15:53PM +0800, Baoquan He wrote: > On 07/28/17 at 01:14pm, Joerg Roedel wrote: > > Yes, exactly, the first device table also needs to be allocated with > > GFP_DMA32 so that it ends up below 4GB. > > Got it, will do. Thanks! Oh, and you also need to check in the kdump

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On Fri, Jul 28, 2017 at 07:15:53PM +0800, Baoquan He wrote: > On 07/28/17 at 01:14pm, Joerg Roedel wrote: > > Yes, exactly, the first device table also needs to be allocated with > > GFP_DMA32 so that it ends up below 4GB. > > Got it, will do. Thanks! Oh, and you also need to check in the kdump

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On 07/28/17 at 01:14pm, Joerg Roedel wrote: > On Fri, Jul 28, 2017 at 05:06:19PM +0800, Baoquan He wrote: > > Do you mean the allocation of amd_iommu_dev_table in > > early_amd_iommu_init() also need be addressed for 1st kernel? Seems we > > don't make sure that for 1st kernel, like adding

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On 07/28/17 at 01:14pm, Joerg Roedel wrote: > On Fri, Jul 28, 2017 at 05:06:19PM +0800, Baoquan He wrote: > > Do you mean the allocation of amd_iommu_dev_table in > > early_amd_iommu_init() also need be addressed for 1st kernel? Seems we > > don't make sure that for 1st kernel, like adding

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On Fri, Jul 28, 2017 at 05:06:19PM +0800, Baoquan He wrote: > Do you mean the allocation of amd_iommu_dev_table in > early_amd_iommu_init() also need be addressed for 1st kernel? Seems we > don't make sure that for 1st kernel, like adding GFP_DMA32 flag when > allocate amd_iommu_dev_table in

Re: [PATCH v8 10/13] iommu/amd: Allocate memory below 4G for dev table if translation pre-enabled

On Fri, Jul 28, 2017 at 05:06:19PM +0800, Baoquan He wrote: > Do you mean the allocation of amd_iommu_dev_table in > early_amd_iommu_init() also need be addressed for 1st kernel? Seems we > don't make sure that for 1st kernel, like adding GFP_DMA32 flag when > allocate amd_iommu_dev_table in

Re: [RFC PATCH v2] membarrier: expedited private command

On Fri, Jul 28, 2017 at 10:55:32AM +0200, Peter Zijlstra wrote: > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > index e9785f7aed75..33f34a201255 100644 > --- a/kernel/sched/core.c > +++ b/kernel/sched/core.c > @@ -2641,8 +2641,18 @@ static struct rq *finish_task_switch(struct >

Re: [RFC PATCH v2] membarrier: expedited private command

On Fri, Jul 28, 2017 at 10:55:32AM +0200, Peter Zijlstra wrote: > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > index e9785f7aed75..33f34a201255 100644 > --- a/kernel/sched/core.c > +++ b/kernel/sched/core.c > @@ -2641,8 +2641,18 @@ static struct rq *finish_task_switch(struct >

Re: [PATCH 09/15] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v6

I haven't seen a newer version posted but the same comment applies on your hmm-v25-4.9 git version from git://people.freedesktop.org/~glisse/linux On Wed 28-06-17 14:00:41, Jérôme Glisse wrote: > This introduce a simple struct and associated helpers for device driver > to use when hotpluging

Re: [PATCH 09/15] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v6

I haven't seen a newer version posted but the same comment applies on your hmm-v25-4.9 git version from git://people.freedesktop.org/~glisse/linux On Wed 28-06-17 14:00:41, Jérôme Glisse wrote: > This introduce a simple struct and associated helpers for device driver > to use when hotpluging

Re: [PATCH net-next v2 01/10] net: dsa: lan9303: Fixed MDIO interface

On 26. juli 2017 18:55, Andrew Lunn wrote: On Tue, Jul 25, 2017 at 06:15:44PM +0200, Egil Hjelmeland wrote: It is better to use mdiobus_read/write or if you are nesting mdio busses, mdiobus_read_nested/mdiobus_write_nested. Please test this code with lockdep enabled. I have

Re: [PATCH net-next v2 01/10] net: dsa: lan9303: Fixed MDIO interface

On 26. juli 2017 18:55, Andrew Lunn wrote: On Tue, Jul 25, 2017 at 06:15:44PM +0200, Egil Hjelmeland wrote: It is better to use mdiobus_read/write or if you are nesting mdio busses, mdiobus_read_nested/mdiobus_write_nested. Please test this code with lockdep enabled. I have

Re: [PATCH 3/4] lib/scatterlist: Introduce and export __sg_alloc_table_from_pages

Quoting Tvrtko Ursulin (2017-07-27 10:05:03) > From: Tvrtko Ursulin > > Drivers like i915 benefit from being able to control the maxium > size of the sg coallesced segment while building the scatter- > gather list. > > Introduce and export the

Re: [PATCH 3/4] lib/scatterlist: Introduce and export __sg_alloc_table_from_pages

Quoting Tvrtko Ursulin (2017-07-27 10:05:03) > From: Tvrtko Ursulin > > Drivers like i915 benefit from being able to control the maxium > size of the sg coallesced segment while building the scatter- > gather list. > > Introduce and export the __sg_alloc_table_from_pages function > which will

Re: [PATCH 4/4] drm/i915: Use __sg_alloc_table_from_pages for userptr allocations

Quoting Tvrtko Ursulin (2017-07-27 10:05:04) > From: Tvrtko Ursulin > > With the addition of __sg_alloc_table_from_pages we can control > the maximum coallescing size and eliminate a separate path for > allocating backing store here. > > Similar to 871dfbd67d4e

Re: [PATCH 4/4] drm/i915: Use __sg_alloc_table_from_pages for userptr allocations

Quoting Tvrtko Ursulin (2017-07-27 10:05:04) > From: Tvrtko Ursulin > > With the addition of __sg_alloc_table_from_pages we can control > the maximum coallescing size and eliminate a separate path for > allocating backing store here. > > Similar to 871dfbd67d4e ("drm/i915: Allow compaction upto

Re: [PATCH v2] staging:wlan-ng Correct multiple line dereference

>From header. Subject. Doesn't apply (read Documentation/process/email-clients.rst). On Fri, Jul 28, 2017 at 04:14:29PM +0530, janani-sankarababu wrote: > This patch fixes the multiple line dereference Warning reported by > checkpath script. This has been made to simplify the code and make >

Re: [PATCH v2] staging:wlan-ng Correct multiple line dereference

>From header. Subject. Doesn't apply (read Documentation/process/email-clients.rst). On Fri, Jul 28, 2017 at 04:14:29PM +0530, janani-sankarababu wrote: > This patch fixes the multiple line dereference Warning reported by > checkpath script. This has been made to simplify the code and make >

<    6   7   8   9   10   11   12   13   14   15   >