[RFC v4 15/20] mm/spf: protect mremap() against speculative pf

mremap() is modifying the VMA layout and thus must be protected against the speculative page fault handler. Signed-off-by: Laurent Dufour --- mm/mremap.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/mm/mremap.c b/mm/mremap.c index cd8a1b199ef9..9c7f69c9e80f 100644 ---

[RFC v4 18/20] x86/mm: Update the handle_speculative_fault's path

If handle_speculative_fault failed due to a VM ERROR, we try again the slow path to allow the signal to be delivered. Signed-off-by: Laurent Dufour --- arch/x86/mm/fault.c | 21 + 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/arch/x86/mm/fault.c

[RFC v4 02/20] mm: Prepare for FAULT_FLAG_SPECULATIVE

From: Peter Zijlstra When speculating faults (without holding mmap_sem) we need to validate that the vma against which we loaded pages is still valid when we're ready to install the new PTE. Therefore, replace the pte_offset_map_lock() calls that (re)take the PTL with

[RFC v4 02/20] mm: Prepare for FAULT_FLAG_SPECULATIVE

From: Peter Zijlstra When speculating faults (without holding mmap_sem) we need to validate that the vma against which we loaded pages is still valid when we're ready to install the new PTE. Therefore, replace the pte_offset_map_lock() calls that (re)take the PTL with pte_map_lock() which can

[RFC v4 04/20] mm: VMA sequence count

From: Peter Zijlstra Wrap the VMA modifications (vma_adjust/unmap_page_range) with sequence counts such that we can easily test if a VMA is changed. The unmap_page_range() one allows us to make assumptions about page-tables; when we find the seqcount hasn't changed we can

[RFC v4 08/20] mm/spf: Fix fe.sequence init in __handle_mm_fault()

__handle_mm_fault() calls handle_pte_fault which requires the sequence field of the fault_env to be initialized. Signed-off-by: Laurent Dufour --- mm/memory.c | 1 + 1 file changed, 1 insertion(+) diff --git a/mm/memory.c b/mm/memory.c index

[RFC v4 04/20] mm: VMA sequence count

From: Peter Zijlstra Wrap the VMA modifications (vma_adjust/unmap_page_range) with sequence counts such that we can easily test if a VMA is changed. The unmap_page_range() one allows us to make assumptions about page-tables; when we find the seqcount hasn't changed we can assume page-tables are

[RFC v4 08/20] mm/spf: Fix fe.sequence init in __handle_mm_fault()

__handle_mm_fault() calls handle_pte_fault which requires the sequence field of the fault_env to be initialized. Signed-off-by: Laurent Dufour --- mm/memory.c | 1 + 1 file changed, 1 insertion(+) diff --git a/mm/memory.c b/mm/memory.c index 9de741554e15..f05288797c60 100644 --- a/mm/memory.c

[RFC v4 06/20] mm: Provide speculative fault infrastructure

From: Peter Zijlstra Provide infrastructure to do a speculative fault (not holding mmap_sem). The not holding of mmap_sem means we can race against VMA change/removal and page-table destruction. We use the SRCU VMA freeing to keep the VMA around. We use the VMA seqcount to

[RFC v4 06/20] mm: Provide speculative fault infrastructure

From: Peter Zijlstra Provide infrastructure to do a speculative fault (not holding mmap_sem). The not holding of mmap_sem means we can race against VMA change/removal and page-table destruction. We use the SRCU VMA freeing to keep the VMA around. We use the VMA seqcount to detect change

[RFC v4 13/20] mm/spf: Add check on the VMA's flags

When handling speculative page fault we should check for the VMA's access permission as it is done in handle_mm_fault() or access_error in x86's fault handler. Signed-off-by: Laurent Dufour --- mm/memory.c | 24 1 file changed, 24

[RFC v4 13/20] mm/spf: Add check on the VMA's flags

When handling speculative page fault we should check for the VMA's access permission as it is done in handle_mm_fault() or access_error in x86's fault handler. Signed-off-by: Laurent Dufour --- mm/memory.c | 24 1 file changed, 24 insertions(+) diff --git a/mm/memory.c

[RFC v4 00/20] Speculative page faults

This is a port on kernel 4.12 of the work done by Peter Zijlstra to handle page fault without holding the mm semaphore. http://linux-kernel.2935.n7.nabble.com/RFC-PATCH-0-6-Another-go-at-speculative-page-faults-tt965642.html#none Compared to the Peter initial work, this series introduce a try

[RFC v4 01/20] mm: Dont assume page-table invariance during faults

