[PATCH v4 2/3] KVM: add converters between pfn_t and kvm_pfn_t

Signed-off-by: Haozhong Zhang --- include/linux/kvm_host.h | 4 1 file changed, 4 insertions(+) diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h index 6882538eda32..caf6f7a6bdb2 100644 --- a/include/linux/kvm_host.h +++ b/include/linux/kvm_host.h

[PATCH v4 3/3] KVM: MMU: consider host cache mode in MMIO page check

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

[PATCH v4 2/3] KVM: add converters between pfn_t and kvm_pfn_t

Signed-off-by: Haozhong Zhang --- include/linux/kvm_host.h | 4 1 file changed, 4 insertions(+) diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h index 6882538eda32..caf6f7a6bdb2 100644 --- a/include/linux/kvm_host.h +++ b/include/linux/kvm_host.h @@ -27,6 +27,7 @@ #include

[PATCH v4 3/3] KVM: MMU: consider host cache mode in MMIO page check

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

[PATCH v4 1/3] x86/mm: add function to check if a pfn is UC/UC-

pat_pfn_is_uc(pfn) is added and will be used by KVM to check whether the memory type of a host pfn is UC/UC-. Signed-off-by: Haozhong Zhang --- arch/x86/include/asm/pat.h | 2 ++ arch/x86/mm/pat.c | 14 ++ 2 files changed, 16 insertions(+) diff

[PATCH v4 0/3] KVM: MMU: fix kvm_is_mmio_pfn()

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

[PATCH v4 1/3] x86/mm: add function to check if a pfn is UC/UC-

pat_pfn_is_uc(pfn) is added and will be used by KVM to check whether the memory type of a host pfn is UC/UC-. Signed-off-by: Haozhong Zhang --- arch/x86/include/asm/pat.h | 2 ++ arch/x86/mm/pat.c | 14 ++ 2 files changed, 16 insertions(+) diff --git

[PATCH v4 0/3] KVM: MMU: fix kvm_is_mmio_pfn()

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

Re: [f2fs-dev] [PATCH 2/2] f2fs: support quota sys files

On 2017/11/3 11:37, Jaegeuk Kim wrote: > On 11/02, Chao Yu wrote: >> On 2017/10/31 11:40, Jaegeuk Kim wrote: >>> This patch supports hidden quota files in the system, which will be used for >>> Android. It requires up-to-date f2fs-tools later than v1.9.0. >>> >>> Signed-off-by: Jaegeuk Kim

Re: [f2fs-dev] [PATCH 2/2] f2fs: support quota sys files

On 2017/11/3 11:37, Jaegeuk Kim wrote: > On 11/02, Chao Yu wrote: >> On 2017/10/31 11:40, Jaegeuk Kim wrote: >>> This patch supports hidden quota files in the system, which will be used for >>> Android. It requires up-to-date f2fs-tools later than v1.9.0. >>> >>> Signed-off-by: Jaegeuk Kim >>>

[GIT] Networking

Hopefully this is the last batch of networking fixes for 4.14 Fingers crossed... 1) Fix stmmac to use the proper sized OF property read, from Bhadram Varka. 2) Fix use after free in net scheduler tc action code, from Cong Wang. 3) Fix SKB control block mangling in tcp_make_synack(). 4)

[GIT] Networking

Hopefully this is the last batch of networking fixes for 4.14 Fingers crossed... 1) Fix stmmac to use the proper sized OF property read, from Bhadram Varka. 2) Fix use after free in net scheduler tc action code, from Cong Wang. 3) Fix SKB control block mangling in tcp_make_synack(). 4)

linux-next: build warnings after merge of the gpio tree

Hi Linus, After merging the gpio tree, yesterday's linux-next build (arm multi_v7_defconfig) produced these warnings: arch/arm/boot/dts/bcm2835-rpi-b.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e98:phys[0])

linux-next: build warnings after merge of the gpio tree

Hi Linus, After merging the gpio tree, yesterday's linux-next build (arm multi_v7_defconfig) produced these warnings: arch/arm/boot/dts/bcm2835-rpi-b.dtb: Warning (phys_property): Missing property '#phy-cells' in node /phy or bad phandle (referred from /soc/usb@7e98:phys[0])

Re: [PATCH net-next] net: Define eth_stp_addr in linux/etherdevice.h

From: Egil Hjelmeland Date: Thu, 2 Nov 2017 10:36:48 +0100 > The lan9303 driver defines eth_stp_addr as a synonym to > eth_reserved_addr_base to get the STP ethernet address 01:80:c2:00:00:00. > > eth_reserved_addr_base is also used to define the start of Bridge

