Re: [PATCH] x86/fpu: move FPU state into separate cache

Hi Kees, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.11-rc4 next-20170330] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kees-Cook/x86

Re: [PATCH] x86/fpu: move FPU state into separate cache

Hi Kees, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.11-rc4 next-20170330] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kees-Cook/x86

linux-next: manual merge of the akpm tree with the tip tree

Hi all, Today's linux-next merge of the akpm tree got a conflict in: kernel/sched/fair.c between commit: 0ccb977f4c80 ("sched/fair: Explicitly generate __update_load_avg() instances") from the tip tree and patch: "kernel/sched/fair.c: uninline __update_load_avg()" from the akpm tree.

linux-next: manual merge of the akpm tree with the tip tree

Hi all, Today's linux-next merge of the akpm tree got a conflict in: kernel/sched/fair.c between commit: 0ccb977f4c80 ("sched/fair: Explicitly generate __update_load_avg() instances") from the tip tree and patch: "kernel/sched/fair.c: uninline __update_load_avg()" from the akpm tree.

Re: sudo x86info -a => kernel BUG at mm/usercopy.c:78!

On 30.03.2017 20:44, Laura Abbott wrote: On 03/30/2017 10:37 AM, Kees Cook wrote: Reads out of /dev/mem should be restricted to non-RAM on Fedora, yes? Tommi, do your kernels have CONFIG_STRICT_DEVMEM=y ? -Kees CONFIG_STRICT_DEVMEM should be on in all Fedora kernels. Yes, the fedora

Re: sudo x86info -a => kernel BUG at mm/usercopy.c:78!

On 30.03.2017 20:44, Laura Abbott wrote: On 03/30/2017 10:37 AM, Kees Cook wrote: Reads out of /dev/mem should be restricted to non-RAM on Fedora, yes? Tommi, do your kernels have CONFIG_STRICT_DEVMEM=y ? -Kees CONFIG_STRICT_DEVMEM should be on in all Fedora kernels. Yes, the fedora

Re: sudo x86info -a => kernel BUG at mm/usercopy.c:78!

On 30.03.2017 23:01, Dave Jones wrote: On Thu, Mar 30, 2017 at 12:52:31PM -0700, Kees Cook wrote: > On Thu, Mar 30, 2017 at 12:41 PM, Dave Jones wrote: > > On Thu, Mar 30, 2017 at 09:45:26AM -0700, Kees Cook wrote: > > > On Wed, Mar 29, 2017 at 11:44 PM, Tommi

Re: sudo x86info -a => kernel BUG at mm/usercopy.c:78!

On 30.03.2017 23:01, Dave Jones wrote: On Thu, Mar 30, 2017 at 12:52:31PM -0700, Kees Cook wrote: > On Thu, Mar 30, 2017 at 12:41 PM, Dave Jones wrote: > > On Thu, Mar 30, 2017 at 09:45:26AM -0700, Kees Cook wrote: > > > On Wed, Mar 29, 2017 at 11:44 PM, Tommi Rantala > > > wrote: > >

Re: [PATCH v2 3/5] PCI: rockchip: add remove() support

On Thu, Mar 30, 2017 at 05:26:09PM -0700, Brian Norris wrote: > Hi Bjorn, > > On Thu, Mar 30, 2017 at 06:28:25PM -0500, Bjorn Helgaas wrote: > > On Fri, Mar 24, 2017 at 10:22:19AM -0700, Brian Norris wrote: > > > On Fri, Mar 24, 2017 at 09:25:41AM -0500, Bjorn Helgaas wrote: > > > > These don't

Re: [PATCH v2 3/5] PCI: rockchip: add remove() support

On Thu, Mar 30, 2017 at 05:26:09PM -0700, Brian Norris wrote: > Hi Bjorn, > > On Thu, Mar 30, 2017 at 06:28:25PM -0500, Bjorn Helgaas wrote: > > On Fri, Mar 24, 2017 at 10:22:19AM -0700, Brian Norris wrote: > > > On Fri, Mar 24, 2017 at 09:25:41AM -0500, Bjorn Helgaas wrote: > > > > These don't

Re: [PATCH RFC] staging: ks7010: remove custom Michael MIC implementation

