Re: CPU_BIG_ENDIAN in generic code (was: Re: [PATCH v3 3/7] arch/sparc: Define config parameter CPU_BIG_ENDIAN)

Geert Uytterhoeven writes: > On Tue, May 23, 2017 at 11:45 PM, Babu Moger wrote: >> Found this problem while enabling queued rwlock on SPARC. >> The parameter CONFIG_CPU_BIG_ENDIAN is used to clear the >> specific byte in qrwlock structure. Without

Re: [PATCH 3/3] mm, memory_hotplug: move movable_node to the hotplug proper

On 05/29/2017 01:41 PM, Michal Hocko wrote: > From: Michal Hocko > > movable_node_is_enabled is defined in memblock proper while it > is initialized from the memory hotplug proper. This is quite messy > and it makes a dependency between the two so move movable_node along > with

Re: Setting ->s_dev to a char device (Was: Re: [PATCH v2] ubifs: allow userspace to map mounts to volumes)

On Mon, May 29, 2017 at 01:50:30PM +0200, Richard Weinberger wrote: > CC'ing VFS folks > > Am 29.05.2017 um 09:22 schrieb Rabin Vincent: > > From: Rabin Vincent > > > > There currently appears to be no way for userspace to find out the > > underlying volume number for a mounted

Re: CPU_BIG_ENDIAN in generic code (was: Re: [PATCH v3 3/7] arch/sparc: Define config parameter CPU_BIG_ENDIAN)

Geert Uytterhoeven writes: > On Tue, May 23, 2017 at 11:45 PM, Babu Moger wrote: >> Found this problem while enabling queued rwlock on SPARC. >> The parameter CONFIG_CPU_BIG_ENDIAN is used to clear the >> specific byte in qrwlock structure. Without this parameter, >> we clear the wrong byte.

Re: [PATCH 3/3] mm, memory_hotplug: move movable_node to the hotplug proper

On 05/29/2017 01:41 PM, Michal Hocko wrote: > From: Michal Hocko > > movable_node_is_enabled is defined in memblock proper while it > is initialized from the memory hotplug proper. This is quite messy > and it makes a dependency between the two so move movable_node along > with the helper

Re: Setting ->s_dev to a char device (Was: Re: [PATCH v2] ubifs: allow userspace to map mounts to volumes)

On Mon, May 29, 2017 at 01:50:30PM +0200, Richard Weinberger wrote: > CC'ing VFS folks > > Am 29.05.2017 um 09:22 schrieb Rabin Vincent: > > From: Rabin Vincent > > > > There currently appears to be no way for userspace to find out the > > underlying volume number for a mounted ubifs file

Re: [PATCH 2/3] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE

On 05/29/2017 01:41 PM, Michal Hocko wrote: > From: Michal Hocko > > 20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated > node") has introduced CONFIG_MOVABLE_NODE without a good explanation on > why it is actually useful. It makes a lot of sense to make movable

Re: [PATCH 2/3] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE

On 05/29/2017 01:41 PM, Michal Hocko wrote: > From: Michal Hocko > > 20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated > node") has introduced CONFIG_MOVABLE_NODE without a good explanation on > why it is actually useful. It makes a lot of sense to make movable node > semantic

[PATCH v8 net-next 07/17] net: qca_spi: remove QCASPI_MTU

There is no need for an additional MTU define. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_spi.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_spi.c

[PATCH v8 net-next 07/17] net: qca_spi: remove QCASPI_MTU

There is no need for an additional MTU define. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_spi.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_spi.c b/drivers/net/ethernet/qualcomm/qca_spi.c index f155548..7464628

Re: [PATCH]: perf/core: addressing 4x slowdown during per-process profiling of STREAM benchmark on Intel Xeon Phi