From: Peter Zijlstra One of the side effects of speculating on faults (without holding mmap_sem) is that we can race with free_pgtables() and therefore we cannot assume the page-tables will stick around. Remove the relyance on the pte pointer. Signed-off-by: Peter

[RFC v4 00/20] Speculative page faults

This is a port on kernel 4.12 of the work done by Peter Zijlstra to handle page fault without holding the mm semaphore. http://linux-kernel.2935.n7.nabble.com/RFC-PATCH-0-6-Another-go-at-speculative-page-faults-tt965642.html#none Compared to the Peter initial work, this series introduce a try

[RFC v4 01/20] mm: Dont assume page-table invariance during faults

From: Peter Zijlstra One of the side effects of speculating on faults (without holding mmap_sem) is that we can race with free_pgtables() and therefore we cannot assume the page-tables will stick around. Remove the relyance on the pte pointer. Signed-off-by: Peter Zijlstra (Intel) ---

RE: [PATCH 6/6] tty: serial: lpuart: add a more accurate baud rate calculation method

> -Original Message- > From: Andy Shevchenko [mailto:andy.shevche...@gmail.com] > Sent: Friday, June 09, 2017 5:26 PM > To: A.S. Dong > Cc: linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm > Mailing List; Greg Kroah-Hartman; Jiri Slaby; Andy Duan; Stefan Agner; >

RE: [PATCH 6/6] tty: serial: lpuart: add a more accurate baud rate calculation method

> -Original Message- > From: Andy Shevchenko [mailto:andy.shevche...@gmail.com] > Sent: Friday, June 09, 2017 5:26 PM > To: A.S. Dong > Cc: linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm > Mailing List; Greg Kroah-Hartman; Jiri Slaby; Andy Duan; Stefan Agner; >

Re: [PATCH] loop: fix error handling regression