On Fri, 2017-03-31 at 15:47 +1100, Tobin C. Harding wrote: > ks7010 currently uses a custom implementation of the Michael MIC > algorithm. The kernel has an implementation of this algorithm > already, we should use it. ok, trivia: Do please run your patch through checkpatch and fix a few style

[PATCH v4 03/11] Move GET_FIELD/SET_FIELD to vas.h

Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other users of VAS, including NX-842 can use those macros. There is a lot of related code between the VAS/NX kernel drivers and skiboot. For consistency switch the order of parameters in SET_FIELD to match the order in skiboot.

[PATCH v4 03/11] Move GET_FIELD/SET_FIELD to vas.h

Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other users of VAS, including NX-842 can use those macros. There is a lot of related code between the VAS/NX kernel drivers and skiboot. For consistency switch the order of parameters in SET_FIELD to match the order in skiboot.

Re: [PATCH RFC] staging: ks7010: remove custom Michael MIC implementation

On Fri, 2017-03-31 at 15:47 +1100, Tobin C. Harding wrote: > ks7010 currently uses a custom implementation of the Michael MIC > algorithm. The kernel has an implementation of this algorithm > already, we should use it. ok, trivia: Do please run your patch through checkpatch and fix a few style

[PATCH v4 00/11] Enable VAS

Power9 introduces a hardware subsystem referred to as the Virtual Accelerator Switchboard (VAS). VAS allows kernel subsystems and user space processes to directly access the Nest Accelerator (NX) engines which implement compression and encryption algorithms in the hardware. NX has been in Power

[PATCH v4 00/11] Enable VAS

Power9 introduces a hardware subsystem referred to as the Virtual Accelerator Switchboard (VAS). VAS allows kernel subsystems and user space processes to directly access the Nest Accelerator (NX) engines which implement compression and encryption algorithms in the hardware. NX has been in Power

[PATCH v4 01/11] Add Power9 PVR

Add Power9 PVR Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/include/asm/reg.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h index fc879fd..7a45ff7 100644 --- a/arch/powerpc/include/asm/reg.h

[PATCH v4 01/11] Add Power9 PVR

Add Power9 PVR Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/include/asm/reg.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h index fc879fd..7a45ff7 100644 --- a/arch/powerpc/include/asm/reg.h +++

[PATCH v4 07/11] VAS: Define helpers to alloc/free windows

Define helpers to allocate/free VAS window objects. These will be used in follow-on patches when opening/closing windows. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/platforms/powernv/vas-window.c | 63 - 1 file changed, 62

[PATCH v4 07/11] VAS: Define helpers to alloc/free windows

Define helpers to allocate/free VAS window objects. These will be used in follow-on patches when opening/closing windows. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/platforms/powernv/vas-window.c | 63 - 1 file changed, 62 insertions(+), 1 deletion(-) diff

[PATCH v4 06/11] VAS: Define helpers to init window context

Define helpers to initialize window context registers of the VAS hardware. These will be used in follow-on patches when opening/closing VAS windows. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - Michael Neuling] Use ilog2(), radix_enabled() helpers;

[PATCH v4 06/11] VAS: Define helpers to init window context

Define helpers to initialize window context registers of the VAS hardware. These will be used in follow-on patches when opening/closing VAS windows. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - Michael Neuling] Use ilog2(), radix_enabled() helpers; drop warning when

[PATCH v4 08/11] VAS: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v4 09/11] VAS: Define vas_win_close() interface

Define the vas_win_close() interface which should be used to close a send or receive windows. While the hardware configurations required to open send and receive windows differ, the configuration to close a window is the same for both. So we use a single interface to close the window.

[PATCH v4 08/11] VAS: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v4 09/11] VAS: Define vas_win_close() interface

Define the vas_win_close() interface which should be used to close a send or receive windows. While the hardware configurations required to open send and receive windows differ, the configuration to close a window is the same for both. So we use a single interface to close the window.

[PATCH v4 05/11] VAS: Define helpers for access MMIO regions

Define some helper functions to access the MMIO regions. We use these in a follow-on patches to read/write VAS hardware registers. These helpers are also used to later issue 'paste' instructions to submit requests to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu

[PATCH v4 11/11] VAS: Define copy/paste interfaces

Define interfaces (wrappers) to the 'copy' and 'paste' instructions (which are new in PowerISA 3.0). These are intended to be used to by NX driver(s) to submit Coprocessor Request Blocks (CRBs) to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu ---

[PATCH v4 10/11] VAS: Define vas_tx_win_open()

Define an interface to open a VAS send window. This interface is intended to be used the Nest Accelerator (NX) driver(s) to open a send window and use it to submit compression/encryption requests to a VAS receive window. The receive window, identified by the [vasid, cop] parameters, must already

[PATCH v4 05/11] VAS: Define helpers for access MMIO regions

Define some helper functions to access the MMIO regions. We use these in a follow-on patches to read/write VAS hardware registers. These helpers are also used to later issue 'paste' instructions to submit requests to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu --- Changelog [v3]:

[PATCH v4 11/11] VAS: Define copy/paste interfaces

Define interfaces (wrappers) to the 'copy' and 'paste' instructions (which are new in PowerISA 3.0). These are intended to be used to by NX driver(s) to submit Coprocessor Request Blocks (CRBs) to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v3] - Map raw CR

[PATCH v4 10/11] VAS: Define vas_tx_win_open()

Define an interface to open a VAS send window. This interface is intended to be used the Nest Accelerator (NX) driver(s) to open a send window and use it to submit compression/encryption requests to a VAS receive window. The receive window, identified by the [vasid, cop] parameters, must already

[PATCH v4 04/11] VAS: Define vas_init() and vas_exit()

Implement vas_init() and vas_exit() functions for a new VAS module. This VAS module is essentially a library for other device drivers and kernel users of the NX coprocessors like NX-842 and NX-GZIP. In the future this will be extended to add support for user space to access the NX coprocessors.

[PATCH v4 02/11] VAS: Define macros, register fields and structures

Define macros for the VAS hardware registers and bit-fields as well as couple of data structures needed by the VAS driver. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - [Michael Neuling] Move VAS code to arch/powerpc; Reorg vas.h and

[PATCH v4 04/11] VAS: Define vas_init() and vas_exit()

Implement vas_init() and vas_exit() functions for a new VAS module. This VAS module is essentially a library for other device drivers and kernel users of the NX coprocessors like NX-842 and NX-GZIP. In the future this will be extended to add support for user space to access the NX coprocessors.

[PATCH v4 02/11] VAS: Define macros, register fields and structures

Define macros for the VAS hardware registers and bit-fields as well as couple of data structures needed by the VAS driver. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - [Michael Neuling] Move VAS code to arch/powerpc; Reorg vas.h and vas-internal.h to kernel and uapi

[lkp-robot] [staging] 5b6f9b95f7: kernel_BUG_at_drivers/base/driver.c

FYI, we noticed the following commit: commit: 5b6f9b95f7aeddf8a77a991bf1657a84ca281ab0 ("staging: unisys: visorbus: get rid of create_bus_type.") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -cpu

[lkp-robot] [staging] 5b6f9b95f7: kernel_BUG_at_drivers/base/driver.c

FYI, we noticed the following commit: commit: 5b6f9b95f7aeddf8a77a991bf1657a84ca281ab0 ("staging: unisys: visorbus: get rid of create_bus_type.") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -cpu

Re: [PATCH v3 14/37] mtd: nand: denali: support "nand-ecc-strength" DT property

Hi Boris, 2017-03-30 23:02 GMT+09:00 Boris Brezillon : > On Thu, 30 Mar 2017 15:46:00 +0900 > Masahiro Yamada wrote: > >> Historically, this driver tried to choose as big ECC strength as >> possible, but it would be reasonable

Re: [PATCH v3 14/37] mtd: nand: denali: support "nand-ecc-strength" DT property

Hi Boris, 2017-03-30 23:02 GMT+09:00 Boris Brezillon : > On Thu, 30 Mar 2017 15:46:00 +0900 > Masahiro Yamada wrote: > >> Historically, this driver tried to choose as big ECC strength as >> possible, but it would be reasonable to allow DT to set a particular >> ECC strength with