Alexey Budankov writes: Here (above the function) you could include a comment describing what happens when this is called, locking considerations, etc. > +static int > +perf_cpu_tree_insert(struct rb_root *tree, struct perf_event *event) > +{ > + struct

[PATCH v8 net-next 08/17] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c

The function qcaspi_tx_cmd() is only called from qca_spi.c. So we better move it there. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 24 drivers/net/ethernet/qualcomm/qca_7k.h | 1 -

Re: [PATCH]: perf/core: addressing 4x slowdown during per-process profiling of STREAM benchmark on Intel Xeon Phi

Alexey Budankov writes: Here (above the function) you could include a comment describing what happens when this is called, locking considerations, etc. > +static int > +perf_cpu_tree_insert(struct rb_root *tree, struct perf_event *event) > +{ > + struct rb_node **node; > + struct

[PATCH v8 net-next 08/17] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c

The function qcaspi_tx_cmd() is only called from qca_spi.c. So we better move it there. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 24 drivers/net/ethernet/qualcomm/qca_7k.h | 1 - drivers/net/ethernet/qualcomm/qca_spi.c | 24

[PATCH v8 net-next 15/17] dt-bindings: slave-device: add current-speed property

This adds a new DT property to define the current baud rate of the slave device. Signed-off-by: Stefan Wahren Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/serial/slave-device.txt | 9 + 1 file changed, 9 insertions(+) diff

Re: [PATCH 1/7] dmaengine: use proper name for the R-Car SoC

Geert, thanks for the Acks. > I'd fix "SH/R-Mobile" too, while at it. That would be a seperate tree-wide series in my book. Regards, Wolfram signature.asc Description: PGP signature

[PATCH v8 net-next 15/17] dt-bindings: slave-device: add current-speed property

This adds a new DT property to define the current baud rate of the slave device. Signed-off-by: Stefan Wahren Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/serial/slave-device.txt | 9 + 1 file changed, 9 insertions(+) diff --git

Re: [PATCH 1/7] dmaengine: use proper name for the R-Car SoC

Geert, thanks for the Acks. > I'd fix "SH/R-Mobile" too, while at it. That would be a seperate tree-wide series in my book. Regards, Wolfram signature.asc Description: PGP signature

[PATCH v8 net-next 12/17] net: qualcomm: make qca_7k_common a separate kernel module

In order to share common functions between QCA7000 SPI and UART protocol driver the qca_7k_common needs to be a separate kernel module. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Kconfig | 8 +++- drivers/net/ethernet/qualcomm/Makefile

[PATCH v8 net-next 12/17] net: qualcomm: make qca_7k_common a separate kernel module

In order to share common functions between QCA7000 SPI and UART protocol driver the qca_7k_common needs to be a separate kernel module. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Kconfig | 8 +++- drivers/net/ethernet/qualcomm/Makefile| 5 +++--

Re: [PATCH 6/7] [media] soc_camera: rcar_vin: use proper name for the R-Car SoC

>Why "soc_camera:" in the subject? I used 'git log $file' and copied the most recent entry. Do I need to resend? signature.asc Description: PGP signature

Re: [PATCH 6/7] [media] soc_camera: rcar_vin: use proper name for the R-Car SoC

>Why "soc_camera:" in the subject? I used 'git log $file' and copied the most recent entry. Do I need to resend? signature.asc Description: PGP signature

[PATCH v8 net-next 13/17] dt-bindings: qca7000-spi: Rework binding

In preparation for the QCA7000 UART binding rework the binding document. Signed-off-by: Stefan Wahren --- .../devicetree/bindings/net/qca-qca7000-spi.txt| 49 +- 1 file changed, 29 insertions(+), 20 deletions(-) diff --git

[PATCH v8 net-next 13/17] dt-bindings: qca7000-spi: Rework binding

In preparation for the QCA7000 UART binding rework the binding document. Signed-off-by: Stefan Wahren --- .../devicetree/bindings/net/qca-qca7000-spi.txt| 49 +- 1 file changed, 29 insertions(+), 20 deletions(-) diff --git

Re: [PATCH RFC 0/5] *** SPI Slave mode support ***

Hi Jiada, On Thu, Apr 27, 2017 at 3:43 AM, Jiada Wang wrote: > BUT if you think the use case don't need to be supported from SPI core, > then I don't have objection either, I will only submit imx SPI slave support > patch, > after your SPI slave support patch set been

Re: [PATCH RFC 0/5] *** SPI Slave mode support ***

Hi Jiada, On Thu, Apr 27, 2017 at 3:43 AM, Jiada Wang wrote: > BUT if you think the use case don't need to be supported from SPI core, > then I don't have objection either, I will only submit imx SPI slave support > patch, > after your SPI slave support patch set been applied Geert's SPI slave

[PATCH v8 net-next 11/17] net: qualcomm: prepare frame decoding for UART driver

Unfortunately the frame format is not exactly identical between SPI and UART. In case of SPI there is an additional HW length at the beginning. So store the initial state to make the decoding state machine more flexible and easy to extend for UART support. Signed-off-by: Stefan Wahren

[PATCH v8 net-next 11/17] net: qualcomm: prepare frame decoding for UART driver

Unfortunately the frame format is not exactly identical between SPI and UART. In case of SPI there is an additional HW length at the beginning. So store the initial state to make the decoding state machine more flexible and easy to extend for UART support. Signed-off-by: Stefan Wahren ---

[PATCH v8 net-next 00/17] net: qualcomm: add QCA7000 UART driver

The Qualcomm QCA7000 HomePlug GreenPHY supports two interfaces: UART and SPI. This patch series adds the missing support for UART. This driver based on the Qualcomm code [1], but contains some changes: * use random MAC address per default * use net_device_stats from device * share frame decoding

[PATCH v8 net-next 00/17] net: qualcomm: add QCA7000 UART driver

The Qualcomm QCA7000 HomePlug GreenPHY supports two interfaces: UART and SPI. This patch series adds the missing support for UART. This driver based on the Qualcomm code [1], but contains some changes: * use random MAC address per default * use net_device_stats from device * share frame decoding

[PATCH v8 net-next 16/17] dt-bindings: qca7000: append UART interface to binding

This merges the serdev binding for the QCA7000 UART driver (Ethernet over UART) into the existing document. Signed-off-by: Stefan Wahren --- .../devicetree/bindings/net/qca,qca7000.txt| 32 ++ 1 file changed, 32 insertions(+) diff --git

[PATCH v8 net-next 16/17] dt-bindings: qca7000: append UART interface to binding

This merges the serdev binding for the QCA7000 UART driver (Ethernet over UART) into the existing document. Signed-off-by: Stefan Wahren --- .../devicetree/bindings/net/qca,qca7000.txt| 32 ++ 1 file changed, 32 insertions(+) diff --git

[PATCH v8 net-next 17/17] net: qualcomm: add QCA7000 UART driver

This patch adds the Ethernet over UART driver for the Qualcomm QCA7000 HomePlug GreenPHY. Signed-off-by: Stefan Wahren Reviewed-by: Lino Sanfilippo --- drivers/net/ethernet/qualcomm/Kconfig | 16 + drivers/net/ethernet/qualcomm/Makefile

[PATCH v8 net-next 17/17] net: qualcomm: add QCA7000 UART driver

This patch adds the Ethernet over UART driver for the Qualcomm QCA7000 HomePlug GreenPHY. Signed-off-by: Stefan Wahren Reviewed-by: Lino Sanfilippo --- drivers/net/ethernet/qualcomm/Kconfig | 16 + drivers/net/ethernet/qualcomm/Makefile| 2 +

[PATCH v8 net-next 02/17] net: qca_framing: use u16 for frame offset

It doesn't make sense to use a signed variable for offset here, so fix it up. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_framing.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/qualcomm/qca_framing.h

[PATCH v8 net-next 14/17] dt-bindings: qca7000: rename binding

Before we can merge the QCA7000 UART binding the document needs to be renamed. Signed-off-by: Stefan Wahren --- .../devicetree/bindings/net/{qca-qca7000-spi.txt => qca,qca7000.txt} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename

[PATCH v8 net-next 02/17] net: qca_framing: use u16 for frame offset

It doesn't make sense to use a signed variable for offset here, so fix it up. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_framing.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/qualcomm/qca_framing.h

[PATCH v8 net-next 14/17] dt-bindings: qca7000: rename binding

Before we can merge the QCA7000 UART binding the document needs to be renamed. Signed-off-by: Stefan Wahren --- .../devicetree/bindings/net/{qca-qca7000-spi.txt => qca,qca7000.txt} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename

[PATCH v8 net-next 09/17] net: qca_spi: Clarify MODULE_DESCRIPTION

Since this driver is specific to the QCA7000, we should make the module description more precisely. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_spi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v8 net-next 09/17] net: qca_spi: Clarify MODULE_DESCRIPTION

Since this driver is specific to the QCA7000, we should make the module description more precisely. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_spi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/qualcomm/qca_spi.c

[PATCH v8 net-next 10/17] net: qualcomm: rename qca_framing.c to qca_7k_common.c

As preparation for the upcoming UART driver we need a module which contains common functions for both interfaces. The module qca_framing is a good candidate but renaming to qca_7k_common would make it clear. Signed-off-by: Stefan Wahren ---

[PATCH v8 net-next 10/17] net: qualcomm: rename qca_framing.c to qca_7k_common.c

As preparation for the upcoming UART driver we need a module which contains common functions for both interfaces. The module qca_framing is a good candidate but renaming to qca_7k_common would make it clear. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/Makefile

Re: [PATCH] ARM: imx_v6_v7_defconfig: Explicitly restore CONFIG_DEBUG_FS

On Fri, 2017-05-26 at 08:42 -0700, Paul E. McKenney wrote: > On Fri, May 26, 2017 at 02:26:06PM +0300, Leonard Crestez wrote: > > > > This option was removed by "make savedefconfig" in > > commit c5054a98bce4 ("ARM: imx_v6_v7_defconfig: Select SMSC_PHY") > > > > This happened because

[PATCH v8 net-next 03/17] net: qca_7k: Use BIT macro

Use the BIT macro for the CONFIG and INT register values. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.h | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_7k.h

Re: [PATCH] ARM: imx_v6_v7_defconfig: Explicitly restore CONFIG_DEBUG_FS

On Fri, 2017-05-26 at 08:42 -0700, Paul E. McKenney wrote: > On Fri, May 26, 2017 at 02:26:06PM +0300, Leonard Crestez wrote: > > > > This option was removed by "make savedefconfig" in > > commit c5054a98bce4 ("ARM: imx_v6_v7_defconfig: Select SMSC_PHY") > > > > This happened because

[PATCH v8 net-next 03/17] net: qca_7k: Use BIT macro

Use the BIT macro for the CONFIG and INT register values. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.h | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/net/ethernet/qualcomm/qca_7k.h b/drivers/net/ethernet/qualcomm/qca_7k.h

[PATCH v8 net-next 06/17] net: qualcomm: Improve readability of length defines

In order to avoid mixing things up, make the MTU and frame length defines easier to read. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_framing.c | 2 +- drivers/net/ethernet/qualcomm/qca_framing.h | 8

[PATCH v8 net-next 05/17] net: qualcomm: use net_device_ops instead of direct call

There is no need to export qcaspi_netdev_open and qcaspi_netdev_close because they are also accessible via the net_device_ops. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_debug.c | 5 +++-- drivers/net/ethernet/qualcomm/qca_spi.c | 4 ++--

[PATCH v8 net-next 05/17] net: qualcomm: use net_device_ops instead of direct call

There is no need to export qcaspi_netdev_open and qcaspi_netdev_close because they are also accessible via the net_device_ops. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_debug.c | 5 +++-- drivers/net/ethernet/qualcomm/qca_spi.c | 4 ++--

[PATCH v8 net-next 06/17] net: qualcomm: Improve readability of length defines

In order to avoid mixing things up, make the MTU and frame length defines easier to read. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_framing.c | 2 +- drivers/net/ethernet/qualcomm/qca_framing.h | 8 drivers/net/ethernet/qualcomm/qca_spi.c | 12

[PATCH v8 net-next 01/17] net: qualcomm: qca_7k: clean up header includes

Currently the includes doesn't reflect the dependencies. So fix this up by removing all unnecessary entries and add the necessary ones explicit. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 6 ++ 1 file changed, 2 insertions(+), 4

[PATCH v8 net-next 04/17] net: qca_spi: Use SET_NETDEV_DEV()

Use SET_NETDEV_DEV() in qca_spi to create the "/sys/class/net//device" symlink. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_spi.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/ethernet/qualcomm/qca_spi.c

[PATCH v8 net-next 01/17] net: qualcomm: qca_7k: clean up header includes

Currently the includes doesn't reflect the dependencies. So fix this up by removing all unnecessary entries and add the necessary ones explicit. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_7k.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

[PATCH v8 net-next 04/17] net: qca_spi: Use SET_NETDEV_DEV()

Use SET_NETDEV_DEV() in qca_spi to create the "/sys/class/net//device" symlink. Signed-off-by: Stefan Wahren --- drivers/net/ethernet/qualcomm/qca_spi.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/ethernet/qualcomm/qca_spi.c b/drivers/net/ethernet/qualcomm/qca_spi.c index

Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained

On Tue, May 23, 2017 at 11:23 PM, Thomas Gleixner wrote: > The AMD pinctrl driver uses a chained interrupt to demultiplex the GPIO > interrupts. Kevin Vandeventer reported, that his new AMD Ryzen locks up > hard on boot when the AMD pinctrl driver is initialized. The reason

Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained

On Tue, May 23, 2017 at 11:23 PM, Thomas Gleixner wrote: > The AMD pinctrl driver uses a chained interrupt to demultiplex the GPIO > interrupts. Kevin Vandeventer reported, that his new AMD Ryzen locks up > hard on boot when the AMD pinctrl driver is initialized. The reason is an > interrupt

Re: [PATCH] Docs: Insert missing space to separate link from text

Acked-by: SeongJae Park 2017-05-29 20:48 GMT+09:00 Sanjeev Gupta : > Korean translation, there should be a space terminating the link. > --- > Documentation/translations/ko_KR/howto.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH] Docs: Insert missing space to separate link from text