On 06/09/2017 04:19 AM, Arnd Bergmann wrote: > gcc points out an unusual indentation: > > drivers/block/loop.c: In function 'loop_set_status': > drivers/block/loop.c:1149:3: error: this 'if' clause does not guard... > [-Werror=misleading-indentation] >if (figure_loop_size(lo,

Re: [PATCH] loop: fix error handling regression

On 06/09/2017 04:19 AM, Arnd Bergmann wrote: > gcc points out an unusual indentation: > > drivers/block/loop.c: In function 'loop_set_status': > drivers/block/loop.c:1149:3: error: this 'if' clause does not guard... > [-Werror=misleading-indentation] >if (figure_loop_size(lo,

Re: [PATCH v8 6/9] drivers: perf: hisi: Add support for Hisilicon Djtag driver

On 08/06/2017 17:35, Mark Rutland wrote: Hi, On Mon, May 22, 2017 at 08:48:32PM +0800, Shaokun Zhang wrote: +/* + * hisi_djtag_lock_v2: djtag lock to avoid djtag access conflict b/w kernel + * and UEFI. The mention of UEFI here worries me somewhat, and I have a number of questions

Re: [PATCH v8 6/9] drivers: perf: hisi: Add support for Hisilicon Djtag driver

On 08/06/2017 17:35, Mark Rutland wrote: Hi, On Mon, May 22, 2017 at 08:48:32PM +0800, Shaokun Zhang wrote: +/* + * hisi_djtag_lock_v2: djtag lock to avoid djtag access conflict b/w kernel + * and UEFI. The mention of UEFI here worries me somewhat, and I have a number of questions

[PATCH v2] nvme: use ctrl->device consistently for logging

Change the few left over users of ctrl->dev over to using ctrl->device for logging purposes, so we consistently use the same device. Signed-off-by: Johannes Thumshirn Reviewed-by: Sagi Grimberg --- Changes to v1: * Fix build drivers/nvme/host/core.c |

[PATCH v2] nvme: use ctrl->device consistently for logging

Change the few left over users of ctrl->dev over to using ctrl->device for logging purposes, so we consistently use the same device. Signed-off-by: Johannes Thumshirn Reviewed-by: Sagi Grimberg --- Changes to v1: * Fix build drivers/nvme/host/core.c | 10 +- 1 file changed, 5

Re: [RFC PATCH 1/8] Documentation: add DT binding for ARM System Control and Management Interface(SCMI) protocol

On Wed, Jun 07, 2017 at 05:10:05PM +0100, Sudeep Holla wrote: > This patch adds devicetree binding for System Control and Management > Interface (SCMI) Message Protocol used between the Application Cores(AP) > and the System Control Processor(SCP). The MHU peripheral provides a > mechanism for

Re: [RFC PATCH 1/8] Documentation: add DT binding for ARM System Control and Management Interface(SCMI) protocol

On Wed, Jun 07, 2017 at 05:10:05PM +0100, Sudeep Holla wrote: > This patch adds devicetree binding for System Control and Management > Interface (SCMI) Message Protocol used between the Application Cores(AP) > and the System Control Processor(SCP). The MHU peripheral provides a > mechanism for

[PATCH v1 1/1] gpio: of: provide option generic property for initial line states

This property is needed for barebox or may be other bootloaders to set proper gpio configuration as early as possible. This example is mainly based on "lines-initial-states" property from this binding documentation: Documentation/devicetree/bindings/gpio/gpio-pcf857x.txt Signed-off-by: Oleksij

[PATCH v1 1/1] gpio: of: provide option generic property for initial line states

This property is needed for barebox or may be other bootloaders to set proper gpio configuration as early as possible. This example is mainly based on "lines-initial-states" property from this binding documentation: Documentation/devicetree/bindings/gpio/gpio-pcf857x.txt Signed-off-by: Oleksij

Re: [PATCH] kbuild: replace genhdr-y with generated-y, deprecating genhdr-y

Le 09/06/2017 à 10:29, Masahiro Yamada a écrit : > Prior to commit fcc8487d477a ("uapi: export all headers under uapi > directories"), genhdr-y was meant to specify generated UAPI headers. > > - generated-y: generated headers (other than asm-generic wrappers) > - header-y : headers to be

Re: [PATCH] kbuild: replace genhdr-y with generated-y, deprecating genhdr-y

Le 09/06/2017 à 10:29, Masahiro Yamada a écrit : > Prior to commit fcc8487d477a ("uapi: export all headers under uapi > directories"), genhdr-y was meant to specify generated UAPI headers. > > - generated-y: generated headers (other than asm-generic wrappers) > - header-y : headers to be

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

Hi Babu, On Fri, Jun 9, 2017 at 3:55 PM, Babu Moger wrote: > On 6/9/2017 2:16 AM, Geert Uytterhoeven wrote: >> On Fri, Jun 9, 2017 at 9:05 AM, Geert Uytterhoeven >> wrote: Here is the original discussion

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

Hi Babu, On Fri, Jun 9, 2017 at 3:55 PM, Babu Moger wrote: > On 6/9/2017 2:16 AM, Geert Uytterhoeven wrote: >> On Fri, Jun 9, 2017 at 9:05 AM, Geert Uytterhoeven >> wrote: Here is the original discussion http://www.spinics.net/lists/devicetree/msg178101.html Signed-off-by:

Re: [PATCH] af_unix: Add sockaddr length checks before accessing sa_family in bind and connect handlers

From: Mateusz Jurczyk Date: Fri, 9 Jun 2017 13:15:40 +0200 > On Thu, Jun 8, 2017 at 10:04 PM, David Miller wrote: >> From: Mateusz Jurczyk >> Date: Thu, 8 Jun 2017 11:13:36 +0200 >> >>> Verify that the caller-provided sockaddr

Re: [PATCH] af_unix: Add sockaddr length checks before accessing sa_family in bind and connect handlers

From: Mateusz Jurczyk Date: Fri, 9 Jun 2017 13:15:40 +0200 > On Thu, Jun 8, 2017 at 10:04 PM, David Miller wrote: >> From: Mateusz Jurczyk >> Date: Thu, 8 Jun 2017 11:13:36 +0200 >> >>> Verify that the caller-provided sockaddr structure is large enough to >>> contain the sa_family field,

Re: [RFC PATCH 2/2] mm, oom: do not trigger out_of_memory from the #PF

On Thu, Jun 08, 2017 at 04:36:07PM +0200, Michal Hocko wrote: > Does anybody see any problem with the patch or I can send it for the > inclusion? > > On Fri 19-05-17 13:26:04, Michal Hocko wrote: > > From: Michal Hocko > > > > Any allocation failure during the #PF path will

Re: [PATCH] scsi: qla2xxx: fix printk format string warning on 32-bit

Hi Arnd, > On Jun 9, 2017, at 3:46 AM, Arnd Bergmann wrote: > > On 32-bit architectures, we using %lx to print a size_t causes a harmless > warning: > > qla2xxx/qla_init.c: In function 'qla24xx_load_risc_flash': > qla2xxx/qla_init.c:6407:7: error: format '%lx' expects argument

Re: [PATCH] scsi: qla2xxx: fix printk format string warning on 32-bit

Hi Arnd, > On Jun 9, 2017, at 3:46 AM, Arnd Bergmann wrote: > > On 32-bit architectures, we using %lx to print a size_t causes a harmless > warning: > > qla2xxx/qla_init.c: In function 'qla24xx_load_risc_flash': > qla2xxx/qla_init.c:6407:7: error: format '%lx' expects argument of type 'long

Re: [RFC PATCH 2/2] mm, oom: do not trigger out_of_memory from the #PF

On Thu, Jun 08, 2017 at 04:36:07PM +0200, Michal Hocko wrote: > Does anybody see any problem with the patch or I can send it for the > inclusion? > > On Fri 19-05-17 13:26:04, Michal Hocko wrote: > > From: Michal Hocko > > > > Any allocation failure during the #PF path will return with

[PATCH v4 3/6] kernel/reboot.c: export pm_power_off_prepare

Export pm_power_off_prepare. It is needed to implement power off on Freescale/NXP iMX6 based boards with external power management integrated circuit (PMIC). Signed-off-by: Oleksij Rempel --- kernel/reboot.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v4 3/6] kernel/reboot.c: export pm_power_off_prepare

Export pm_power_off_prepare. It is needed to implement power off on Freescale/NXP iMX6 based boards with external power management integrated circuit (PMIC). Signed-off-by: Oleksij Rempel --- kernel/reboot.c | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/reboot.c b/kernel/reboot.c

[PATCH v4 1/6] ARM: imx6q: provide documentation for new fsl,pmic-stby-poweroff property

Signed-off-by: Oleksij Rempel Acked-by: Rob Herring --- Documentation/devicetree/bindings/clock/imx6q-clock.txt | 8 1 file changed, 8 insertions(+) diff --git a/Documentation/devicetree/bindings/clock/imx6q-clock.txt

[PATCH v4 5/6] regulator: pfuze100-regulator: provide pm_power_off_prepare handler

On some boards the SoC can use one pin "PMIC_STBY_REQ" to notify th PMIC about state changes. In this case internal state of PMIC must be preconfigured for upcomming state change. It works fine with the current regulator framework, except with the power-off case. This patch is providing an

[PATCH v4 1/6] ARM: imx6q: provide documentation for new fsl,pmic-stby-poweroff property

Signed-off-by: Oleksij Rempel Acked-by: Rob Herring --- Documentation/devicetree/bindings/clock/imx6q-clock.txt | 8 1 file changed, 8 insertions(+) diff --git a/Documentation/devicetree/bindings/clock/imx6q-clock.txt b/Documentation/devicetree/bindings/clock/imx6q-clock.txt index

[PATCH v4 5/6] regulator: pfuze100-regulator: provide pm_power_off_prepare handler

On some boards the SoC can use one pin "PMIC_STBY_REQ" to notify th PMIC about state changes. In this case internal state of PMIC must be preconfigured for upcomming state change. It works fine with the current regulator framework, except with the power-off case. This patch is providing an

[PATCH v4 4/6] regulator: pfuze100: add fsl,pmic-stby-poweroff property

Document the new optional "fsl,pmic-stby-poweroff" property. Signed-off-by: Oleksij Rempel --- Documentation/devicetree/bindings/regulator/pfuze100.txt | 7 +++ 1 file changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/regulator/pfuze100.txt

[PATCH v4 4/6] regulator: pfuze100: add fsl,pmic-stby-poweroff property

Document the new optional "fsl,pmic-stby-poweroff" property. Signed-off-by: Oleksij Rempel --- Documentation/devicetree/bindings/regulator/pfuze100.txt | 7 +++ 1 file changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/regulator/pfuze100.txt

[PATCH v4 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set

One of the Freescale recommended sequences for power off with external PMIC is the following: ... 3. SoC is programming PMIC for power off when standby is asserted. 4. In CCM STOP mode, Standby is asserted, PMIC gates SoC supplies. See:

[PATCH v4 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set

One of the Freescale recommended sequences for power off with external PMIC is the following: ... 3. SoC is programming PMIC for power off when standby is asserted. 4. In CCM STOP mode, Standby is asserted, PMIC gates SoC supplies. See:

[PATCH v4 0/6] provide power off support for iMX6 with external PMIC

This patch series is providing power off support for Freescale/NXP iMX6 based boards with external power management integrated circuit (PMIC). changes: v4: - update comment in "regulator: pfuze100: add fsl,pmic-stby-poweroff ..." patch - add Acked-by to "ARM: imx6q: provide documentation for

[PATCH v4 0/6] provide power off support for iMX6 with external PMIC

This patch series is providing power off support for Freescale/NXP iMX6 based boards with external power management integrated circuit (PMIC). changes: v4: - update comment in "regulator: pfuze100: add fsl,pmic-stby-poweroff ..." patch - add Acked-by to "ARM: imx6q: provide documentation for

[PATCH v4 6/6] ARM: dts: imx6: RIoTboard provide standby on power off option

This board, as well as some other boards with i.MX6 and a PMIC, uses a "MPIC_STBY_REQ" line to notify the PMIC about a state change. The PMIC is programmed for a specific state change before triggering the line. In this case, PMIC_STBY_REQ can be used for stand by, sleep and power off modes.

[PATCH v4 6/6] ARM: dts: imx6: RIoTboard provide standby on power off option

This board, as well as some other boards with i.MX6 and a PMIC, uses a "MPIC_STBY_REQ" line to notify the PMIC about a state change. The PMIC is programmed for a specific state change before triggering the line. In this case, PMIC_STBY_REQ can be used for stand by, sleep and power off modes.

Re: [PATCH] usb: gadget: functions: add ftrace export over USB

Hi, Steven Rostedt writes: > On Fri, 9 Jun 2017 09:13:27 +0300 > Felipe Balbi wrote: > >> Allow for ftrace data to be exported over a USB Gadget >> Controller. With this, we have a potentially very fast pipe for >> transmitting ftrace data to

Re: [PATCH] usb: gadget: functions: add ftrace export over USB

Hi, Steven Rostedt writes: > On Fri, 9 Jun 2017 09:13:27 +0300 > Felipe Balbi wrote: > >> Allow for ftrace data to be exported over a USB Gadget >> Controller. With this, we have a potentially very fast pipe for >> transmitting ftrace data to a Host PC for further analysis. >> >> Note that

Re: [RFC][PATCH] atomic: Fix atomic_set_release() for 'funny' architectures

On 6/9/2017 7:05 AM, Peter Zijlstra wrote: Subject: atomic: Fix atomic_set_release() for 'funny' architectures Those architectures that have a special atomic_set implementation also need a special atomic_set_release(), because for the very same reason WRITE_ONCE() is broken for them,

Re: [RFC][PATCH] atomic: Fix atomic_set_release() for 'funny' architectures

On 6/9/2017 7:05 AM, Peter Zijlstra wrote: Subject: atomic: Fix atomic_set_release() for 'funny' architectures Those architectures that have a special atomic_set implementation also need a special atomic_set_release(), because for the very same reason WRITE_ONCE() is broken for them,

Re: [PATCH 1/4] dt-bindings: tps65217: Update binding documentation.

On Wed, Jun 07, 2017 at 12:32:39PM +0200, Enric Balletbo i Serra wrote: > This patch adds a new binding documentation for the TPS65217 MFD and > updates the documentation for all the sub-devices in accordance to get > each individual sub-driver functioning correctly. Explain why breaking

Re: [PATCH 1/4] dt-bindings: tps65217: Update binding documentation.

On Wed, Jun 07, 2017 at 12:32:39PM +0200, Enric Balletbo i Serra wrote: > This patch adds a new binding documentation for the TPS65217 MFD and > updates the documentation for all the sub-devices in accordance to get > each individual sub-driver functioning correctly. Explain why breaking

Re: [PATCH] usb: gadget: functions: add ftrace export over USB

On Fri, 9 Jun 2017 09:13:27 +0300 Felipe Balbi wrote: > Allow for ftrace data to be exported over a USB Gadget > Controller. With this, we have a potentially very fast pipe for > transmitting ftrace data to a Host PC for further analysis. > > Note that in order to

Re: [PATCH] usb: gadget: functions: add ftrace export over USB

On Fri, 9 Jun 2017 09:13:27 +0300 Felipe Balbi wrote: > Allow for ftrace data to be exported over a USB Gadget > Controller. With this, we have a potentially very fast pipe for > transmitting ftrace data to a Host PC for further analysis. > > Note that in order to decode the data, one needs

[PATCH 09/10] Revert "printk: fix double printing with earlycon"

From: Petr Mladek This reverts commit cf39bf58afdaabc0b86f141630fb3fd18190294e. The commit regression to users that define both console=ttyS1 and console=ttyS0 on the command line, see https://lkml.kernel.org/r/20170509082915.GA13236@bistromath.localdomain The kernel log

[PATCH 09/10] Revert "printk: fix double printing with earlycon"

From: Petr Mladek This reverts commit cf39bf58afdaabc0b86f141630fb3fd18190294e. The commit regression to users that define both console=ttyS1 and console=ttyS0 on the command line, see https://lkml.kernel.org/r/20170509082915.GA13236@bistromath.localdomain The kernel log messages always

Re: linux-next: Tree for Jun 9

Hi Stephen, On 9 June 2017 at 12:12, Stephen Rothwell wrote: > Hi all, > < snip > > You can see which trees have been included by looking in the Next/Trees > file in the source. There are also quilt-import.log and merge.log > files in the Next directory. Between each

Re: linux-next: Tree for Jun 9

Hi Stephen, On 9 June 2017 at 12:12, Stephen Rothwell wrote: > Hi all, > < snip > > You can see which trees have been included by looking in the Next/Trees > file in the source. There are also quilt-import.log and merge.log > files in the Next directory. Between each merge, the tree was built

Re: [PATCH v2 1/3] dt-bindings: arm: amlogic: Add SoC information bindings

On 06/09/2017 03:37 PM, Rob Herring wrote: > On Tue, Jun 06, 2017 at 11:45:38AM +0200, Neil Armstrong wrote: >> Add bindings for the SoC information register of the Amlogic SoCs. >> >> Signed-off-by: Neil Armstrong >> --- >>

Re: [PATCH v2 1/3] dt-bindings: arm: amlogic: Add SoC information bindings

On 06/09/2017 03:37 PM, Rob Herring wrote: > On Tue, Jun 06, 2017 at 11:45:38AM +0200, Neil Armstrong wrote: >> Add bindings for the SoC information register of the Amlogic SoCs. >> >> Signed-off-by: Neil Armstrong >> --- >> Documentation/devicetree/bindings/arm/amlogic.txt | 32 >>

[PATCH] x86, mm: disable 1GB direct mapping when disabling 2MB mapping

The kmemleak and debug_pagealloc features both disable using huge pages for direct mapping so they can do cpa() on page level granularity in any context. However they only do that for 2MB pages, which means 1GB pages can still be used if the CPU supports it, unless disabled by a boot param, which

[PATCH] x86, mm: disable 1GB direct mapping when disabling 2MB mapping

The kmemleak and debug_pagealloc features both disable using huge pages for direct mapping so they can do cpa() on page level granularity in any context. However they only do that for 2MB pages, which means 1GB pages can still be used if the CPU supports it, unless disabled by a boot param, which

Re: [linux-sunxi] [PATCH] arm64: allwinner: sun50i-a64: Remove duplicate ethernet@1c30000

On Fri, Jun 09, 2017 at 02:38:39PM +0100, Andre Przywara wrote: > Hi, > > On 09/06/17 13:40, Jagan Teki wrote: > > From: Jagan Teki > > > > Remove duplicate ethernet@1c3 from allwinner/sun50i-a64.dtsi > > I think this is an artefact of the sun8i-dwmac merging,

Re: [linux-sunxi] [PATCH] arm64: allwinner: sun50i-a64: Remove duplicate ethernet@1c30000

On Fri, Jun 09, 2017 at 02:38:39PM +0100, Andre Przywara wrote: > Hi, > > On 09/06/17 13:40, Jagan Teki wrote: > > From: Jagan Teki > > > > Remove duplicate ethernet@1c3 from allwinner/sun50i-a64.dtsi > > I think this is an artefact of the sun8i-dwmac merging, where both David > and Maxime

Re: [PATCH] checkpatch.pl: Add SPDX license tag check for dts files and headers

On Wed, Jun 07, 2017 at 05:45:03PM +0900, Masahiro Yamada wrote: > Hi Rob, > > 2017-02-24 0:56 GMT+09:00 Rob Herring : > > Add a check for using SPDX-License-Identifier tags to define the license of > > .dts{i} and DT header files rather than using free form license text. This >

Re: [PATCH] checkpatch.pl: Add SPDX license tag check for dts files and headers

On Wed, Jun 07, 2017 at 05:45:03PM +0900, Masahiro Yamada wrote: > Hi Rob, > > 2017-02-24 0:56 GMT+09:00 Rob Herring : > > Add a check for using SPDX-License-Identifier tags to define the license of > > .dts{i} and DT header files rather than using free form license text. This > > check looks for

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

Geert, On 6/9/2017 2:16 AM, Geert Uytterhoeven wrote: Hi Babu, On Fri, Jun 9, 2017 at 9:05 AM, Geert Uytterhoeven wrote: Here is the original discussion http://www.spinics.net/lists/devicetree/msg178101.html Signed-off-by: Babu Moger

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

Geert, On 6/9/2017 2:16 AM, Geert Uytterhoeven wrote: Hi Babu, On Fri, Jun 9, 2017 at 9:05 AM, Geert Uytterhoeven wrote: Here is the original discussion http://www.spinics.net/lists/devicetree/msg178101.html Signed-off-by: Babu Moger Suggested-by: Arnd Bergmann Hmm, the link above refers

Re: [PATCH 2/2] ARM: dts: imx6ul: Add imx6ul-tempmon

Hi, On Fri, 9 Jun 2017 13:58:15 +0300 Leonard Crestez wrote: > On Thu, 2017-06-08 at 13:45 -0300, Fabio Estevam wrote: > > On Thu, Jun 8, 2017 at 1:26 PM, Leonard Crestez wrote: > > > > > > > > +   tempmon: tempmon { > > > +   compatible =

Re: [PATCH 2/2] ARM: dts: imx6ul: Add imx6ul-tempmon

Hi, On Fri, 9 Jun 2017 13:58:15 +0300 Leonard Crestez wrote: > On Thu, 2017-06-08 at 13:45 -0300, Fabio Estevam wrote: > > On Thu, Jun 8, 2017 at 1:26 PM, Leonard Crestez wrote: > > > > > > > > +   tempmon: tempmon { > > > +   compatible =

DMA-safety for edac_atomic_scrub on ARM

Hi, I've CCed Rob as the original author of the ARM EDAC scrub function. On Fr, 2017-06-09 at 15:14 +0200, Jan Lübbe wrote: > [...] > > + mci->scrub_mode = SCRUB_SW_SRC; > I'm not sure if this works as expected ARM as it is currently > implemented, but that's a topic for a different mail.

DMA-safety for edac_atomic_scrub on ARM

Hi, I've CCed Rob as the original author of the ARM EDAC scrub function. On Fr, 2017-06-09 at 15:14 +0200, Jan Lübbe wrote: > [...] > > + mci->scrub_mode = SCRUB_SW_SRC; > I'm not sure if this works as expected ARM as it is currently > implemented, but that's a topic for a different mail.

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

On Wed, 2017-05-31 at 14:42 +0200, Matthias Brugger wrote: > > On 31/05/17 13:39, YT Shen wrote: > > This adds basic chip support for Mediatek 2712 > > > > Signed-off-by: YT Shen > > --- > > arch/arm64/boot/dts/mediatek/Makefile | 1 + > >

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

On Wed, 2017-05-31 at 14:42 +0200, Matthias Brugger wrote: > > On 31/05/17 13:39, YT Shen wrote: > > 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

[PATCH v5 17/23] scsi: hisi_sas: add v3 code to send ATA frame

From: Xiang Chen Add code to prepare ATA frame for v3 hw Signed-off-by: John Garry Signed-off-by: Xiang Chen --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 106 + 1 file changed, 106

[PATCH v5 17/23] scsi: hisi_sas: add v3 code to send ATA frame

From: Xiang Chen Add code to prepare ATA frame for v3 hw Signed-off-by: John Garry Signed-off-by: Xiang Chen --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 106 + 1 file changed, 106 insertions(+) diff --git a/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c

[PATCH v5 13/23] scsi: hisi_sas: add phy up/down/bcast and channel ISR

From: Xiang Chen Add code to initialise interrupts and add some interrupt handlers. Also add function hisi_sas_v3_destroy_irqs() to clean-up irqs upon module unloading. Signed-off-by: John Garry Signed-off-by: Xiang Chen

[PATCH v5 13/23] scsi: hisi_sas: add phy up/down/bcast and channel ISR

From: Xiang Chen Add code to initialise interrupts and add some interrupt handlers. Also add function hisi_sas_v3_destroy_irqs() to clean-up irqs upon module unloading. Signed-off-by: John Garry Signed-off-by: Xiang Chen --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 283

[PATCH v5 21/23] scsi: hisi_sas: Add v3 code to support ECC and AXI bus fatal error

From: Xiang Chen For ECC 1bit error, logic can recover it, so we only print a warning. For ECC multi-bit and AXI bus fatal error, we panic. Note: once v3 hw controller reset support is added, the panic will be replaced by a controller reset, like v2 hw.

[PATCH v5 21/23] scsi: hisi_sas: Add v3 code to support ECC and AXI bus fatal error

From: Xiang Chen For ECC 1bit error, logic can recover it, so we only print a warning. For ECC multi-bit and AXI bus fatal error, we panic. Note: once v3 hw controller reset support is added, the panic will be replaced by a controller reset, like v2 hw. Signed-off-by: John Garry

[PATCH v5 08/23] scsi: hisi_sas: create hisi_sas_get_fw_info()

Move the functionality to retrieve the fw info into a dedicated device type-agnostic function, hisi_sas_get_fw_info(). The reasoning is that this function will be required for future pci-based platforms. Also add some debug logs for failure. Signed-off-by: John Garry ---

[PATCH v5 02/23] scsi: hisi_sas: define hisi_sas_device.device_id as int

Currently hisi_sas_device.device_id is a u64. This can create a problem in selecting the queue for a device, in that this code does a 64b division on device id. For some 32b systems, 64b division is slow and the lib reference must be explicitly included. The device id does not need to be 64b in

[PATCH v5 08/23] scsi: hisi_sas: create hisi_sas_get_fw_info()

Move the functionality to retrieve the fw info into a dedicated device type-agnostic function, hisi_sas_get_fw_info(). The reasoning is that this function will be required for future pci-based platforms. Also add some debug logs for failure. Signed-off-by: John Garry ---

[PATCH v5 02/23] scsi: hisi_sas: define hisi_sas_device.device_id as int

Currently hisi_sas_device.device_id is a u64. This can create a problem in selecting the queue for a device, in that this code does a 64b division on device id. For some 32b systems, 64b division is slow and the lib reference must be explicitly included. The device id does not need to be 64b in

[PATCH v5 07/23] scsi: hisi_sas: add pci_dev in hisi_hba struct

Since hip08 SAS controller is based on pci device, add hisi_hba.pci_dev for hip08 (will be v3), and also rename hisi_hba.pdev to .platform_dev for clarity. In addition, for common code which wants to reference the controller device struct, add hisi_hba.dev, and change the common code to use it.

[PATCH v5 07/23] scsi: hisi_sas: add pci_dev in hisi_hba struct

Since hip08 SAS controller is based on pci device, add hisi_hba.pci_dev for hip08 (will be v3), and also rename hisi_hba.pdev to .platform_dev for clarity. In addition, for common code which wants to reference the controller device struct, add hisi_hba.dev, and change the common code to use it.

[PATCH v5 12/23] scsi: hisi_sas: add v3 hw PHY init

From: Xiang Chen Add code to configure PHYs for v3 hw. Signed-off-by: John Garry Signed-off-by: Xiang Chen --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 127 - 1 file changed, 126

[PATCH v5 12/23] scsi: hisi_sas: add v3 hw PHY init

From: Xiang Chen Add code to configure PHYs for v3 hw. Signed-off-by: John Garry Signed-off-by: Xiang Chen --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 127 - 1 file changed, 126 insertions(+), 1 deletion(-) diff --git a/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c

[PATCH v5 05/23] scsi: hisi_sas: relocate sata_done_v2_hw()

From: Xiang Chen Relocate get_ata_protocol() to a common location, as future hw versions will require it. Also rename with "hisi_sas_" prefix for consistency. Signed-off-by: Xiang Chen Signed-off-by: John Garry ---

[PATCH v5 05/23] scsi: hisi_sas: relocate sata_done_v2_hw()

From: Xiang Chen Relocate get_ata_protocol() to a common location, as future hw versions will require it. Also rename with "hisi_sas_" prefix for consistency. Signed-off-by: Xiang Chen Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas.h | 2 ++

[PATCH v5 01/23] scsi: hisi_sas: fix timeout check in hisi_sas_internal_task_abort()

From: Xiang Chen We need to check for timeout before task status, or the task will be mistook as completed internal abort command. Also add protection for sas_task.task_state_flags in hisi_sas_tmf_timedout(). Signed-off-by: Xiang Chen

[PATCH v5 01/23] scsi: hisi_sas: fix timeout check in hisi_sas_internal_task_abort()

From: Xiang Chen We need to check for timeout before task status, or the task will be mistook as completed internal abort command. Also add protection for sas_task.task_state_flags in hisi_sas_tmf_timedout(). Signed-off-by: Xiang Chen Signed-off-by: John Garry ---

[PATCH v5 09/23] scsi: hisi_sas: add skeleton v3 hw driver

Add skeleton driver for v3 hw in hisi_sas_v3_hw.c File hisi_sas_v3_hw.c will serve 2 purposes: - probing and initialisation of the controller based on pci device - hw layer for v3-based controllers The controller design is quite similar to v2 hw in hip07. However key differences include: -All

[PATCH v5 04/23] scsi: hisi_sas: relocate get_ata_protocol()

From: Xiang Chen Relocate get_ata_protocol() to a common location, as future hw versions will require it. Also rename with "hisi_sas_" prefix for consistency. Signed-off-by: Xiang Chen Signed-off-by: John Garry ---

<    4   5   6   7   8   9   10   11   12   13   >