[PATCH iproute2 2/2] iplink: double the buffer size also in iplink_get()

Commit 72b365e8e0fd ("libnetlink: Double the dump buffer size") increased the buffer size for "ip link show" command to 32 KB to handle NICs with large number of VFs. With "dev" filter, a different code path is taken and iplink_get() still uses only 16 KB buffer. The size of 32768 is not very

[PATCH iproute2 1/2] iplink: check for message truncation in iplink_get()

If message length exceeds maxlen argument of rtnl_talk(), it is truncated to maxlen but unlike in the case of truncation to the length of local buffer in rtnl_talk(), the caller doesn't get any indication of a problem. In particular, iplink_get() passes the truncated message on and parsing it

[PATCH iproute2 0/2] fix "ip link show dev ..." for NICs with many VFs

Two of our customers recently encountered problems with processing of large messages produced by kernel in response to "ip link show" for NICs with many (120-128) virtual functions. While some of them have been already addressed in recent versions of iproute2, some still persist. Patch 1 adds

[PATCH iproute2 0/2] fix "ip link show dev ..." for NICs with many VFs

Two of our customers recently encountered problems with processing of large messages produced by kernel in response to "ip link show" for NICs with many (120-128) virtual functions. While some of them have been already addressed in recent versions of iproute2, some still persist. Patch 1 adds

Re: [PATCH 4/4] lockdep: Fix workqueue crossrelease annotation

On Fri, Sep 01, 2017 at 10:51:48PM +0900, Byungchul Park wrote: > On Fri, Sep 1, 2017 at 9:38 PM, Peter Zijlstra wrote: > > On Fri, Sep 01, 2017 at 07:16:29PM +0900, Byungchul Park wrote: > > > >> It would be gone _only_ at the time the history overrun, and then it > >> will

Re: [PATCH 4/4] lockdep: Fix workqueue crossrelease annotation

On Fri, Sep 01, 2017 at 10:51:48PM +0900, Byungchul Park wrote: > On Fri, Sep 1, 2017 at 9:38 PM, Peter Zijlstra wrote: > > On Fri, Sep 01, 2017 at 07:16:29PM +0900, Byungchul Park wrote: > > > >> It would be gone _only_ at the time the history overrun, and then it > >> will be built again. So,

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Suman, On Fri, Sep 01, 2017 at 11:21:45AM -0500, Suman Anna wrote: > It's primarily a question of whether each iommu platform device need to > be represented as a unique iommu_device or not. If you still think that > both these need to be presented to iommu core as one device, I would > have to

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Suman, On Fri, Sep 01, 2017 at 11:21:45AM -0500, Suman Anna wrote: > It's primarily a question of whether each iommu platform device need to > be represented as a unique iommu_device or not. If you still think that > both these need to be presented to iommu core as one device, I would > have to

[PATCH v2 1/2] ARM: dts: sun8i: h3: Enable AP6212 WiFi on mmc1 on Nanopi M1 Plus

From: Philipp Rossak The WiFi side of the AP6212 WiFi/BT combo module is connected to mmc1. There are also GPIOs for enable and interrupts. Enable WiFi on this board by enabling mmc1 and adding the power sequencing clocks and GPIO, as well as the chip's interrupt line.

[PATCH v2 1/2] ARM: dts: sun8i: h3: Enable AP6212 WiFi on mmc1 on Nanopi M1 Plus

From: Philipp Rossak The WiFi side of the AP6212 WiFi/BT combo module is connected to mmc1. There are also GPIOs for enable and interrupts. Enable WiFi on this board by enabling mmc1 and adding the power sequencing clocks and GPIO, as well as the chip's interrupt line. Signed-off-by: Philipp

[PATCH v2 2/2] ARM: dts: sun8i: h3: Improved Wifi bindings on Bananapi M2 Plus

From: Philipp Rossak * vqmmc is in this case not needed * no need for pincontrol nodes when the pin is set to a GPIO Signed-off-by: Philipp Rossak --- arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts | 7 --- 1 file changed, 7 deletions(-) diff --git

[PATCH v2 2/2] ARM: dts: sun8i: h3: Improved Wifi bindings on Bananapi M2 Plus

From: Philipp Rossak * vqmmc is in this case not needed * no need for pincontrol nodes when the pin is set to a GPIO Signed-off-by: Philipp Rossak --- arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts | 7 --- 1 file changed, 7 deletions(-) diff --git