Acked-by: SeongJae Park 2017-05-29 20:48 GMT+09:00 Sanjeev Gupta : > Korean translation, there should be a space terminating the link. > --- > Documentation/translations/ko_KR/howto.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [v3 0/9] parallelized "struct page" zeroing

On Fri 26-05-17 12:45:55, Pasha Tatashin wrote: > Hi Michal, > > I have considered your proposals: > > 1. Making memset(0) unconditional inside __init_single_page() is not going > to work because it slows down SPARC, and ppc64. On SPARC even the BSTI > optimization that I have proposed earlier

Re: [v3 0/9] parallelized "struct page" zeroing

On Fri 26-05-17 12:45:55, Pasha Tatashin wrote: > Hi Michal, > > I have considered your proposals: > > 1. Making memset(0) unconditional inside __init_single_page() is not going > to work because it slows down SPARC, and ppc64. On SPARC even the BSTI > optimization that I have proposed earlier

Setting ->s_dev to a char device (Was: Re: [PATCH v2] ubifs: allow userspace to map mounts to volumes)

CC'ing VFS folks Am 29.05.2017 um 09:22 schrieb Rabin Vincent: > From: Rabin Vincent > > There currently appears to be no way for userspace to find out the > underlying volume number for a mounted ubifs file system, since ubifs > uses anonymous block devices. The volume name