Re: [PATCH net-next] net: Define eth_stp_addr in linux/etherdevice.h

From: Egil Hjelmeland Date: Thu, 2 Nov 2017 10:36:48 +0100 > The lan9303 driver defines eth_stp_addr as a synonym to > eth_reserved_addr_base to get the STP ethernet address 01:80:c2:00:00:00. > > eth_reserved_addr_base is also used to define the start of Bridge Reserved > ethernet address

Re: [PATCH 1/2] [net-next] bpf: fix link error without CONFIG_NET

From: Arnd Bergmann Date: Thu, 2 Nov 2017 12:05:51 +0100 > I ran into this link error with the latest net-next plus linux-next > trees when networking is disabled: > > kernel/bpf/verifier.o:(.rodata+0x2958): undefined reference to > `tc_cls_act_analyzer_ops' >

Re: [PATCH 1/2] [net-next] bpf: fix link error without CONFIG_NET

From: Arnd Bergmann Date: Thu, 2 Nov 2017 12:05:51 +0100 > I ran into this link error with the latest net-next plus linux-next > trees when networking is disabled: > > kernel/bpf/verifier.o:(.rodata+0x2958): undefined reference to > `tc_cls_act_analyzer_ops' >

Re: [PATCH 2/2] [net-next] bpf: fix out-of-bounds access warning in bpf_check

From: Arnd Bergmann Date: Thu, 2 Nov 2017 12:05:52 +0100 > The bpf_verifer_ops array is generated dynamically and may be > empty depending on configuration, which then causes an out > of bounds access: > > kernel/bpf/verifier.c: In function 'bpf_check': >

Re: [PATCH 2/2] [net-next] bpf: fix out-of-bounds access warning in bpf_check

From: Arnd Bergmann Date: Thu, 2 Nov 2017 12:05:52 +0100 > The bpf_verifer_ops array is generated dynamically and may be > empty depending on configuration, which then causes an out > of bounds access: > > kernel/bpf/verifier.c: In function 'bpf_check': > kernel/bpf/verifier.c:4320:29: error:

Re: [PATCH V9 1/4] dma-mapping: Rework dma_get_cache_alignment()

I can queue 1 up in the dma-mapping tree, and if I get reviews for the mips and scsi bits I'd be happy to queue those up as well. But I think you'd be better off moving patches 3 and 4 to the front without the dma_get_cache_alignment prototype change so that they can be merged to stable.

Re: [PATCH V9 1/4] dma-mapping: Rework dma_get_cache_alignment()

I can queue 1 up in the dma-mapping tree, and if I get reviews for the mips and scsi bits I'd be happy to queue those up as well. But I think you'd be better off moving patches 3 and 4 to the front without the dma_get_cache_alignment prototype change so that they can be merged to stable.

Re: [PATCH] ARM: multi_v7_defconfig: Select RPMSG_VIRTIO as module

On Thu 05 Oct 09:49 PDT 2017, Anup Patel wrote: > The RPMSG_VIRTIO is now user selectable option so we explicitly > select it in multi_v7_defconfig. Till now RPMSG_VIRTIO was > selected by ST_REMOTEPROC=m in multi_v7_defconfig. > Acked-by: Bjorn Andersson >

Re: [PATCH] ARM: multi_v7_defconfig: Select RPMSG_VIRTIO as module

On Thu 05 Oct 09:49 PDT 2017, Anup Patel wrote: > The RPMSG_VIRTIO is now user selectable option so we explicitly > select it in multi_v7_defconfig. Till now RPMSG_VIRTIO was > selected by ST_REMOTEPROC=m in multi_v7_defconfig. > Acked-by: Bjorn Andersson > Signed-off-by: Anup Patel

Re: [PATCH V8 0/2] printk: hash addresses printed with %p

On Tue, Oct 31, 2017 at 04:33:13PM -0700, Joe Perches wrote: > On Wed, 2017-11-01 at 10:16 +1100, Tobin C. Harding wrote: > > Cool, thanks Joe I'll keep this in mind for when we get to %pa. > > fyi: There are more of these misuses of 0x%pa now: > > $ git grep -E -n "0[xX]%pa[dp]?\b" >

Re: [PATCH V8 0/2] printk: hash addresses printed with %p