[PATCH v2 0/2] [DTS] Enable hardware for Nanopi M1 & Nanopi M1 Plus

From: Philipp Rossak This is v2 of my Enable hardware for Nanopi M1 & Nanopi M1 Plus Patchseries. Changes since v1: - removed pincrtl node from power sequence - removed vqmmc-supply - changed ap6212 label to sdio_wifi - removed vqmmc-supply & pincrtl node for

[PATCH v2 0/2] [DTS] Enable hardware for Nanopi M1 & Nanopi M1 Plus

From: Philipp Rossak This is v2 of my Enable hardware for Nanopi M1 & Nanopi M1 Plus Patchseries. Changes since v1: - removed pincrtl node from power sequence - removed vqmmc-supply - changed ap6212 label to sdio_wifi - removed vqmmc-supply & pincrtl node for powersequence on

Re: [RFC PATCH v3] membarrier: provide core serialization

On Fri, Sep 01, 2017 at 12:10:07PM -0400, Mathieu Desnoyers wrote: > Add a new MEMBARRIER_FLAG_SYNC_CORE flag to the membarrier > system call. It allows membarrier to issue core serializing barriers in > addition to memory barriers on target threads whenever a membarrier > command is performed. >

Re: [RFC PATCH v3] membarrier: provide core serialization

On Fri, Sep 01, 2017 at 12:10:07PM -0400, Mathieu Desnoyers wrote: > Add a new MEMBARRIER_FLAG_SYNC_CORE flag to the membarrier > system call. It allows membarrier to issue core serializing barriers in > addition to memory barriers on target threads whenever a membarrier > command is performed. >

Re: Converting struct timer_list callback argument to struct timer_list *

On Fri, Sep 1, 2017 at 3:44 AM, Christoph Hellwig wrote: > On Fri, Sep 01, 2017 at 12:21:46PM +0200, Thomas Gleixner wrote: >> On Fri, 1 Sep 2017, Christoph Hellwig wrote: >> >> > Good work! >> > >> > I just think that the TIMER_CONTAINER name is revolting. >> > >> > The usual

Re: Converting struct timer_list callback argument to struct timer_list *

On Fri, Sep 1, 2017 at 3:44 AM, Christoph Hellwig wrote: > On Fri, Sep 01, 2017 at 12:21:46PM +0200, Thomas Gleixner wrote: >> On Fri, 1 Sep 2017, Christoph Hellwig wrote: >> >> > Good work! >> > >> > I just think that the TIMER_CONTAINER name is revolting. >> > >> > The usual name for such a

Re: Applied "regulator: pbias: Select voltage table based on max-voltage" to the regulator tree

On Fri, Sep 01, 2017 at 03:18:03PM +0200, Ulf Hansson wrote: > On 31 August 2017 at 15:50, Mark Brown wrote: > > On Thu, Aug 31, 2017 at 05:37:34PM +0530, Kishon Vijay Abraham I wrote: > >> This patch should be merged along with the 1st patch of the series "mmc: > >> host: >

Re: Applied "regulator: pbias: Select voltage table based on max-voltage" to the regulator tree

On Fri, Sep 01, 2017 at 03:18:03PM +0200, Ulf Hansson wrote: > On 31 August 2017 at 15:50, Mark Brown wrote: > > On Thu, Aug 31, 2017 at 05:37:34PM +0530, Kishon Vijay Abraham I wrote: > >> This patch should be merged along with the 1st patch of the series "mmc: > >> host: > >> omap_hsmmc:

[PATCH] tools/power/acpi: fix acpi power tool building error

When we tried to build acpi power tool, just like the following: $make tools/acpi ... ... can't create power/acpi/tools/acpidbg/acpidbg.o: No such file or directory ... ... Root cause is that the 'tools' folder in the path 'power/acpi/tools/acpidbg/acpidbg.o' doesn't exist. Signed-off-by:

[PATCH] tools/power/acpi: fix acpi power tool building error

When we tried to build acpi power tool, just like the following: $make tools/acpi ... ... can't create power/acpi/tools/acpidbg/acpidbg.o: No such file or directory ... ... Root cause is that the 'tools' folder in the path 'power/acpi/tools/acpidbg/acpidbg.o' doesn't exist. Signed-off-by:

Re: [PATCH 2/3] watchdog: Add Realtek RTD1295

On 08/28/2017 04:35 AM, Andreas Färber wrote: Add a watchdog driver for the Realtek RTD1295 SoC. Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_watchdog.c code and mach-rtk119x/driver/dc2vo/fpga/include/iso_reg.h register defines. Signed-off-by: Andreas Färber ---

Re: [PATCH 2/3] watchdog: Add Realtek RTD1295

On 08/28/2017 04:35 AM, Andreas Färber wrote: Add a watchdog driver for the Realtek RTD1295 SoC. Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_watchdog.c code and mach-rtk119x/driver/dc2vo/fpga/include/iso_reg.h register defines. Signed-off-by: Andreas Färber --- drivers/watchdog/Kconfig

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Joerg, On 09/01/2017 05:01 AM, Joerg Roedel wrote: > Hi Suman, > > On Thu, Aug 31, 2017 at 08:14:02AM -0500, Suman Anna wrote: >> The OMAP IOMMU driver has been enhanced to support allowing >> multiple IOMMUs to be programmed by a single client user. This >> support is being added mainly to

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Joerg, On 09/01/2017 05:01 AM, Joerg Roedel wrote: > Hi Suman, > > On Thu, Aug 31, 2017 at 08:14:02AM -0500, Suman Anna wrote: >> The OMAP IOMMU driver has been enhanced to support allowing >> multiple IOMMUs to be programmed by a single client user. This >> support is being added mainly to

Re: virtio_net: ethtool supported link modes

On Fri, 2017-09-01 at 18:43 +0300, Michael S. Tsirkin wrote: > On Thu, Aug 31, 2017 at 06:04:04PM +0100, Radu Rendec wrote: > > Looking at the code in virtnet_set_link_ksettings, it seems the speed > > and duplex can be set to any valid value. The driver will "remember" > > them and report them

Re: virtio_net: ethtool supported link modes

On Fri, 2017-09-01 at 18:43 +0300, Michael S. Tsirkin wrote: > On Thu, Aug 31, 2017 at 06:04:04PM +0100, Radu Rendec wrote: > > Looking at the code in virtnet_set_link_ksettings, it seems the speed > > and duplex can be set to any valid value. The driver will "remember" > > them and report them

Re: [PATCH 1/1] perf stat: Only auto-merge events that are PMU aliases

On Thu, Aug 31, 2017 at 03:41:22PM -0300, Arnaldo Carvalho de Melo wrote: > Hi Andi, Jiri, > > Please check the patch below, would be glad to have your acks, > > - Arnaldo > > Peter reported that when he explicitely asked for multiple events with > the same name on the command line it got

Re: [PATCH 1/1] perf stat: Only auto-merge events that are PMU aliases

On Thu, Aug 31, 2017 at 03:41:22PM -0300, Arnaldo Carvalho de Melo wrote: > Hi Andi, Jiri, > > Please check the patch below, would be glad to have your acks, > > - Arnaldo > > Peter reported that when he explicitely asked for multiple events with > the same name on the command line it got

[RFC PATCH v3] membarrier: provide core serialization

Add a new MEMBARRIER_FLAG_SYNC_CORE flag to the membarrier system call. It allows membarrier to issue core serializing barriers in addition to memory barriers on target threads whenever a membarrier command is performed. It is relevant for reclaim of JIT code, which requires to issue core

[RFC PATCH v3] membarrier: provide core serialization

Add a new MEMBARRIER_FLAG_SYNC_CORE flag to the membarrier system call. It allows membarrier to issue core serializing barriers in addition to memory barriers on target threads whenever a membarrier command is performed. It is relevant for reclaim of JIT code, which requires to issue core

[patch v7 4/4] Documentation: jtag: Add ABI documentation

Added document that describe the ABI for JTAG class drivrer Signed-off-by: Oleksandr Shamray --- v6->v7 Comments pointed by Pavel Machek - Added jtag-cdev documentation to Documentation/ABI/testing folder --- Documentation/ABI/testing/jatg-cdev | 27

[patch v7 4/4] Documentation: jtag: Add ABI documentation

Added document that describe the ABI for JTAG class drivrer Signed-off-by: Oleksandr Shamray --- v6->v7 Comments pointed by Pavel Machek - Added jtag-cdev documentation to Documentation/ABI/testing folder --- Documentation/ABI/testing/jatg-cdev | 27 +++ MAINTAINERS