Setting ->s_dev to a char device (Was: Re: [PATCH v2] ubifs: allow userspace to map mounts to volumes)

CC'ing VFS folks Am 29.05.2017 um 09:22 schrieb Rabin Vincent: > From: Rabin Vincent > > There currently appears to be no way for userspace to find out the > underlying volume number for a mounted ubifs file system, since ubifs > uses anonymous block devices. The volume name is present in >

[PATCH] Docs: Insert missing space to separate link from text

Korean translation, there should be a space terminating the link. --- Documentation/translations/ko_KR/howto.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/translations/ko_KR/howto.rst b/Documentation/translations/ko_KR/howto.rst index

[PATCH] Docs: Insert missing space to separate link from text

Korean translation, there should be a space terminating the link. --- Documentation/translations/ko_KR/howto.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/translations/ko_KR/howto.rst b/Documentation/translations/ko_KR/howto.rst index

Re: [PATCH 0/3] ipc subsystem refcounter conversions

ebied...@xmission.com (Eric W. Biederman) writes: > ebied...@xmission.com (Eric W. Biederman) writes: > >> Peter Zijlstra writes: >> >>> On Mon, May 29, 2017 at 04:11:13AM -0500, Eric W. Biederman wrote: >>> Kees I I have a concern: __must_check bool