[lkp-robot] [PCI] d3881e5015: BUG:kernel_hang_in_boot_stage

FYI, we noticed the following commit: commit: d3881e5015421a578bc328136471fcf1d02ac389 ("PCI: Export PCI device config accessors") https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git pci/enumeration in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [PCI] d3881e5015: BUG:kernel_hang_in_boot_stage

FYI, we noticed the following commit: commit: d3881e5015421a578bc328136471fcf1d02ac389 ("PCI: Export PCI device config accessors") https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git pci/enumeration in testcase: trinity with following parameters: runtime: 300s

Re: [PATCH] x86/fpu: move FPU state into separate cache

Hi Kees, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.11-rc4 next-20170330] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kees-Cook/x86

Re: [PATCH] x86/fpu: move FPU state into separate cache

Hi Kees, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.11-rc4 next-20170330] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kees-Cook/x86

[PATCH RFC] staging: ks7010: remove custom Michael MIC implementation

ks7010 currently uses a custom implementation of the Michael MIC algorithm. The kernel has an implementation of this algorithm already, we should use it. Remove the custom implementation. Implement helper functions that call the in-tree implementation through the crypto API. Update the makefile.

[PATCH RFC] remove custom Michael MIC implementation

This RFC can be applied on op on Linus' tree 89970a0 Configuration options needed to build are CONFIG_STAGING=y CONFIG_KS7010=m The ks7010 driver currently uses a custom implementation of the Michael MIC algorithm. The kernel has an implementation of this algorithm already. This patch is an

[PATCH RFC] staging: ks7010: remove custom Michael MIC implementation

ks7010 currently uses a custom implementation of the Michael MIC algorithm. The kernel has an implementation of this algorithm already, we should use it. Remove the custom implementation. Implement helper functions that call the in-tree implementation through the crypto API. Update the makefile.

[PATCH RFC] remove custom Michael MIC implementation

This RFC can be applied on op on Linus' tree 89970a0 Configuration options needed to build are CONFIG_STAGING=y CONFIG_KS7010=m The ks7010 driver currently uses a custom implementation of the Michael MIC algorithm. The kernel has an implementation of this algorithm already. This patch is an

Re: [PATCH v4 0/7] PCI: dwc: Miscellaneous fixes and cleanups

On Friday 31 March 2017 05:14 AM, Bjorn Helgaas wrote: > On Mon, Mar 13, 2017 at 07:13:21PM +0530, Kishon Vijay Abraham I wrote: >> This should be the final set of cleanups/fixes before endpoint >> support can be merged. >> >> Keerthy's patch is a general fix in dra7xx driver and is not >>

Re: [PATCH v4 0/7] PCI: dwc: Miscellaneous fixes and cleanups

On Friday 31 March 2017 05:14 AM, Bjorn Helgaas wrote: > On Mon, Mar 13, 2017 at 07:13:21PM +0530, Kishon Vijay Abraham I wrote: >> This should be the final set of cleanups/fixes before endpoint >> support can be merged. >> >> Keerthy's patch is a general fix in dra7xx driver and is not >>

[PATCH] arm64: dts: uniphier: add input-delay properties to Cadence eMMC node

Since commit a04e2b383401 ("mmc: sdhci-cadence: Update PHY delay configuration"), PHY parameters must be specified by DT. The hard-coded settings have been converted as follows: - SDHCI_CDNS_PHY_DLY_SD_DEFAULT -> cdns,phy-input-delay-legacy - SDHCI_CDNS_PHY_DLY_EMMC_SDR ->

[PATCH] arm64: dts: uniphier: add input-delay properties to Cadence eMMC node

Since commit a04e2b383401 ("mmc: sdhci-cadence: Update PHY delay configuration"), PHY parameters must be specified by DT. The hard-coded settings have been converted as follows: - SDHCI_CDNS_PHY_DLY_SD_DEFAULT -> cdns,phy-input-delay-legacy - SDHCI_CDNS_PHY_DLY_EMMC_SDR ->

linux-next: manual merge of the mux tree with the arm-soc tree