[patch v7 3/4] Documentation: jtag: Add bindings for Aspeed SoC 24xx and 25xx families JTAG master driver

It has been tested on Mellanox system with BMC equipped with Aspeed 2520 SoC for programming CPLD devices. Signed-off-by: Oleksandr Shamray Signed-off-by: Jiri Pirko Acked-by: Rob Herring --- V6->v7 Comments pointed by Tobias Klauser

[patch v7 3/4] Documentation: jtag: Add bindings for Aspeed SoC 24xx and 25xx families JTAG master driver

It has been tested on Mellanox system with BMC equipped with Aspeed 2520 SoC for programming CPLD devices. Signed-off-by: Oleksandr Shamray Signed-off-by: Jiri Pirko Acked-by: Rob Herring --- V6->v7 Comments pointed by Tobias Klauser - Fix spell "Doccumentation" -> "Documentation" v5->v6

[patch v7 1/4] drivers: jtag: Add JTAG core driver

Initial patch for JTAG friver JTAG class driver provide infrastructure to support hardware/software JTAG platform drivers. It provide user layer API interface for flashing and debugging external devices which equipped with JTAG interface using standard transactions. Driver exposes set of IOCTL to

[patch v7 1/4] drivers: jtag: Add JTAG core driver

Initial patch for JTAG friver JTAG class driver provide infrastructure to support hardware/software JTAG platform drivers. It provide user layer API interface for flashing and debugging external devices which equipped with JTAG interface using standard transactions. Driver exposes set of IOCTL to