Re: [PATCH 0/3] ipc subsystem refcounter conversions

ebied...@xmission.com (Eric W. Biederman) writes: > ebied...@xmission.com (Eric W. Biederman) writes: > >> Peter Zijlstra writes: >> >>> On Mon, May 29, 2017 at 04:11:13AM -0500, Eric W. Biederman wrote: >>> Kees I I have a concern: __must_check bool

Re: [PATCH v2]: perf/core: addressing 4x slowdown during per-process, profiling of STREAM benchmark on Intel Xeon Phi

On 29.05.2017 14:23, Peter Zijlstra wrote: On Mon, May 29, 2017 at 01:56:05PM +0300, Alexey Budankov wrote: On 29.05.2017 13:43, Peter Zijlstra wrote: Why can't the tree do both? Well, indeed, the tree provides such capability too. However switching to the full tree iteration in cases

Re: [PATCH v2]: perf/core: addressing 4x slowdown during per-process, profiling of STREAM benchmark on Intel Xeon Phi

On 29.05.2017 14:23, Peter Zijlstra wrote: On Mon, May 29, 2017 at 01:56:05PM +0300, Alexey Budankov wrote: On 29.05.2017 13:43, Peter Zijlstra wrote: Why can't the tree do both? Well, indeed, the tree provides such capability too. However switching to the full tree iteration in cases