On Tue, Oct 31, 2017 at 04:33:13PM -0700, Joe Perches wrote: > On Wed, 2017-11-01 at 10:16 +1100, Tobin C. Harding wrote: > > Cool, thanks Joe I'll keep this in mind for when we get to %pa. > > fyi: There are more of these misuses of 0x%pa now: > > $ git grep -E -n "0[xX]%pa[dp]?\b" >

Re: [PATCH] ARM: multi_v7_defconfig: Select RPMSG_VIRTIO as module

On Thu, Oct 26, 2017 at 9:33 PM, Anup Patel wrote: > On Thu, Oct 5, 2017 at 10:19 PM, Anup Patel wrote: >> The RPMSG_VIRTIO is now user selectable option so we explicitly >> select it in multi_v7_defconfig. Till now RPMSG_VIRTIO was >> selected by

Re: [PATCH] ARM: multi_v7_defconfig: Select RPMSG_VIRTIO as module

On Thu, Oct 26, 2017 at 9:33 PM, Anup Patel wrote: > On Thu, Oct 5, 2017 at 10:19 PM, Anup Patel wrote: >> The RPMSG_VIRTIO is now user selectable option so we explicitly >> select it in multi_v7_defconfig. Till now RPMSG_VIRTIO was >> selected by ST_REMOTEPROC=m in multi_v7_defconfig. >> >>

Re: [PATCH 3/3] openrisc: dts: Add OpenRISC platform SoC

On Sun, Oct 22, 2017 at 11:46:41AM +0900, Stafford Horne wrote: > Add devicetree binding documentation for the OpenRISC platform > opencores,or1ksim. This is the main OpenRISC reference platform > supporting multiple FPGA SoC's. > > This format is based on some of the mips binding docs as we

Re: [PATCH 3/3] openrisc: dts: Add OpenRISC platform SoC

On Sun, Oct 22, 2017 at 11:46:41AM +0900, Stafford Horne wrote: > Add devicetree binding documentation for the OpenRISC platform > opencores,or1ksim. This is the main OpenRISC reference platform > supporting multiple FPGA SoC's. > > This format is based on some of the mips binding docs as we

[lkp-robot] [kprobes/x86] b664d57f39: BUG:using_smp_processor_id()in_preemptible

FYI, we noticed the following commit (built with gcc-4.9): commit: b664d57f39d01e775204d4f1a7e2f8bda77bc549 ("kprobes/x86: Remove IRQ disabling from jprobe handlers") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: boot on test machine: qemu-system-x86_64

[lkp-robot] [kprobes/x86] b664d57f39: BUG:using_smp_processor_id()in_preemptible

FYI, we noticed the following commit (built with gcc-4.9): commit: b664d57f39d01e775204d4f1a7e2f8bda77bc549 ("kprobes/x86: Remove IRQ disabling from jprobe handlers") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: boot on test machine: qemu-system-x86_64

[PATCH v4 6/6] pmbus: max31785: Add dual tachometer support

The dual tachometer feature is implemented in hardware with a TACHSEL input to indicate the rotor under measurement, and exposed on the device by extending the READ_FAN_SPEED_1 word with two extra bytes*. The need to read the non-standard four-byte response leads to a cut-down implementation of

[PATCH v4 6/6] pmbus: max31785: Add dual tachometer support

The dual tachometer feature is implemented in hardware with a TACHSEL input to indicate the rotor under measurement, and exposed on the device by extending the READ_FAN_SPEED_1 word with two extra bytes*. The need to read the non-standard four-byte response leads to a cut-down implementation of

[PATCH v4 5/6] pmbus: core: Add virtual page config bit

Some circumstances call for virtual pages to expose multiple values packed into an extended PMBus register in a manner non-compliant with the PMBus standard. We should not try to set virtual pages on the device; add a flag so we can avoid doing so. Signed-off-by: Andrew Jeffery

[PATCH v4 5/6] pmbus: core: Add virtual page config bit

Some circumstances call for virtual pages to expose multiple values packed into an extended PMBus register in a manner non-compliant with the PMBus standard. We should not try to set virtual pages on the device; add a flag so we can avoid doing so. Signed-off-by: Andrew Jeffery ---

[PATCH v4 3/6] pmbus: core: Add fan control support

Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes. Fans in a PMBus device are driven by the configuration of two registers: FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan and the tacho operate (if installed), while FAN_COMMAND_x sets the desired fan rate. The

[PATCH v4 3/6] pmbus: core: Add fan control support

Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes. Fans in a PMBus device are driven by the configuration of two registers: FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan and the tacho operate (if installed), while FAN_COMMAND_x sets the desired fan rate. The

[PATCH v4 2/6] pmbus: Add driver for Maxim MAX31785 Intelligent Fan Controller