Hi all, Today's linux-next merge of the mux tree got conflicts in: drivers/Kconfig drivers/Makefile between commit: 967c9cca2cc5 ("tee: generic TEE subsystem") from the arm-soc tree and commit: 1fc1dd988186 ("mux: minimal mux subsystem and gpio-based mux controller") from the mux

linux-next: manual merge of the mux tree with the arm-soc tree

Hi all, Today's linux-next merge of the mux tree got conflicts in: drivers/Kconfig drivers/Makefile between commit: 967c9cca2cc5 ("tee: generic TEE subsystem") from the arm-soc tree and commit: 1fc1dd988186 ("mux: minimal mux subsystem and gpio-based mux controller") from the mux

[PATCH v3] xfs: Honor FALLOC_FL_KEEP_SIZE when punching ends of files

When punching past EOF on XFS, fallocate(mode=PUNCH_HOLE|KEEP_SIZE) will round the file size up to the nearest multiple of PAGE_SIZE: calvinow@vm-disks/generic-xfs-1 ~$ dd if=/dev/urandom of=test bs=2048 count=1 calvinow@vm-disks/generic-xfs-1 ~$ stat test Size: 2048Blocks: 8

[PATCH v3] xfs: Honor FALLOC_FL_KEEP_SIZE when punching ends of files

When punching past EOF on XFS, fallocate(mode=PUNCH_HOLE|KEEP_SIZE) will round the file size up to the nearest multiple of PAGE_SIZE: calvinow@vm-disks/generic-xfs-1 ~$ dd if=/dev/urandom of=test bs=2048 count=1 calvinow@vm-disks/generic-xfs-1 ~$ stat test Size: 2048Blocks: 8

Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid IO split due to mixed WB_SYNC_ALL and WB_SYNC_NONE

On 03/31, heyunlei wrote: > Hi Jaegeuk, > > Can we split in place update bios into single sbi->f2fs_bio_info for more page > merged in out place update? This case can be show as below: > > in place update submit a bio with one page > out place update submit a bio with one page > in place

Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid IO split due to mixed WB_SYNC_ALL and WB_SYNC_NONE

On 03/31, heyunlei wrote: > Hi Jaegeuk, > > Can we split in place update bios into single sbi->f2fs_bio_info for more page > merged in out place update? This case can be show as below: > > in place update submit a bio with one page > out place update submit a bio with one page > in place

Re: [PATCH 11/16] fpga: intel: fme: add partial reconfiguration sub feature support

On 31/03/2017 4:30 AM, Alan Tull wrote: On Thu, Mar 30, 2017 at 7:08 AM, Wu Hao wrote: From: Kang Luwei Partial Reconfiguration (PR) is the most important function for FME. It allows reconfiguration for given Port/Accelerated Function Unit (AFU).

Re: [PATCH 11/16] fpga: intel: fme: add partial reconfiguration sub feature support

On 31/03/2017 4:30 AM, Alan Tull wrote: On Thu, Mar 30, 2017 at 7:08 AM, Wu Hao wrote: From: Kang Luwei Partial Reconfiguration (PR) is the most important function for FME. It allows reconfiguration for given Port/Accelerated Function Unit (AFU). This patch adds support for PR sub

Re: [PATCH V2 net-next 5/7] tun: support receiving skb through msg_control

On 2017年03月30日 23:06, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:28PM +0800, Jason Wang wrote: This patch makes tun_recvmsg() can receive from skb from its caller through msg_control. Vhost_net will be the first user. Signed-off-by: Jason Wang Do we need to

Re: [PATCH V2 net-next 5/7] tun: support receiving skb through msg_control

On 2017年03月30日 23:06, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:28PM +0800, Jason Wang wrote: This patch makes tun_recvmsg() can receive from skb from its caller through msg_control. Vhost_net will be the first user. Signed-off-by: Jason Wang Do we need to bother with tun? I

Re: [PATCH V2 net-next 6/7] tap: support receiving skb from msg_control

On 2017年03月30日 23:03, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:29PM +0800, Jason Wang wrote: This patch makes tap_recvmsg() can receive from skb from its caller through msg_control. Vhost_net will be the first user. Signed-off-by: Jason Wang ---

Re: [PATCH V2 net-next 6/7] tap: support receiving skb from msg_control