Re: [PATCH] ubifs: Add freeze support

On Mon, May 29, 2017 at 1:17 PM, Richard Weinberger wrote: > Amir, > > Am 29.05.2017 um 12:04 schrieb Amir Goldstein: >>> Well, UBIFS is a bit different. >>> The UBIFS journal is not an add-on feature, you have to replay it in >>> any case. Otherwise you're facing corrupted data.

Re: [PATCH] ubifs: Add freeze support

On Mon, May 29, 2017 at 1:17 PM, Richard Weinberger wrote: > Amir, > > Am 29.05.2017 um 12:04 schrieb Amir Goldstein: >>> Well, UBIFS is a bit different. >>> The UBIFS journal is not an add-on feature, you have to replay it in >>> any case. Otherwise you're facing corrupted data. >> >> Yes, I

Re: KASAN vs. boot-time switching between 4- and 5-level paging

On 05/29/2017 02:19 PM, Dmitry Vyukov wrote: > On Mon, May 29, 2017 at 1:18 PM, Andrey Ryabinin > wrote: >> >> >> On 05/29/2017 01:02 PM, Dmitry Vyukov wrote: >>> On Sat, May 27, 2017 at 12:10 AM, Kirill A. Shutemov >>> wrote: On Thu, May 25,

Re: KASAN vs. boot-time switching between 4- and 5-level paging

On 05/29/2017 02:19 PM, Dmitry Vyukov wrote: > On Mon, May 29, 2017 at 1:18 PM, Andrey Ryabinin > wrote: >> >> >> On 05/29/2017 01:02 PM, Dmitry Vyukov wrote: >>> On Sat, May 27, 2017 at 12:10 AM, Kirill A. Shutemov >>> wrote: On Thu, May 25, 2017 at 11:33:33PM +0300, Kirill A. Shutemov

[PATCH 3/3] mm, memory_hotplug: move movable_node to the hotplug proper

From: Michal Hocko movable_node_is_enabled is defined in memblock proper while it is initialized from the memory hotplug proper. This is quite messy and it makes a dependency between the two so move movable_node along with the helper functions to memory_hotplug. To make it more