[patch v7 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Driver adds support of Aspeed 2500/2400 series SOC JTAG master controller. Driver implements the following jtag ops: - freq_get; - freq_set; - status_get; - idle; - xfer; It has been tested on Mellanox system with BMC equipped with Aspeed 2520 SoC for programming CPLD devices. Signed-off-by:

[patch v7 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Driver adds support of Aspeed 2500/2400 series SOC JTAG master controller. Driver implements the following jtag ops: - freq_get; - freq_set; - status_get; - idle; - xfer; It has been tested on Mellanox system with BMC equipped with Aspeed 2520 SoC for programming CPLD devices. Signed-off-by:

[patch v7 0/4] JTAG driver introduction

When a need raise up to use JTAG interface for system's devices programming or CPU debugging, usually the user layer application implements jtag protocol by bit-bang or using a proprietary connection to vendor hardware. This method can be slow and not generic. We propose to implement general

[patch v7 0/4] JTAG driver introduction

When a need raise up to use JTAG interface for system's devices programming or CPU debugging, usually the user layer application implements jtag protocol by bit-bang or using a proprietary connection to vendor hardware. This method can be slow and not generic. We propose to implement general

[PATCH] phy: xgene: make array serdes_reg static const

From: Colin Ian King Don't populate the array serdes_reg on the stack, instead make it static const. Makes the object code smaller by 150 bytes: Before: textdata bss dec hex filename 218906432 64 283866ee2 drivers/phy/phy-xgene.o

[PATCH] phy: xgene: make array serdes_reg static const

From: Colin Ian King Don't populate the array serdes_reg on the stack, instead make it static const. Makes the object code smaller by 150 bytes: Before: textdata bss dec hex filename 218906432 64 283866ee2 drivers/phy/phy-xgene.o After: textdata

[GIT PULL] Ceph fix for 4.13-rc8

Hi Linus, The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98: Linux 4.13-rc7 (2017-08-27 17:20:40 -0700) are available in the git repository at: https://github.com/ceph/ceph-client.git tags/ceph-for-4.13-rc8 for you to fetch changes up to

[GIT PULL] Ceph fix for 4.13-rc8

Hi Linus, The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98: Linux 4.13-rc7 (2017-08-27 17:20:40 -0700) are available in the git repository at: https://github.com/ceph/ceph-client.git tags/ceph-for-4.13-rc8 for you to fetch changes up to

Re: [PATCH 19/25] can/bcm: Replace hrtimer_tasklet with softirq based hrtimer

On Fri, 1 Sep 2017, Oliver Hartkopp wrote: > Hi Anna-Maria & Thomas, > > thanks for the effort! > > I'm really happy that the hrtimer becomes softirq capable as it basically > reverts this ugly commit from January 2009: > >

Re: [PATCH 19/25] can/bcm: Replace hrtimer_tasklet with softirq based hrtimer

On Fri, 1 Sep 2017, Oliver Hartkopp wrote: > Hi Anna-Maria & Thomas, > > thanks for the effort! > > I'm really happy that the hrtimer becomes softirq capable as it basically > reverts this ugly commit from January 2009: > >

Re: [PATCH v3 2/5] dt-bindings: scsi: ufs: add document for hisi-ufs

On Tue, Aug 29, 2017 at 04:41:13PM +0800, Li Wei wrote: > add ufs node document for Hisilicon > > Signed-off-by: Li Wei > --- > Documentation/devicetree/bindings/ufs/ufs-hisi.txt | 35 > ++ > 1 file changed, 35 insertions(+) > create mode 100644

Re: [PATCH v3 2/5] dt-bindings: scsi: ufs: add document for hisi-ufs

On Tue, Aug 29, 2017 at 04:41:13PM +0800, Li Wei wrote: > add ufs node document for Hisilicon > > Signed-off-by: Li Wei > --- > Documentation/devicetree/bindings/ufs/ufs-hisi.txt | 35 > ++ > 1 file changed, 35 insertions(+) > create mode 100644

[RFC PATCH 00/11] AFS: Namespacing part 1

Here are some changes to the AFS filesystem that form the first part of network-namespacing and IPv6 enabling the AFS filesystem. AF_RXRPC is already namespaced. This is built on AF_RXRPC changes tagged with rxrpc-next-20170829 (which is also in net-next). The AFS changes are: (1) Create a

[RFC PATCH 00/11] AFS: Namespacing part 1

Here are some changes to the AFS filesystem that form the first part of network-namespacing and IPv6 enabling the AFS filesystem. AF_RXRPC is already namespaced. This is built on AF_RXRPC changes tagged with rxrpc-next-20170829 (which is also in net-next). The AFS changes are: (1) Create a

Re: [RFC PATCH v1 1/3] arm64/ras: support sea error recovery

Hi Xie, On 01/09/17 11:31, Xie XiuQi wrote: With ARM v8.2 RAS Extension, SEA are usually triggered when memory errors are consumed. In some cases, if the error address is in a clean page or a read-only page, there is a chance to recover. Such as error occurs in a instruction page, we can reread

Re: [RFC PATCH v1 1/3] arm64/ras: support sea error recovery

Hi Xie, On 01/09/17 11:31, Xie XiuQi wrote: With ARM v8.2 RAS Extension, SEA are usually triggered when memory errors are consumed. In some cases, if the error address is in a clean page or a read-only page, there is a chance to recover. Such as error occurs in a instruction page, we can reread

Re: [PATCH net] vhost_net: correctly check tx avail during rx busy polling

On Fri, Sep 01, 2017 at 05:02:50PM +0800, Jason Wang wrote: > We check tx avail through vhost_enable_notify() in the past which is > wrong since it only checks whether or not guest has filled more > available buffer since last avail idx synchronization which was just > done by

Re: [PATCH net] vhost_net: correctly check tx avail during rx busy polling

On Fri, Sep 01, 2017 at 05:02:50PM +0800, Jason Wang wrote: > We check tx avail through vhost_enable_notify() in the past which is > wrong since it only checks whether or not guest has filled more > available buffer since last avail idx synchronization which was just > done by

Re: [PATCH 19/25] can/bcm: Replace hrtimer_tasklet with softirq based hrtimer

Hi Anna-Maria & Thomas, thanks for the effort! I'm really happy that the hrtimer becomes softirq capable as it basically reverts this ugly commit from January 2009: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=6e5c172cf7ca1ab878cc6a6a4c1d52fef60f3ee0 From the

Re: [PATCH 19/25] can/bcm: Replace hrtimer_tasklet with softirq based hrtimer

Hi Anna-Maria & Thomas, thanks for the effort! I'm really happy that the hrtimer becomes softirq capable as it basically reverts this ugly commit from January 2009: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=6e5c172cf7ca1ab878cc6a6a4c1d52fef60f3ee0 From the

Re: [Patch v3 02/19] CIFS: SMBD: Add SMBDirect protocol and transport constants

Probably easier to configure in /proc/fs/cifs than as module param On Wed, Aug 30, 2017 at 1:30 PM, Pavel Shilovsky via samba-technical wrote: > 2017-08-30 11:24 GMT-07:00 Long Li : >>> -Original Message- >>> From: Pavel Shilovsky

Re: [Patch v3 02/19] CIFS: SMBD: Add SMBDirect protocol and transport constants

Probably easier to configure in /proc/fs/cifs than as module param On Wed, Aug 30, 2017 at 1:30 PM, Pavel Shilovsky via samba-technical wrote: > 2017-08-30 11:24 GMT-07:00 Long Li : >>> -Original Message- >>> From: Pavel Shilovsky [mailto:piastr...@gmail.com] >>> Sent: Wednesday, August

[PATCH V13 3/4] powerpc/hotplug: Improve responsiveness of hotplug change

powerpc/hotplug: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. During hotplug CPU operations, this patch resets the timer on topology update work function to a small

[PATCH V13 4/4] powerpc/vphn: Fix numa update end-loop bug

powerpc/vphn: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch fixes an end-of-updates processing problem observed occasionally in numa_update_cpu_topology().

[PATCH V13 3/4] powerpc/hotplug: Improve responsiveness of hotplug change

powerpc/hotplug: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. During hotplug CPU operations, this patch resets the timer on topology update work function to a small

[PATCH V13 4/4] powerpc/vphn: Fix numa update end-loop bug

powerpc/vphn: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch fixes an end-of-updates processing problem observed occasionally in numa_update_cpu_topology().

[PATCH V13 1/4] powerpc/vphn: Update CPU topology when VPHN enabled

powerpc/vphn: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch corrects the currently broken capability to set the topology for shared CPUs in LPARs. At boot

[PATCH V13 2/4] powerpc/vphn: Improve recognition of PRRN/VPHN

powerpc/vphn: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch updates the initialization checks to independently recognize PRRN or VPHN support. Signed-off-by:

[PATCH V13 1/4] powerpc/vphn: Update CPU topology when VPHN enabled

powerpc/vphn: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch corrects the currently broken capability to set the topology for shared CPUs in LPARs. At boot

[PATCH V13 2/4] powerpc/vphn: Improve recognition of PRRN/VPHN

powerpc/vphn: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch updates the initialization checks to independently recognize PRRN or VPHN support. Signed-off-by:

[PATCH V13 0/4] powerpc/vphn: Update CPU topology when VPHN enabled

powerpc/numa: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch addresses some of those problems. First, it corrects the currently broken capability to set the

[PATCH 02/17] autofs4: switch autofs4_write to __kernel_write

Instead of playing games with the address limit.. Signed-off-by: Christoph Hellwig --- fs/autofs4/waitq.c | 9 + 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/fs/autofs4/waitq.c b/fs/autofs4/waitq.c index 24a58bf9ca72..4ac49d038bf3 100644 ---

[PATCH V13 0/4] powerpc/vphn: Update CPU topology when VPHN enabled

powerpc/numa: On Power systems with shared configurations of CPUs and memory, there are some issues with the association of additional CPUs and memory to nodes when hot-adding resources. This patch addresses some of those problems. First, it corrects the currently broken capability to set the

[PATCH 02/17] autofs4: switch autofs4_write to __kernel_write

Instead of playing games with the address limit.. Signed-off-by: Christoph Hellwig --- fs/autofs4/waitq.c | 9 + 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/fs/autofs4/waitq.c b/fs/autofs4/waitq.c index 24a58bf9ca72..4ac49d038bf3 100644 --- a/fs/autofs4/waitq.c +++

[PATCH 05/17] fs: fix kernel_read prototype

Use proper ssize_t and size_t types for the return value and count argument, move the offset last and make it an in/out argument like all other read/write helpers, and make the buf argument a void pointer to get rid of lots of casts in the callers. Signed-off-by: Christoph Hellwig

[PATCH 05/17] fs: fix kernel_read prototype

Use proper ssize_t and size_t types for the return value and count argument, move the offset last and make it an in/out argument like all other read/write helpers, and make the buf argument a void pointer to get rid of lots of casts in the callers. Signed-off-by: Christoph Hellwig ---

[PATCH 04/17] fs: move kernel_read to fs/read_write.c

Signed-off-by: Christoph Hellwig --- fs/exec.c | 17 - fs/read_write.c | 16 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/fs/exec.c b/fs/exec.c index 62175cbcc801..8adcc5eaa175 100644 --- a/fs/exec.c +++ b/fs/exec.c @@

[PATCH 04/17] fs: move kernel_read to fs/read_write.c

Signed-off-by: Christoph Hellwig --- fs/exec.c | 17 - fs/read_write.c | 16 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/fs/exec.c b/fs/exec.c index 62175cbcc801..8adcc5eaa175 100644 --- a/fs/exec.c +++ b/fs/exec.c @@ -885,23 +885,6 @@

[PATCH 08/17] serial2002: switch serial2002_tty_write to kernel_{read/write}

Instead of playing games with the address limit. This also gains us proper usage of the write counter, time stamp updates and kvec validation. Signed-off-by: Christoph Hellwig --- drivers/staging/comedi/drivers/serial2002.c | 24 +--- 1 file changed, 5

[PATCH 08/17] serial2002: switch serial2002_tty_write to kernel_{read/write}

Instead of playing games with the address limit. This also gains us proper usage of the write counter, time stamp updates and kvec validation. Signed-off-by: Christoph Hellwig --- drivers/staging/comedi/drivers/serial2002.c | 24 +--- 1 file changed, 5 insertions(+), 19

[PATCH 06/17] fs: fix kernel_write prototype

Make the position an in/out argument like all the other read/write helpers and and make the buf argument a void pointer. Signed-off-by: Christoph Hellwig --- drivers/mtd/nand/nandsim.c| 2 +- drivers/target/target_core_alua.c | 3 ++- drivers/target/target_core_file.c | 2

[PATCH 06/17] fs: fix kernel_write prototype

Make the position an in/out argument like all the other read/write helpers and and make the buf argument a void pointer. Signed-off-by: Christoph Hellwig --- drivers/mtd/nand/nandsim.c| 2 +- drivers/target/target_core_alua.c | 3 ++- drivers/target/target_core_file.c | 2 +-

[PATCH 09/17] mm/nommu: switch do_mmap_private to kernel_read

Instead of playing with the address limit. This also gains us validation of the kvec and proper atime updates. Signed-off-by: Christoph Hellwig --- mm/nommu.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/mm/nommu.c b/mm/nommu.c index

[PATCH 09/17] mm/nommu: switch do_mmap_private to kernel_read

Instead of playing with the address limit. This also gains us validation of the kvec and proper atime updates. Signed-off-by: Christoph Hellwig --- mm/nommu.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/mm/nommu.c b/mm/nommu.c index fc184f597d59..e907a25ec9bd

[PATCH 11/17] btrfs: switch write_buf to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig Reviewed-by: Nikolay Borisov --- fs/btrfs/send.c | 18 -- 1 file changed, 4 insertions(+), 14 deletions(-) diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c index

[PATCH 11/17] btrfs: switch write_buf to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig Reviewed-by: Nikolay Borisov --- fs/btrfs/send.c | 18 -- 1 file changed, 4 insertions(+), 14 deletions(-) diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c index b082210df9c8..24b989fd130c 100644 ---

[PATCH 10/17] net/9p: switch p9_fd_read to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig --- net/9p/trans_fd.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/net/9p/trans_fd.c b/net/9p/trans_fd.c index f12815777beb..903a190319b9 100644 --- a/net/9p/trans_fd.c

[PATCH 12/17] mconsole: switch to kernel_read

Instead of playing with address limits. Signed-off-by: Christoph Hellwig --- arch/um/drivers/mconsole_kern.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/arch/um/drivers/mconsole_kern.c b/arch/um/drivers/mconsole_kern.c index af326fb6510d..c4d162a94be9

[PATCH 10/17] net/9p: switch p9_fd_read to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig --- net/9p/trans_fd.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/net/9p/trans_fd.c b/net/9p/trans_fd.c index f12815777beb..903a190319b9 100644 --- a/net/9p/trans_fd.c +++

[PATCH 12/17] mconsole: switch to kernel_read

Instead of playing with address limits. Signed-off-by: Christoph Hellwig --- arch/um/drivers/mconsole_kern.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/arch/um/drivers/mconsole_kern.c b/arch/um/drivers/mconsole_kern.c index af326fb6510d..c4d162a94be9 100644 ---

Re: [PATCH V2 0/5] support PERF_SAMPLE_PHYS_ADDR (user)

On Tue, Aug 29, 2017 at 01:11:07PM -0400, kan.li...@intel.com wrote: > From: Kan Liang > > The patch series is to support PERF_SAMPLE_PHYS_ADDR in user perf tool. > The kernel patch has been merged, which commit ID is > fc7ce9c74c3a ("perf/core, x86: Add

Re: [PATCH V2 0/5] support PERF_SAMPLE_PHYS_ADDR (user)

On Tue, Aug 29, 2017 at 01:11:07PM -0400, kan.li...@intel.com wrote: > From: Kan Liang > > The patch series is to support PERF_SAMPLE_PHYS_ADDR in user perf tool. > The kernel patch has been merged, which commit ID is > fc7ce9c74c3a ("perf/core, x86: Add PERF_SAMPLE_PHYS_ADDR"). > > Changes

[PATCH 14/17] lustre: switch to kernel_write

Signed-off-by: Christoph Hellwig --- drivers/staging/lustre/lnet/libcfs/tracefile.c | 10 ++ drivers/staging/lustre/lustre/obdclass/kernelcomm.c | 7 +-- 2 files changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/staging/lustre/lnet/libcfs/tracefile.c

[PATCH 14/17] lustre: switch to kernel_write

Signed-off-by: Christoph Hellwig --- drivers/staging/lustre/lnet/libcfs/tracefile.c | 10 ++ drivers/staging/lustre/lustre/obdclass/kernelcomm.c | 7 +-- 2 files changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/staging/lustre/lnet/libcfs/tracefile.c

Re: virtio_net: ethtool supported link modes

On Thu, Aug 31, 2017 at 06:04:04PM +0100, Radu Rendec wrote: > Hello, > > Looking at the code in virtnet_set_link_ksettings, it seems the speed > and duplex can be set to any valid value. The driver will "remember" > them and report them back in virtnet_get_link_ksettings. > > However, the

Re: virtio_net: ethtool supported link modes

On Thu, Aug 31, 2017 at 06:04:04PM +0100, Radu Rendec wrote: > Hello, > > Looking at the code in virtnet_set_link_ksettings, it seems the speed > and duplex can be set to any valid value. The driver will "remember" > them and report them back in virtnet_get_link_ksettings. > > However, the

[RFC PATCH 07/11] afs: Update the cache index structure

Update the cache index structure in the following ways: (1) Don't use the volume name followed by the volume type as levels in the cache index. Volumes can be renamed. Use the volume ID instead. (2) Don't store the VLDB data for a volume in the tree. If the volume database should

[RFC PATCH 07/11] afs: Update the cache index structure

Update the cache index structure in the following ways: (1) Don't use the volume name followed by the volume type as levels in the cache index. Volumes can be renamed. Use the volume ID instead. (2) Don't store the VLDB data for a volume in the tree. If the volume database should

[RFC PATCH 11/11] afs: Retry rxrpc calls with address rotation on network error

When a network error occurs when we attempt a call, we want to rotate the set of addresses we have for that peer and try the call again. Use the new AF_RXRPC call-retrying facility to do this, thereby avoiding the need to re-encrypt each time as this allows us to reuse the Tx-queue from the dead

[RFC PATCH 11/11] afs: Retry rxrpc calls with address rotation on network error

When a network error occurs when we attempt a call, we want to rotate the set of addresses we have for that peer and try the call again. Use the new AF_RXRPC call-retrying facility to do this, thereby avoiding the need to re-encrypt each time as this allows us to reuse the Tx-queue from the dead

[RFC PATCH 09/11] afs: Allow IPv6 address specification of VL servers

Allow VL server specifications to be given IPv6 addresses as well as IPv4 addresses, for example as: echo add procyon.org.uk :::0:::: >/proc/fs/afs/cells Note that ':' is the expected separator for separating IPv4 addresses, but if a ',' is detected or no '.'

[RFC PATCH 10/11] afs: Overhaul cell database management

Overhaul the way that the in-kernel AFS client keeps track of cells in the following manner: (1) Cells are now held in an rbtree to make walking them quicker and RCU managed (though this is probably overkill). (2) Cells now have a manager work item that: (A) Looks after fetching and

<    1   2   3   4   5   6   7   8   9   10   >