On 2017年03月30日 23:03, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:29PM +0800, Jason Wang wrote: This patch makes tap_recvmsg() can receive from skb from its caller through msg_control. Vhost_net will be the first user. Signed-off-by: Jason Wang --- drivers/net/tap.c | 12

Re: [PATCH] zram: factor out partial IO routine

Hello, On (03/31/17 08:33), Minchan Kim wrote: [..] > > a bigger side effect is that now we double the amount of lines we need > > to change in certain patches and, thus, the amount of work - when we > > add new functionality/fix something in zram_bvec_{write, read} we also > > would need to

Re: [PATCH] zram: factor out partial IO routine

Hello, On (03/31/17 08:33), Minchan Kim wrote: [..] > > a bigger side effect is that now we double the amount of lines we need > > to change in certain patches and, thus, the amount of work - when we > > add new functionality/fix something in zram_bvec_{write, read} we also > > would need to

Re: [PATCH v2] sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable

On Thu, 03/30 11:30, Martin K. Petersen wrote: > Fam Zheng writes: > > >>rw_max = min_not_zero(logical_to_sectors(sdp, dev_max), > >> BLK_DEF_MAX_SECTORS); > > > > Yes, it is better. Is it okay to make the change when you apply? > > Sure.

Re: [PATCH v2] sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable

On Thu, 03/30 11:30, Martin K. Petersen wrote: > Fam Zheng writes: > > >>rw_max = min_not_zero(logical_to_sectors(sdp, dev_max), > >> BLK_DEF_MAX_SECTORS); > > > > Yes, it is better. Is it okay to make the change when you apply? > > Sure. Applied to

Re: [PATCH v3 00/37] mtd: nand: denali: 2nd round of Denali NAND IP patch bomb

Hi Boris, 2017-03-31 1:38 GMT+09:00 Boris Brezillon : > The rest looks almost good, except for a few comments I had on patch > 14, 18, 25, 26 and 32. > > I'll probably apply 33 and 34 soon. > Thank you! Please note I left a minor comment on 34. (Accidental

Re: [PATCH v3 00/37] mtd: nand: denali: 2nd round of Denali NAND IP patch bomb

Hi Boris, 2017-03-31 1:38 GMT+09:00 Boris Brezillon : > The rest looks almost good, except for a few comments I had on patch > 14, 18, 25, 26 and 32. > > I'll probably apply 33 and 34 soon. > Thank you! Please note I left a minor comment on 34. (Accidental addition of braces.) -- Best

Re: [PATCH 1/6] virtio: wrap find_vqs

On 2017年03月30日 22:32, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 02:00:08PM +0800, Jason Wang wrote: On 2017年03月30日 04:48, Michael S. Tsirkin wrote: We are going to add more parameters to find_vqs, let's wrap the call so we don't need to tweak all drivers every time. Signed-off-by:

Re: [PATCH 1/6] virtio: wrap find_vqs

On 2017年03月30日 22:32, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 02:00:08PM +0800, Jason Wang wrote: On 2017年03月30日 04:48, Michael S. Tsirkin wrote: We are going to add more parameters to find_vqs, let's wrap the call so we don't need to tweak all drivers every time. Signed-off-by:

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

On (03/31/17 11:35), Sergey Senozhatsky wrote: [..] > > [ 21.009531] VFS: Warning: trinity-c2 using old stat() call. Recompile > > your binary. > > [ 21.148898] VFS: Warning: trinity-c0 using old stat() call. Recompile > > your binary. > > [ 22.298208] warning: process `trinity-c2' used

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

On (03/31/17 11:35), Sergey Senozhatsky wrote: [..] > > [ 21.009531] VFS: Warning: trinity-c2 using old stat() call. Recompile > > your binary. > > [ 21.148898] VFS: Warning: trinity-c0 using old stat() call. Recompile > > your binary. > > [ 22.298208] warning: process `trinity-c2' used

Re: [PATCH V2 net-next 7/7] vhost_net: try batch dequing from skb array

On 2017年03月30日 22:21, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:30PM +0800, Jason Wang wrote: We used to dequeue one skb during recvmsg() from skb_array, this could be inefficient because of the bad cache utilization which cache does this refer to btw? Both icache and dcache