[PATCH 1/3] mm, memory_hotplug: drop artificial restriction on online/offline

From: Michal Hocko 74d42d8fe146 ("memory_hotplug: ensure every online node has NORMAL memory") has introduced a restriction that every numa node has to have at least some memory in !movable zones before a first movable memory can be onlined if !CONFIG_MOVABLE_NODE.

[PATCH 1/3] mm, memory_hotplug: drop artificial restriction on online/offline

From: Michal Hocko 74d42d8fe146 ("memory_hotplug: ensure every online node has NORMAL memory") has introduced a restriction that every numa node has to have at least some memory in !movable zones before a first movable memory can be onlined if !CONFIG_MOVABLE_NODE. Likewise_offline_normal checks

[PATCH 3/3] mm, memory_hotplug: move movable_node to the hotplug proper

From: Michal Hocko movable_node_is_enabled is defined in memblock proper while it is initialized from the memory hotplug proper. This is quite messy and it makes a dependency between the two so move movable_node along with the helper functions to memory_hotplug. To make it more entertaining the

[PATCH 0/2] remove CONFIG_MOVABLE_NODE

Hi, this has been previously posted as an RFC [1]. As it hasn't met any disagreement, I have integrated the feedback and resending it without RFC and hope for a soon merging (ideally along with other memory hotplug pile). I am continuing to cleanup the memory hotplug code and CONFIG_MOVABLE_NODE

[PATCH 2/3] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE

From: Michal Hocko 20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated node") has introduced CONFIG_MOVABLE_NODE without a good explanation on why it is actually useful. It makes a lot of sense to make movable node semantic opt in but we already have that because

[PATCH 0/2] remove CONFIG_MOVABLE_NODE

Hi, this has been previously posted as an RFC [1]. As it hasn't met any disagreement, I have integrated the feedback and resending it without RFC and hope for a soon merging (ideally along with other memory hotplug pile). I am continuing to cleanup the memory hotplug code and CONFIG_MOVABLE_NODE

[PATCH 2/3] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE

From: Michal Hocko 20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated node") has introduced CONFIG_MOVABLE_NODE without a good explanation on why it is actually useful. It makes a lot of sense to make movable node semantic opt in but we already have that because the feature has

Re: [PATCH 0/3] ipc subsystem refcounter conversions

ebied...@xmission.com (Eric W. Biederman) writes: > Peter Zijlstra writes: > >> On Mon, May 29, 2017 at 04:11:13AM -0500, Eric W. Biederman wrote: >> >>> Kees I I have a concern: >>> >>> __must_check bool refcount_add_not_zero(unsigned int i, refcount_t *r) >>> { >>>

Re: [PATCH 0/3] ipc subsystem refcounter conversions

ebied...@xmission.com (Eric W. Biederman) writes: > Peter Zijlstra writes: > >> On Mon, May 29, 2017 at 04:11:13AM -0500, Eric W. Biederman wrote: >> >>> Kees I I have a concern: >>> >>> __must_check bool refcount_add_not_zero(unsigned int i, refcount_t *r) >>> { >>> unsigned int new,

Re: [PATCH 3/3] gpio: adp5588: move header file out of I2C realm

On Sun, May 21, 2017 at 11:57 PM, Wolfram Sang wrote: > include/linux/i2c is not for client devices. Move the header file to a > more appropriate location. > > Signed-off-by: Wolfram Sang > --- > > This driver could also go via the input-tree or my tree.

Re: [PATCH 3/3] gpio: adp5588: move header file out of I2C realm

On Sun, May 21, 2017 at 11:57 PM, Wolfram Sang wrote: > include/linux/i2c is not for client devices. Move the header file to a > more appropriate location. > > Signed-off-by: Wolfram Sang > --- > > This driver could also go via the input-tree or my tree. I don't really care > and just picked

Re: [PATCH 3/3] gpio: ml-ioh: check the return value of irq_alloc_generic_chip()

On Thu, May 25, 2017 at 10:37 AM, Bartosz Golaszewski wrote: > This function can fail, so check the return value before dereferencing > the returned pointer. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH 3/3] gpio: ml-ioh: check the return value of irq_alloc_generic_chip()

On Thu, May 25, 2017 at 10:37 AM, Bartosz Golaszewski wrote: > This function can fail, so check the return value before dereferencing > the returned pointer. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH 2/3] gpio: sta2x11: check the return value of irq_alloc_generic_chip()