The Maxim MAX31785 is a PMBus device providing closed-loop, multi-channel fan management with temperature and remote voltage sensing. Various fan control features are provided, including PWM frequency control, temperature hysteresis, dual tachometer measurements, and fan health monitoring. This

[PATCH v4 2/6] pmbus: Add driver for Maxim MAX31785 Intelligent Fan Controller

The Maxim MAX31785 is a PMBus device providing closed-loop, multi-channel fan management with temperature and remote voltage sensing. Various fan control features are provided, including PWM frequency control, temperature hysteresis, dual tachometer measurements, and fan health monitoring. This

[PATCH v4 4/6] pmbus: max31785: Add fan control

The implementation makes use of the new fan control virtual registers exposed by the pmbus core. It mixes use of the default implementations with some overrides via the read/write handlers to handle FAN_COMMAND_1 on the MAX31785, whose definition breaks the value range into various control bands

[PATCH v4 4/6] pmbus: max31785: Add fan control

The implementation makes use of the new fan control virtual registers exposed by the pmbus core. It mixes use of the default implementations with some overrides via the read/write handlers to handle FAN_COMMAND_1 on the MAX31785, whose definition breaks the value range into various control bands

Re: [PATCH v2] f2fs: fix out-of-free problem caused by atomic write

Because I found that it will still lead to out-of-free problem with out that check. I trace and find that it is possible that the committing date pages of the atomic file is bigger than the sbi->user_block_count - valid_user_blocks(sbi), so I add this check. On 2017/11/3 11:46, Jaegeuk Kim

Re: [PATCH v2] f2fs: fix out-of-free problem caused by atomic write

Because I found that it will still lead to out-of-free problem with out that check. I trace and find that it is possible that the committing date pages of the atomic file is bigger than the sbi->user_block_count - valid_user_blocks(sbi), so I add this check. On 2017/11/3 11:46, Jaegeuk Kim

[PATCH v4 1/6] dt-bindings: pmbus: Add Maxim MAX31785 documentation

Signed-off-by: Andrew Jeffery --- .../devicetree/bindings/hwmon/max31785.txt | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 Documentation/devicetree/bindings/hwmon/max31785.txt diff --git

[PATCH v4 1/6] dt-bindings: pmbus: Add Maxim MAX31785 documentation

Signed-off-by: Andrew Jeffery --- .../devicetree/bindings/hwmon/max31785.txt | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 Documentation/devicetree/bindings/hwmon/max31785.txt diff --git a/Documentation/devicetree/bindings/hwmon/max31785.txt

[PATCH v4 0/6] pmbus: Expand fan support and add MAX31785 driver

Hello, This series introduces support for the MAX31785 intelligent fan controller, a PMBus device providing closed-loop fan control among a number of other features. Along the way the series adds support to control fans and create virtual pages to the PMBus core, the latter to support some of the

[PATCH v4 0/6] pmbus: Expand fan support and add MAX31785 driver

Hello, This series introduces support for the MAX31785 intelligent fan controller, a PMBus device providing closed-loop fan control among a number of other features. Along the way the series adds support to control fans and create virtual pages to the PMBus core, the latter to support some of the

[git pull] drm fixes for v4.14-rc8

Hi Linus, One nouveau regression fix, Some amdgpu fixes for stable to fix hangs on some harvested Polaris GPUs A set of KASAN and regression fixes for i915, their CI system seems to be working pretty well now. Dave. The following changes since commit 0b07194bb55ed836c2cc7c22e866b87a14681984:

[git pull] drm fixes for v4.14-rc8

Hi Linus, One nouveau regression fix, Some amdgpu fixes for stable to fix hangs on some harvested Polaris GPUs A set of KASAN and regression fixes for i915, their CI system seems to be working pretty well now. Dave. The following changes since commit 0b07194bb55ed836c2cc7c22e866b87a14681984:

Re: [PATCH V9 1/4] dma-mapping: Rework dma_get_cache_alignment()

Why this is still un-merged? Should I remove the cc-stable and resend this series? Huacai -- Original -- From: "陈华才"; Date: Thu, Oct 26, 2017 02:33 PM To: "Marek Szyprowski"; "Christoph Hellwig";

Re: [PATCH V9 1/4] dma-mapping: Rework dma_get_cache_alignment()

Why this is still un-merged? Should I remove the cc-stable and resend this series? Huacai -- Original -- From: "陈华才"; Date: Thu, Oct 26, 2017 02:33 PM To: "Marek Szyprowski"; "Christoph Hellwig"; Cc: "Robin Murphy"; "Andrew Morton"; "Fuxin Zhang";