Re: [PATCH V2 net-next 7/7] vhost_net: try batch dequing from skb array

On 2017年03月30日 22:21, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:30PM +0800, Jason Wang wrote: We used to dequeue one skb during recvmsg() from skb_array, this could be inefficient because of the bad cache utilization which cache does this refer to btw? Both icache and dcache

Re: [PATCH v3 34/37] mtd: nand: allow drivers to request minimum alignment for passed buffer

Hi Boris, 2017-03-30 17:15 GMT+09:00 Masahiro Yamada : > In some cases, nand_do_{read,write}_ops is passed with unaligned > ops->datbuf. Drivers using DMA will be unhappy about unaligned > buffer. > > The new struct member, buf_align, represents the minimum

Re: [PATCH v3 34/37] mtd: nand: allow drivers to request minimum alignment for passed buffer

Hi Boris, 2017-03-30 17:15 GMT+09:00 Masahiro Yamada : > In some cases, nand_do_{read,write}_ops is passed with unaligned > ops->datbuf. Drivers using DMA will be unhappy about unaligned > buffer. > > The new struct member, buf_align, represents the minimum alignment > the driver require for

Re: [PATCH 2/7] iommu/iova: cut down judgement times

On 2017/3/23 20:11, Robin Murphy wrote: > On 22/03/17 06:27, Zhen Lei wrote: >> Below judgement can only be satisfied at the last time, which produced 2N >> judgements(suppose N times failed, 0 or 1 time successed) in vain. >> >> if ((pfn >= iova->pfn_lo) && (pfn <= iova->pfn_hi)) { >>

Re: [PATCH 2/7] iommu/iova: cut down judgement times

On 2017/3/23 20:11, Robin Murphy wrote: > On 22/03/17 06:27, Zhen Lei wrote: >> Below judgement can only be satisfied at the last time, which produced 2N >> judgements(suppose N times failed, 0 or 1 time successed) in vain. >> >> if ((pfn >= iova->pfn_lo) && (pfn <= iova->pfn_hi)) { >>

Re: [f2fs-dev] [PATCH 1/2] f2fs: write small sized IO to hot log

On 03/31, heyunlei wrote: > Hi Jaegeuk, > > On 2017/3/30 4:48, Jaegeuk Kim wrote: > > It would better split small and large IOs separately in order to get more > > consecutive big writes. > > > > The default threshold is set to 64KB, but configurable by > > sysfs/min_hot_blocks. > > > >

Re: [f2fs-dev] [PATCH 1/2] f2fs: write small sized IO to hot log

On 03/31, heyunlei wrote: > Hi Jaegeuk, > > On 2017/3/30 4:48, Jaegeuk Kim wrote: > > It would better split small and large IOs separately in order to get more > > consecutive big writes. > > > > The default threshold is set to 64KB, but configurable by > > sysfs/min_hot_blocks. > > > >

Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid IO split due to mixed WB_SYNC_ALL and WB_SYNC_NONE

Hi Jaegeuk, Can we split in place update bios into single sbi->f2fs_bio_info for more page merged in out place update? This case can be show as below: in place update submit a bio with one page out place update submit a bio with one page in place update submit a bio with one page

Re: [PATCH V2 net-next 1/7] ptr_ring: introduce batch dequeuing

On 2017年03月30日 21:53, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:24PM +0800, Jason Wang wrote: This patch introduce a batched version of consuming, consumer can dequeue more than one pointers from the ring at a time. We don't care about the reorder of reading here so no need for

Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid IO split due to mixed WB_SYNC_ALL and WB_SYNC_NONE

Hi Jaegeuk, Can we split in place update bios into single sbi->f2fs_bio_info for more page merged in out place update? This case can be show as below: in place update submit a bio with one page out place update submit a bio with one page in place update submit a bio with one page

Re: [PATCH V2 net-next 1/7] ptr_ring: introduce batch dequeuing

On 2017年03月30日 21:53, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:24PM +0800, Jason Wang wrote: This patch introduce a batched version of consuming, consumer can dequeue more than one pointers from the ring at a time. We don't care about the reorder of reading here so no need for

Re: [PATCH 3/6] mm: remove return value from init_currently_empty_zone

On March 30, 2017 7:55 PM Michal Hocko wrote: > > From: Michal Hocko > > init_currently_empty_zone doesn't have any error to return yet it is > still an int and callers try to be defensive and try to handle potential > error. Remove this nonsense and simplify all callers. >

Re: [PATCH 3/6] mm: remove return value from init_currently_empty_zone

On March 30, 2017 7:55 PM Michal Hocko wrote: > > From: Michal Hocko > > init_currently_empty_zone doesn't have any error to return yet it is > still an int and callers try to be defensive and try to handle potential > error. Remove this nonsense and simplify all callers. > It is already cut

Re: [RESEND PATCH 2/2] sched/fair: Optimize __update_sched_avg()

On Fri, Mar 31, 2017 at 03:13:55AM +0800, Yuyang Du wrote: > On Thu, Mar 30, 2017 at 04:14:28PM +0200, Peter Zijlstra wrote: > > On Thu, Mar 30, 2017 at 02:16:58PM +0200, Peter Zijlstra wrote: > > > On Thu, Mar 30, 2017 at 04:21:08AM -0700, Paul Turner wrote: > > > > > > > + > > > > > + if

Re: [RESEND PATCH 2/2] sched/fair: Optimize __update_sched_avg()

On Fri, Mar 31, 2017 at 03:13:55AM +0800, Yuyang Du wrote: > On Thu, Mar 30, 2017 at 04:14:28PM +0200, Peter Zijlstra wrote: > > On Thu, Mar 30, 2017 at 02:16:58PM +0200, Peter Zijlstra wrote: > > > On Thu, Mar 30, 2017 at 04:21:08AM -0700, Paul Turner wrote: > > > > > > > + > > > > > + if

Re: [PATCH 4.10 00/17] 4.10.8-stable review

On 03/30/2017 03:00 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.10.8 release. There are 17 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.10 00/17] 4.10.8-stable review

On 03/30/2017 03:00 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.10.8 release. There are 17 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.9 00/16] 4.9.20-stable review