On Thu, May 25, 2017 at 10:37 AM, Bartosz Golaszewski wrote: > This function can fail, so check the return value before dereferencing > the returned pointer. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH 2/3] gpio: sta2x11: check the return value of irq_alloc_generic_chip()

On Thu, May 25, 2017 at 10:37 AM, Bartosz Golaszewski wrote: > This function can fail, so check the return value before dereferencing > the returned pointer. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

[PATCH] acpi: configfs: Unload SSDT on configfs entry removal

Enhance acpi_load_table to also return the table index. Use that index to unload the table again when the corresponding directory in configfs gets removed. This allows to change SSDTs without rebooting the system. It also allows to destroy devices again that a dynamically loaded SSDT created.

[PATCH] acpi: configfs: Unload SSDT on configfs entry removal

Enhance acpi_load_table to also return the table index. Use that index to unload the table again when the corresponding directory in configfs gets removed. This allows to change SSDTs without rebooting the system. It also allows to destroy devices again that a dynamically loaded SSDT created.

Re: [PATCH 1/3] gpio: pch: check the return value of irq_alloc_generic_chip()

On Thu, May 25, 2017 at 10:37 AM, Bartosz Golaszewski wrote: > This function can fail, so check the return value before dereferencing > the returned pointer. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH 1/3] gpio: pch: check the return value of irq_alloc_generic_chip()

On Thu, May 25, 2017 at 10:37 AM, Bartosz Golaszewski wrote: > This function can fail, so check the return value before dereferencing > the returned pointer. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH 05/10] gpio: mockup: improve the debugfs input sanitization

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > We're currently only checking the first character of the input to the > debugfs event files, so a string like '0sdfdsf' is valid and indicates > a falling edge event. > > Be more strict and only allow '0', '1', '0\n' &

Re: [PATCH 05/10] gpio: mockup: improve the debugfs input sanitization

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > We're currently only checking the first character of the input to the > debugfs event files, so a string like '0sdfdsf' is valid and indicates > a falling edge event. > > Be more strict and only allow '0', '1', '0\n' & '1\n'. > >

Re: [PATCH 04/10] gpio: mockup: support irqmask and irqunmask

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > Even though this is a testing module, be nice and actually implement > these functions. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH 04/10] gpio: mockup: support irqmask and irqunmask

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > Even though this is a testing module, be nice and actually implement > these functions. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH 03/10] gpio: mockup: be quiet unless something goes wrong

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > When inserting and removing the module repeatedly (e.g. when running > the libgpiod test-suite) the kernel log gets clobbered with messages > reporting successful creation of dummy gpiochips. > > Remove this message

Re: [PATCH 03/10] gpio: mockup: be quiet unless something goes wrong

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > When inserting and removing the module repeatedly (e.g. when running > the libgpiod test-suite) the kernel log gets clobbered with messages > reporting successful creation of dummy gpiochips. > > Remove this message and only emit

Re: [PATCH 02/10] gpio: mockup: add prefixes to the direction enum

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > All internal symbols except for the direction enum follow the same > convention and use the gpio_mockup prefix. Add the prefix to the > DIR_IN and DIR_OUT definitions as well for consistency across the > file. > >

Re: [PATCH 02/10] gpio: mockup: add prefixes to the direction enum

On Thu, May 25, 2017 at 10:33 AM, Bartosz Golaszewski wrote: > All internal symbols except for the direction enum follow the same > convention and use the gpio_mockup prefix. Add the prefix to the > DIR_IN and DIR_OUT definitions as well for consistency across the > file. > > Signed-off-by:

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