Re: [PATCHv5 1/1] [tools/selftests]: android/ion: userspace test utility for ion buffer sharing

On Fri, Nov 3, 2017 at 6:02 AM, Shuah Khan wrote: > On 11/02/2017 05:54 PM, Laura Abbott wrote: >> On 11/02/2017 10:53 AM, Shuah Khan wrote: >>> On 11/02/2017 10:19 AM, Shuah Khan wrote: On 11/02/2017 10:15 AM, Pintu Kumar wrote: > On Thu, Nov 2, 2017 at 8:37 PM,

Re: [PATCHv5 1/1] [tools/selftests]: android/ion: userspace test utility for ion buffer sharing

On Fri, Nov 3, 2017 at 6:02 AM, Shuah Khan wrote: > On 11/02/2017 05:54 PM, Laura Abbott wrote: >> On 11/02/2017 10:53 AM, Shuah Khan wrote: >>> On 11/02/2017 10:19 AM, Shuah Khan wrote: On 11/02/2017 10:15 AM, Pintu Kumar wrote: > On Thu, Nov 2, 2017 at 8:37 PM, Shuah Khan wrote:

RE: [PATCH v9 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

Hi Leon, I understand this fixes correctly freeing the v4l control handlers in probe(). But if there is a scenario where the sensor is mounted on a removable daughter card, shouldn't the probe fail if the daughter card is not connected? A sample read/write to an IMX274 register should be

RE: [PATCH v9 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

Hi Leon, I understand this fixes correctly freeing the v4l control handlers in probe(). But if there is a scenario where the sensor is mounted on a removable daughter card, shouldn't the probe fail if the daughter card is not connected? A sample read/write to an IMX274 register should be

[PATCH for-next] openrisc: fix possible deadlock scenario during timer sync

OpenRISC borrows its timer sync logic from MIPS, Matt helped to review the OpenRISC implementation and noted that we may suffer the same deadlock case that MIPS has faced. The case being: "the MIPS timer synchronization code contained the possibility of deadlock. If you mark a CPU online

[PATCH for-next] openrisc: fix possible deadlock scenario during timer sync

OpenRISC borrows its timer sync logic from MIPS, Matt helped to review the OpenRISC implementation and noted that we may suffer the same deadlock case that MIPS has faced. The case being: "the MIPS timer synchronization code contained the possibility of deadlock. If you mark a CPU online

next-20171102: ARM64 dies on boot

Hi all, I reproduce it with qemu. The exact reason of panic is the NULL-dereference in memory_present: (gdb) bt #0 0x08dd8c6c in sparse_index_init (nid=, section_nr=) at mm/sparse.c:80 #1 memory_present (nid=0, start=18446462598881083392, end=0) at mm/sparse.c:215 #2

next-20171102: ARM64 dies on boot

Hi all, I reproduce it with qemu. The exact reason of panic is the NULL-dereference in memory_present: (gdb) bt #0 0x08dd8c6c in sparse_index_init (nid=, section_nr=) at mm/sparse.c:80 #1 memory_present (nid=0, start=18446462598881083392, end=0) at mm/sparse.c:215 #2

Re: [PATCH v2] f2fs: fix out-of-free problem caused by atomic write

ping... On 2017/10/30 21:04, Yunlong Song wrote: f2fs_balance_fs only actives once in the commit_inmem_pages, but there are more than one page to commit, so all the other pages will miss the check. This will lead to out-of-free problem when commit a very large file. However, we cannot do

Re: [PATCH v2] f2fs: fix out-of-free problem caused by atomic write

ping... On 2017/10/30 21:04, Yunlong Song wrote: f2fs_balance_fs only actives once in the commit_inmem_pages, but there are more than one page to commit, so all the other pages will miss the check. This will lead to out-of-free problem when commit a very large file. However, we cannot do

[PATCH 1/3] arm64: Define cputype macros for Falkor CPU

Add cputype definition macros for Qualcomm Datacenter Technologies Falkor CPU in cputype.h. It's unfortunate that the first revision of the Falkor CPU used the wrong part number 0x800, got fixed in v2 chip with part number 0xC00, and would be used the same value for future revisions.

Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

ping... On 2017/10/13 21:31, Yunlong Song wrote: This can help us to debug on some corner case. Signed-off-by: Yunlong Song Signed-off-by: Chao Yu --- fs/f2fs/gc.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

Re: mptsas driver cannot detect hotplugging disk with the LSI SCSI SAS1068 controller in Ubuntu guest on VMware

On Sat, Oct 28, 2017 at 11:35 AM, Gavin Guo wrote: > On Fri, Oct 27, 2017 at 10:53 PM, Hannes Reinecke wrote: >> On 10/27/2017 04:02 PM, Gavin Guo wrote: >>> Hi Hannes, >>> >>> Thank you for looking into the issue. If there is anything I can help >>> to

[tip:x86/asm 24/32] mm/migrate.o: warning: objtool: migrate_misplaced_transhuge_page()+0x71: unreachable instruction

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/asm head: 1e4c4f610f774df6088d7c065b2dd4d22adba698 commit: da51da189a24bb9b7e2d5a123be096e51a4695a5 [24/32] x86/entry/64: Pass SP0 directly to load_sp0() config: x86_64-randconfig-in0-11031034 (attached as .config)

[PATCH 1/3] arm64: Define cputype macros for Falkor CPU

Add cputype definition macros for Qualcomm Datacenter Technologies Falkor CPU in cputype.h. It's unfortunate that the first revision of the Falkor CPU used the wrong part number 0x800, got fixed in v2 chip with part number 0xC00, and would be used the same value for future revisions.

Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

ping... On 2017/10/13 21:31, Yunlong Song wrote: This can help us to debug on some corner case. Signed-off-by: Yunlong Song Signed-off-by: Chao Yu --- fs/f2fs/gc.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c index 197ebf4..2b03202

Re: mptsas driver cannot detect hotplugging disk with the LSI SCSI SAS1068 controller in Ubuntu guest on VMware

On Sat, Oct 28, 2017 at 11:35 AM, Gavin Guo wrote: > On Fri, Oct 27, 2017 at 10:53 PM, Hannes Reinecke wrote: >> On 10/27/2017 04:02 PM, Gavin Guo wrote: >>> Hi Hannes, >>> >>> Thank you for looking into the issue. If there is anything I can help >>> to test the patch? I appreciate your help.

[tip:x86/asm 24/32] mm/migrate.o: warning: objtool: migrate_misplaced_transhuge_page()+0x71: unreachable instruction

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/asm head: 1e4c4f610f774df6088d7c065b2dd4d22adba698 commit: da51da189a24bb9b7e2d5a123be096e51a4695a5 [24/32] x86/entry/64: Pass SP0 directly to load_sp0() config: x86_64-randconfig-in0-11031034 (attached as .config)

[PATCH 2/3] arm64: Prepare SCTLR_ELn accesses to handle Falkor erratum 1041

This patch introduces two helper macros read_sctlr and write_sctlr to access system register SCTLR_ELn. Replace all MSR/MRS references to sctlr_el1{el2} with macros. This should cause no behavioral change. Signed-off-by: Shanker Donthineni ---

[PATCH 2/3] arm64: Prepare SCTLR_ELn accesses to handle Falkor erratum 1041

This patch introduces two helper macros read_sctlr and write_sctlr to access system register SCTLR_ELn. Replace all MSR/MRS references to sctlr_el1{el2} with macros. This should cause no behavioral change. Signed-off-by: Shanker Donthineni --- arch/arm64/include/asm/assembler.h | 18

[PATCH 3/3] arm64: Add software workaround for Falkor erratum 1041

The ARM architecture defines the memory locations that are permitted to be accessed as the result of a speculative instruction fetch from an exception level for which all stages of translation are disabled. Specifically, the core is permitted to speculatively fetch from the 4KB region containing

[PATCH 3/3] arm64: Add software workaround for Falkor erratum 1041

The ARM architecture defines the memory locations that are permitted to be accessed as the result of a speculative instruction fetch from an exception level for which all stages of translation are disabled. Specifically, the core is permitted to speculatively fetch from the 4KB region containing

[PATCH 0/3] Implement a software workaround for Falkor erratum 1041

On Falkor CPU, we’ve discovered a hardware issue which might lead to a kernel crash or the unexpected behavior. The Falkor core may errantly access memory locations on speculative instruction fetches. This may happen whenever MMU translation state, SCTLR_ELn[M] bit is being changed from enabled to

[PATCH 0/3] Implement a software workaround for Falkor erratum 1041

On Falkor CPU, we’ve discovered a hardware issue which might lead to a kernel crash or the unexpected behavior. The Falkor core may errantly access memory locations on speculative instruction fetches. This may happen whenever MMU translation state, SCTLR_ELn[M] bit is being changed from enabled to

MAP_SYNC in libnvdimm-for-next and collision fixups

/git/djbw/nvdimm.git/log/?h= libnvdimm-vs-next-20171102 --- commit 2adeca04276acb4e747dbe7a5668efe03b164566 Merge: fa8785e862ef c29c91a9daa3 Author: Dan Williams <dan.j.willi...@intel.com> Date: Thu Nov 2 19:20:59 2017 -0700 Merge branch 'libnvdimm-for-next' into test diff --cc fs/dax.c

MAP_SYNC in libnvdimm-for-next and collision fixups

/git/djbw/nvdimm.git/log/?h= libnvdimm-vs-next-20171102 --- commit 2adeca04276acb4e747dbe7a5668efe03b164566 Merge: fa8785e862ef c29c91a9daa3 Author: Dan Williams Date: Thu Nov 2 19:20:59 2017 -0700 Merge branch 'libnvdimm-for-next' into test diff --cc fs/dax.c index 3652b26a0048,78233c716757

Re: [PATCH] selftests: breakpoints: fix compile error on breakpoint_test_arm64

Hi Shuah, On 2 November 2017 at 02:22, Shuah Khan wrote: > On 10/23/2017 01:42 AM, Sumit Semwal wrote: >> The current mainline breakpoints test for arm64 fails to compile with >> >> breakpoint_test_arm64.c: In function ‘set_watchpoint’: >> breakpoint_test_arm64.c:97:28: error:

Re: [PATCH] selftests: breakpoints: fix compile error on breakpoint_test_arm64

Hi Shuah, On 2 November 2017 at 02:22, Shuah Khan wrote: > On 10/23/2017 01:42 AM, Sumit Semwal wrote: >> The current mainline breakpoints test for arm64 fails to compile with >> >> breakpoint_test_arm64.c: In function ‘set_watchpoint’: >> breakpoint_test_arm64.c:97:28: error: storage size of

Re: [PATCH] powerpc/perf: Fix core-imc hotplug callback failure during imc initialization

On Friday 03 November 2017 05:49 AM, Michael Ellerman wrote: Madhavan Srinivasan writes: On Wednesday 01 November 2017 06:22 AM, Michael Ellerman wrote: Anju T Sudhakar writes: Call trace observed during boot: What's the actual oops?

Re: [PATCH] powerpc/perf: Fix core-imc hotplug callback failure during imc initialization

On Friday 03 November 2017 05:49 AM, Michael Ellerman wrote: Madhavan Srinivasan writes: On Wednesday 01 November 2017 06:22 AM, Michael Ellerman wrote: Anju T Sudhakar writes: Call trace observed during boot: What's the actual oops? I could recreate this in mambo with CPUS=2 and

Re: [PATCH] selftests: remove obsolete kconfig fragment for cpu-hotplug

Hello Lei, On 2 November 2017 at 07:43, lyang0 wrote: > > > On 2017年11月02日 06:59, Shuah Khan wrote: >> >> On 11/01/2017 04:52 PM, Thomas Gleixner wrote: >>> >>> On Wed, 1 Nov 2017, Shuah Khan wrote: On 10/17/2017 08:10 PM, lei.y...@windriver.com wrote: >

Re: [greybus-dev] [PATCH 2/2] staging: greybus/loopback: use ktime_get() for time intervals

On 02-11-17, 15:32, Arnd Bergmann wrote: > This driver is the only one using the deprecated timeval_to_ns() > helper. Changing it from do_gettimeofday() to ktime_get() makes > the code more efficient, more robust against concurrent > settimeofday(), more accurate and lets us get rid of that helper

Re: [PATCH] selftests: remove obsolete kconfig fragment for cpu-hotplug

Hello Lei, On 2 November 2017 at 07:43, lyang0 wrote: > > > On 2017年11月02日 06:59, Shuah Khan wrote: >> >> On 11/01/2017 04:52 PM, Thomas Gleixner wrote: >>> >>> On Wed, 1 Nov 2017, Shuah Khan wrote: On 10/17/2017 08:10 PM, lei.y...@windriver.com wrote: > > From: Lei Yang >

Re: [greybus-dev] [PATCH 2/2] staging: greybus/loopback: use ktime_get() for time intervals

On 02-11-17, 15:32, Arnd Bergmann wrote: > This driver is the only one using the deprecated timeval_to_ns() > helper. Changing it from do_gettimeofday() to ktime_get() makes > the code more efficient, more robust against concurrent > settimeofday(), more accurate and lets us get rid of that helper

[PATCH net-next 4/6] net: hns3: add support for set_link_ksettings

From: Fuyun Liang This patch adds set_link_ksettings support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Lipeng --- drivers/net/ethernet/hisilicon/hns3/hns3pf/hns3_ethtool.c | 11 +++ 1 file changed,

[PATCH net-next 4/6] net: hns3: add support for set_link_ksettings

From: Fuyun Liang This patch adds set_link_ksettings support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Lipeng --- drivers/net/ethernet/hisilicon/hns3/hns3pf/hns3_ethtool.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH net-next 3/6] net: hns3: fix a bug in hns3_driv_to_eth_caps

From: Fuyun Liang The value of link_modes.advertising and the value of link_modes.supported is initialized to zero every time in for loop in hns3_driv_to_eth_caps(). But we just want to set specified bit for them. Initialization is unnecessary. This patch fixes it.

[PATCH net-next 3/6] net: hns3: fix a bug in hns3_driv_to_eth_caps

From: Fuyun Liang The value of link_modes.advertising and the value of link_modes.supported is initialized to zero every time in for loop in hns3_driv_to_eth_caps(). But we just want to set specified bit for them. Initialization is unnecessary. This patch fixes it. Fixes: 496d03e (net: hns3:

Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

On 10/13, Yunlong Song wrote: > This can help us to debug on some corner case. > > Signed-off-by: Yunlong Song > Signed-off-by: Chao Yu > --- > fs/f2fs/gc.c | 6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/fs/f2fs/gc.c

Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

On 10/13, Yunlong Song wrote: > This can help us to debug on some corner case. > > Signed-off-by: Yunlong Song > Signed-off-by: Chao Yu > --- > fs/f2fs/gc.c | 6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c > index 197ebf4..2b03202

Re: [PATCH v4 2/2] watchdog: Add Spreadtrum watchdog driver

On Wed, Nov 01, 2017 at 01:46:36PM +, Guenter Roeck wrote: > On 10/31/2017 01:16 AM, Eric Long wrote: > > This patch adds the watchdog driver for Spreadtrum SC9860 platform. > > > > Signed-off-by: Eric Long > > --- > > Changes since v3: > > - Update Kconfig

Re: [PATCH v4 2/2] watchdog: Add Spreadtrum watchdog driver

On Wed, Nov 01, 2017 at 01:46:36PM +, Guenter Roeck wrote: > On 10/31/2017 01:16 AM, Eric Long wrote: > > This patch adds the watchdog driver for Spreadtrum SC9860 platform. > > > > Signed-off-by: Eric Long > > --- > > Changes since v3: > > - Update Kconfig SPRD_WATCHDOG help messages. > >

Re: [PATCH V2] of: platform: Create dummy routines for !CONFIG_OF_ADDRESS

On 02-11-17, 07:40, Rob Herring wrote: > No. As an example, ideally of_device_alloc would be an internal > function. But we have one user in ibmebus. Okay. Lets abandon this change then. -- viresh

Re: [PATCH V2] of: platform: Create dummy routines for !CONFIG_OF_ADDRESS

On 02-11-17, 07:40, Rob Herring wrote: > No. As an example, ideally of_device_alloc would be an internal > function. But we have one user in ibmebus. Okay. Lets abandon this change then. -- viresh

[PATCH net-next 5/6] net: hns3: add support for nway_reset

From: Fuyun Liang This patch adds nway_reset support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Lipeng --- .../net/ethernet/hisilicon/hns3/hns3pf/hns3_ethtool.c | 18 ++ 1 file changed, 18

[PATCH net-next 5/6] net: hns3: add support for nway_reset

From: Fuyun Liang This patch adds nway_reset support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Lipeng --- .../net/ethernet/hisilicon/hns3/hns3pf/hns3_ethtool.c | 18 ++ 1 file changed, 18 insertions(+) diff --git

Re: [PATCH v2] cpufreq: schedutil: Examine the correct CPU when we update util

On 02-11-17, 12:06, Chris Redpath wrote: > According to my diff, this was the commit which switched from assigning > the values directly (and not overwriting the cpu member, which was > introduced in the other commit you reference) to using a memset and > clearing the whole struct. I understand

Re: [PATCH v2] cpufreq: schedutil: Examine the correct CPU when we update util

On 02-11-17, 12:06, Chris Redpath wrote: > According to my diff, this was the commit which switched from assigning > the values directly (and not overwriting the cpu member, which was > introduced in the other commit you reference) to using a memset and > clearing the whole struct. I understand

  1   2   3   4   5   6   7   8   9   10   >