On 03/30/2017 03:15 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.20 release. There are 16 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.9 00/16] 4.9.20-stable review

On 03/30/2017 03:15 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.20 release. There are 16 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.4 00/14] 4.4.59-stable review

On 03/30/2017 02:58 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.59 release. There are 14 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.4 00/14] 4.4.59-stable review

On 03/30/2017 02:58 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.59 release. There are 14 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

[PATCH] treewide: Correct diffrent[iate] and banlance typos

Add these misspellings to scripts/spelling.txt too Signed-off-by: Joe Perches --- drivers/media/dvb-frontends/drx39xyj/drx_dap_fasi.h | 2 +- drivers/net/ethernet/broadcom/bnx2x/bnx2x_sp.c | 2 +- drivers/net/ethernet/hisilicon/hns/hns_enet.c | 2 +-

[PATCH] treewide: Correct diffrent[iate] and banlance typos

Add these misspellings to scripts/spelling.txt too Signed-off-by: Joe Perches --- drivers/media/dvb-frontends/drx39xyj/drx_dap_fasi.h | 2 +- drivers/net/ethernet/broadcom/bnx2x/bnx2x_sp.c | 2 +- drivers/net/ethernet/hisilicon/hns/hns_enet.c | 2 +-

Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid IO split due to mixed WB_SYNC_ALL and WB_SYNC_NONE

Hi Jaegeuk, I try this patch and find it can fix below case: kworker/u16:3-423 [002] 183.812347: submit_bio: kworker/u16:3(423): WRITE block 104749352 on mmcblk0p50 (8 sectors) fio-2122 [003] 183.812380: submit_bio: fio(2122): WRITE block 104749360 on

Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid IO split due to mixed WB_SYNC_ALL and WB_SYNC_NONE

Hi Jaegeuk, I try this patch and find it can fix below case: kworker/u16:3-423 [002] 183.812347: submit_bio: kworker/u16:3(423): WRITE block 104749352 on mmcblk0p50 (8 sectors) fio-2122 [003] 183.812380: submit_bio: fio(2122): WRITE block 104749360 on

  1   2   3   4   5   6   7   8   9   10   >