[PATCH net 0/3] Fix integration of eee-broken-modes

The purpose of this series is to fix the integration of the ethernet phy property "eee-broken-modes" [0] The v3 of this series has been merged, missing a fix (error reported by kbuild robot) available in the v4 [1] More importantly, Florian opposed adding a DT property mapping a device register

[PATCH net 0/3] Fix integration of eee-broken-modes

The purpose of this series is to fix the integration of the ethernet phy property "eee-broken-modes" [0] The v3 of this series has been merged, missing a fix (error reported by kbuild robot) available in the v4 [1] More importantly, Florian opposed adding a DT property mapping a device register

Re: [PATCH] stmmac: fix memory barriers

Tested-by: Niklas Cassel On 12/18/2016 09:38 PM, Pavel Machek wrote: > Fix up memory barriers in stmmac driver. They are meant to protect > against DMA engine, so smp_ variants are certainly wrong, and dma_ > variants are preferable. > > Signed-off-by: Pavel Machek

Re: [PATCH] stmmac: fix memory barriers

Tested-by: Niklas Cassel On 12/18/2016 09:38 PM, Pavel Machek wrote: > Fix up memory barriers in stmmac driver. They are meant to protect > against DMA engine, so smp_ variants are certainly wrong, and dma_ > variants are preferable. > > Signed-off-by: Pavel Machek > > diff --git

[PATCH v3 0/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

Hi all, this series of patches is based on the git://github.com/spi-nor/linux.git tree. It has been extracted from the SFDP series and is resent as a standalone series. This series fixes compatibility issue between Linux and many bootloaders when using SPI flash with size greater than 128Mib.

[PATCH v3 0/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

Hi all, this series of patches is based on the git://github.com/spi-nor/linux.git tree. It has been extracted from the SFDP series and is resent as a standalone series. This series fixes compatibility issue between Linux and many bootloaders when using SPI flash with size greater than 128Mib.

[PATCH net 3/3] dt: bindings: net: use boolean dt properties for eee broken modes

The patches regarding eee-broken-modes was merged before all people involved could find an agreement on the best way to move forward. While we agreed on having a DT property to mark particular modes as broken, the value used for eee-broken-modes mapped the phy register in very direct way. Because

[PATCH net 1/3] net: phy: fix sign type error in genphy_config_eee_advert

In genphy_config_eee_advert, the return value of phy_read_mmd_indirect is checked to know if the register could be accessed but the result is assigned to a 'u32'. Changing to 'int' to correctly get errors from phy_read_mmd_indirect. Fixes: d853d145ea3e ("net: phy: add an option to disable EEE

[PATCH v3 2/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

This patch provides an alternative mean to support memory above 16MiB (128Mib) by replacing 3byte address op codes by their associated 4byte address versions. Using the dedicated 4byte address op codes doesn't change the internal state of the SPI NOR memory as opposed to using other means such as

[PATCH net 3/3] dt: bindings: net: use boolean dt properties for eee broken modes

The patches regarding eee-broken-modes was merged before all people involved could find an agreement on the best way to move forward. While we agreed on having a DT property to mark particular modes as broken, the value used for eee-broken-modes mapped the phy register in very direct way. Because

[PATCH net 1/3] net: phy: fix sign type error in genphy_config_eee_advert

In genphy_config_eee_advert, the return value of phy_read_mmd_indirect is checked to know if the register could be accessed but the result is assigned to a 'u32'. Changing to 'int' to correctly get errors from phy_read_mmd_indirect. Fixes: d853d145ea3e ("net: phy: add an option to disable EEE

[PATCH v3 2/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

This patch provides an alternative mean to support memory above 16MiB (128Mib) by replacing 3byte address op codes by their associated 4byte address versions. Using the dedicated 4byte address op codes doesn't change the internal state of the SPI NOR memory as opposed to using other means such as

[PATCH v3 1/2] mtd: spi-nor: rename SPINOR_OP_* macros of the 4-byte address op codes

This patch renames the SPINOR_OP_* macros of the 4-byte address instruction set so the new names all share a common pattern: the 4-byte address name is built from the 3-byte address name appending the "_4B" suffix. The patch also introduces new op codes to support other SPI protocols such as SPI

[PATCH net 2/3] net: phy: use boolean dt properties for eee broken modes

The patches regarding eee-broken-modes was merged before all people involved could find an agreement on the best way to move forward. While we agreed on having a DT property to mark particular modes as broken, the value used for eee-broken-modes mapped the phy register in very direct way. Because

[PATCH v3 1/2] mtd: spi-nor: rename SPINOR_OP_* macros of the 4-byte address op codes

This patch renames the SPINOR_OP_* macros of the 4-byte address instruction set so the new names all share a common pattern: the 4-byte address name is built from the 3-byte address name appending the "_4B" suffix. The patch also introduces new op codes to support other SPI protocols such as SPI

[PATCH net 2/3] net: phy: use boolean dt properties for eee broken modes

The patches regarding eee-broken-modes was merged before all people involved could find an agreement on the best way to move forward. While we agreed on having a DT property to mark particular modes as broken, the value used for eee-broken-modes mapped the phy register in very direct way. Because

[PATCH] trace/trace_stat: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- kernel/trace/trace_stat.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/trace/trace_stat.c b/kernel/trace/trace_stat.c

[PATCH] PM / Hibernate: use rb_entry instead of container_of

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- kernel/power/swap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/power/swap.c b/kernel/power/swap.c index 32e0c23..f80fd33

[PATCH] trace/trace_stat: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- kernel/trace/trace_stat.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/trace/trace_stat.c b/kernel/trace/trace_stat.c index 413ff10..0765150

[PATCH] PM / Hibernate: use rb_entry instead of container_of

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- kernel/power/swap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/power/swap.c b/kernel/power/swap.c index 32e0c23..f80fd33 100644 ---

Re: [PATCH] genwqe: drop .link_reset()

[+cc linux-pci, Linas] On Mon, Dec 19, 2016 at 03:23:56PM +0800, Cao jin wrote: > In AER recovery, pci_error_handlers.link_reset() is never called, > drop it now. I think it's true that .link_reset() is never called. If that's the case, why not remove it completely, i.e., remove it from struct

Re: [PATCH] genwqe: drop .link_reset()

[+cc linux-pci, Linas] On Mon, Dec 19, 2016 at 03:23:56PM +0800, Cao jin wrote: > In AER recovery, pci_error_handlers.link_reset() is never called, > drop it now. I think it's true that .link_reset() is never called. If that's the case, why not remove it completely, i.e., remove it from struct

Re: [RFC PATCH v3 0/6] KVM: x86: avoid redundant REQ_EVENT

On 19/12/2016 14:05, Denis Plotnikov wrote: >> > This new patch-set does avoid unnecessary interrupt re-injections - > checked. > > The test (MS Windows, sending messages between multiple windows using > windows-specific interface), > which showed performance growth with "[PATCH v2] KVM: x86:

Re: [RFC PATCH v3 0/6] KVM: x86: avoid redundant REQ_EVENT

On 19/12/2016 14:05, Denis Plotnikov wrote: >> > This new patch-set does avoid unnecessary interrupt re-injections - > checked. > > The test (MS Windows, sending messages between multiple windows using > windows-specific interface), > which showed performance growth with "[PATCH v2] KVM: x86:

Re: [PATCH 1/2] jump_labels: API for flushing deferred jump label updates

On Fri, Dec 16, 2016 at 02:30:35PM -0800, David Matlack wrote: > Modules that use static_key_deferred need a way to synchronize with > any delayed work that is still pending when the module is unloaded. > Introduce static_key_deferred_flush() which flushes any pending > jump label updates. Makes

Re: [PATCH 1/2] jump_labels: API for flushing deferred jump label updates

On Fri, Dec 16, 2016 at 02:30:35PM -0800, David Matlack wrote: > Modules that use static_key_deferred need a way to synchronize with > any delayed work that is still pending when the module is unloaded. > Introduce static_key_deferred_flush() which flushes any pending > jump label updates. Makes

Re: [PATCH v4 3/4] KVM: x86: make interrupt delivery fast and slow path behave the same

Am 16.12.2016 um 18:07 schrieb Radim Krčmář: 2016-12-16 17:53+0100, Paolo Bonzini: On 16/12/2016 17:41, David Hildenbrand wrote: Just to verify: The GET_APIC_DEST_FIELD(mda) == APIC_BROADCAST is still correct in kvm_apic_broadcast() ? No, it seems wrong. Definitely, sending v4 of this

Re: [PATCH v4 3/4] KVM: x86: make interrupt delivery fast and slow path behave the same

Am 16.12.2016 um 18:07 schrieb Radim Krčmář: 2016-12-16 17:53+0100, Paolo Bonzini: On 16/12/2016 17:41, David Hildenbrand wrote: Just to verify: The GET_APIC_DEST_FIELD(mda) == APIC_BROADCAST is still correct in kvm_apic_broadcast() ? No, it seems wrong. Definitely, sending v4 of this

[PATCH] ovl: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- fs/overlayfs/readdir.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/overlayfs/readdir.c b/fs/overlayfs/readdir.c index

[PATCH] ovl: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- fs/overlayfs/readdir.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/overlayfs/readdir.c b/fs/overlayfs/readdir.c index f241b4e..401bdc4 100644 ---

[PATCH 2/9] ARM: dts: omap3: Add an empty chosen node to top level DTSI

Commit 008a2ebcd677 ("ARM: dts: omap3: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 2/9] ARM: dts: omap3: Add an empty chosen node to top level DTSI

Commit 008a2ebcd677 ("ARM: dts: omap3: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH] drm/i915/debugfs: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- drivers/gpu/drm/i915/i915_debugfs.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_debugfs.c

[PATCH] drm/i915/debugfs: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- drivers/gpu/drm/i915/i915_debugfs.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_debugfs.c

[PATCH] btrfs: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- fs/btrfs/ctree.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c index a426dc8..146b2dc

[PATCH] btrfs: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- fs/btrfs/ctree.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c index a426dc8..146b2dc 100644 ---

RE: [PATCH] perf diff: bug fix, donot overwrite valid build id

Hi Arnaldo, Ping Are you OK with the fix? Thanks, Kan > > From: Kan Liang > > Fixes a perf diff regression issue which was introduced by commit > 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files > based on a build ID") > > The binary name could be

RE: [PATCH] perf diff: bug fix, donot overwrite valid build id

Hi Arnaldo, Ping Are you OK with the fix? Thanks, Kan > > From: Kan Liang > > Fixes a perf diff regression issue which was introduced by commit > 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files > based on a build ID") > > The binary name could be same when perf diff

[PATCH 9/9] ARM: dts: dra7: Add an empty chosen node to top level DTSI

Commit 55871eb6e2cc ("ARM: dts: dra7: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies on

[PATCH 9/9] ARM: dts: dra7: Add an empty chosen node to top level DTSI

Commit 55871eb6e2cc ("ARM: dts: dra7: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies on

[PATCH 8/9] ARM: dts: dm816x: Add an empty chosen node to top level DTSI

Commit 06bfb9c19957 ("ARM: dts: dm816x: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 8/9] ARM: dts: dm816x: Add an empty chosen node to top level DTSI

Commit 06bfb9c19957 ("ARM: dts: dm816x: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 7/9] ARM: dts: dm814x: Add an empty chosen node to top level DTSI

Commit 76155b378c59 ("ARM: dts: dm814x: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 7/9] ARM: dts: dm814x: Add an empty chosen node to top level DTSI

Commit 76155b378c59 ("ARM: dts: dm814x: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[RFC PATCH] usb: USB Type-C connector class

The purpose of USB Type-C connector class is to provide unified interface for the user space to get the status and basic information about USB Type-C connectors on a system, control over data role swapping, and when the port supports USB Power Delivery, also control over power role swapping and

[RFC PATCH] usb: USB Type-C connector class

The purpose of USB Type-C connector class is to provide unified interface for the user space to get the status and basic information about USB Type-C connectors on a system, control over data role swapping, and when the port supports USB Power Delivery, also control over power role swapping and

[PATCH 6/9] ARM: dts: am4372: Add an empty chosen node to top level DTSI

Commit 75813028bbd7 ("ARM: dts: am4372: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 6/9] ARM: dts: am4372: Add an empty chosen node to top level DTSI

Commit 75813028bbd7 ("ARM: dts: am4372: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 5/9] ARM: dts: am33xx: Add an empty chosen node to top level DTSI

Commit f8bf01611c99 ("ARM: dts: am33xx: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH] iommu/iova: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- drivers/iommu/iova.c | 23 +++ 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/drivers/iommu/iova.c

[PATCH 5/9] ARM: dts: am33xx: Add an empty chosen node to top level DTSI

Commit f8bf01611c99 ("ARM: dts: am33xx: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH] iommu/iova: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- drivers/iommu/iova.c | 23 +++ 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c index

[PATCH 1/9] ARM: dts: omap2: Add an empty chosen node to top level DTSI

Commit d1f3156fc8c7 ("ARM: dts: omap2: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 4/9] ARM: dts: omap5: Add an empty chosen node to top level DTSI

Commit 76a8548ea987 ("ARM: dts: omap5: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 3/9] ARM: dts: omap4: Add an empty chosen node to top level DTSI

Commit da6269e7e3dd ("ARM: dts: omap4: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 1/9] ARM: dts: omap2: Add an empty chosen node to top level DTSI

Commit d1f3156fc8c7 ("ARM: dts: omap2: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 4/9] ARM: dts: omap5: Add an empty chosen node to top level DTSI

Commit 76a8548ea987 ("ARM: dts: omap5: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 3/9] ARM: dts: omap4: Add an empty chosen node to top level DTSI

Commit da6269e7e3dd ("ARM: dts: omap4: Remove skeleton.dtsi usage") removed the skeleton.dtsi usage since we want to get rid of it. But this can cause issues when booting a kernel with a boot-loader that doesn't create a chosen node if this isn't present in the DTB since the decompressor relies

[PATCH 0/9] ARM: omap: Add empty chosen node in SoCs top level DTSI

Hello Tony, As discussed in [0], there's a regression when booting a kernel with a DTB that doesn't have a pre-existing chosen node. This is usually not an issue for most boards since u-boot creates an empty chosen node if isn't present in the DTB. But it can be an issue for others bootloaders

[PATCH 0/9] ARM: omap: Add empty chosen node in SoCs top level DTSI

Hello Tony, As discussed in [0], there's a regression when booting a kernel with a DTB that doesn't have a pre-existing chosen node. This is usually not an issue for most boards since u-boot creates an empty chosen node if isn't present in the DTB. But it can be an issue for others bootloaders

[PATCH v2] drm: tilcdc: simplify the recovery from sync lost error on rev1

Revision 2 of LCDC suffers from an issue where a SYNC_LOST error caused by limited memory bandwidth may leave the picture shifted a couple pixels to the right. This issue has not been observed on revision 1, while the recovery mechanism introduces a different issue, where the END_OF_FRAME

[PATCH v2] drm: tilcdc: simplify the recovery from sync lost error on rev1

Revision 2 of LCDC suffers from an issue where a SYNC_LOST error caused by limited memory bandwidth may leave the picture shifted a couple pixels to the right. This issue has not been observed on revision 1, while the recovery mechanism introduces a different issue, where the END_OF_FRAME

Re: [PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option

On Mon, Dec 19, 2016 at 02:57:00PM +0100, Geert Uytterhoeven wrote: > Hi Konrad, > > On Mon, Dec 19, 2016 at 2:38 PM, Konrad Rzeszutek Wilk > wrote: > > On Fri, Dec 16, 2016 at 02:28:42PM +0100, Geert Uytterhoeven wrote: > >> On architectures like arm64, swiotlb is tied

Re: [PATCH v2 3/3] swiotlb: Add swiotlb=noforce debug option

On Mon, Dec 19, 2016 at 02:57:00PM +0100, Geert Uytterhoeven wrote: > Hi Konrad, > > On Mon, Dec 19, 2016 at 2:38 PM, Konrad Rzeszutek Wilk > wrote: > > On Fri, Dec 16, 2016 at 02:28:42PM +0100, Geert Uytterhoeven wrote: > >> On architectures like arm64, swiotlb is tied intimately to the core >

Re: [PATCH v2] ARM: dts: sun8i: add opp-v2 table for A33

On 19/12/2016 15:06, Icenowy Zheng wrote: > > > 19.12.2016, 16:54, "Chen-Yu Tsai" : >> On Mon, Dec 19, 2016 at 4:46 PM, Maxime Ripard >> wrote: >>> On Fri, Dec 16, 2016 at 02:27:54AM +0800, Icenowy Zheng wrote: An operating point table is

Re: [PATCH] livepatch: fixup klp-convert tool integration

On Sat, 17 Dec 2016, Konstantin Khlebnikov wrote: > I've found some minor problems, this patch fixes: > > * save cmd_ld_ko_o into .module.cmd, if_changed_rule doesn't do that > * fix bashisms for debian where /bin/sh is a symlink to /bin/dash > * rename rule_link_module to rule_ld_ko_o,

Re: [PATCH] livepatch: fixup klp-convert tool integration

On Sat, 17 Dec 2016, Konstantin Khlebnikov wrote: > I've found some minor problems, this patch fixes: > > * save cmd_ld_ko_o into .module.cmd, if_changed_rule doesn't do that > * fix bashisms for debian where /bin/sh is a symlink to /bin/dash > * rename rule_link_module to rule_ld_ko_o,

Re: [PATCH v2] ARM: dts: sun8i: add opp-v2 table for A33

On 19/12/2016 15:06, Icenowy Zheng wrote: > > > 19.12.2016, 16:54, "Chen-Yu Tsai" : >> On Mon, Dec 19, 2016 at 4:46 PM, Maxime Ripard >> wrote: >>> On Fri, Dec 16, 2016 at 02:27:54AM +0800, Icenowy Zheng wrote: An operating point table is needed for the cpu frequency adjusting to

Re: task isolation discussion at Linux Plumbers

On Sat, Nov 05, 2016 at 12:04:45AM -0400, Chris Metcalf wrote: > A bunch of people got together this week at the Linux Plumbers > Conference to discuss nohz_full, task isolation, and related stuff. > (Thanks to Thomas for getting everyone gathered at one place and time!) Which reminds me... One

Re: task isolation discussion at Linux Plumbers

On Sat, Nov 05, 2016 at 12:04:45AM -0400, Chris Metcalf wrote: > A bunch of people got together this week at the Linux Plumbers > Conference to discuss nohz_full, task isolation, and related stuff. > (Thanks to Thomas for getting everyone gathered at one place and time!) Which reminds me... One

[PATCH] regmap: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- drivers/base/regmap/regcache-rbtree.c | 7 +++ drivers/base/regmap/regmap.c | 4 ++-- 2 files changed, 5 insertions(+), 6 deletions(-)

[PATCH] regmap: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- drivers/base/regmap/regcache-rbtree.c | 7 +++ drivers/base/regmap/regmap.c | 4 ++-- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git

Re: [PATCH v7 08/11] x86, kvm/x86.c: support vcpu preempted check

On 19/12/2016 14:56, Pan Xinhui wrote: > hi, Andrea > thanks for your reply. :) > > 在 2016/12/19 19:42, Andrea Arcangeli 写道: >> Hello, >> >> On Wed, Nov 02, 2016 at 05:08:35AM -0400, Pan Xinhui wrote: >>> Support the vcpu_is_preempted() functionality under KVM. This will >>> enhance lock

[PATCH 2/2] nsfs: Add an ioctl() to return creator UID of a userns

# Some open questions about this patch below. # One of the rules regarding capabilities is: A process that resides in the parent of the user namespace and whose effective user ID matches the owner of the namespace has all capabilities in the namespace. Therefore, in order to write

Re: [PATCH v7 08/11] x86, kvm/x86.c: support vcpu preempted check

On 19/12/2016 14:56, Pan Xinhui wrote: > hi, Andrea > thanks for your reply. :) > > 在 2016/12/19 19:42, Andrea Arcangeli 写道: >> Hello, >> >> On Wed, Nov 02, 2016 at 05:08:35AM -0400, Pan Xinhui wrote: >>> Support the vcpu_is_preempted() functionality under KVM. This will >>> enhance lock

[PATCH 2/2] nsfs: Add an ioctl() to return creator UID of a userns

# Some open questions about this patch below. # One of the rules regarding capabilities is: A process that resides in the parent of the user namespace and whose effective user ID matches the owner of the namespace has all capabilities in the namespace. Therefore, in order to write

Re: [PATCH 4/4] oom-reaper: use madvise_dontneed() instead of unmap_page_range()

On Fri 16-12-16 17:15:56, Kirill A. Shutemov wrote: > Logic on whether we can reap pages from the VMA should match what we > have in madvise_dontneed(). In particular, we should skip, VM_PFNMAP > VMAs, but we don't now. > > Let's just call madvise_dontneed() from __oom_reap_task_mm(), so we >

[PATCH 1/2] nsfs: Add an ioctl() to return the namespace type

Linux 4.9 added two ioctl() operations that can be used to discover: * the parental relationships for hierarchical namespaces (user and PID) [NS_GET_PARENT] * the user namespaces that owns a specified non-user-namespace [NS_GET_USERNS] For no good reason that I can glean, NS_GET_USERNS was

Re: [PATCH 4/4] oom-reaper: use madvise_dontneed() instead of unmap_page_range()

On Fri 16-12-16 17:15:56, Kirill A. Shutemov wrote: > Logic on whether we can reap pages from the VMA should match what we > have in madvise_dontneed(). In particular, we should skip, VM_PFNMAP > VMAs, but we don't now. > > Let's just call madvise_dontneed() from __oom_reap_task_mm(), so we >

[PATCH 1/2] nsfs: Add an ioctl() to return the namespace type

Linux 4.9 added two ioctl() operations that can be used to discover: * the parental relationships for hierarchical namespaces (user and PID) [NS_GET_PARENT] * the user namespaces that owns a specified non-user-namespace [NS_GET_USERNS] For no good reason that I can glean, NS_GET_USERNS was

[PATCH 0/2] Add further ioctl() operations for namespace discovery

Eric, The code proposed in this patch series is pretty small. Is there any chance we could make the 4.10 merge window, if the changes seem acceptable to you? I would like to write code that can answer the question: "what capabilities does process X have in namespace Y"? (where Y is defined by a

[PATCH 0/2] Add further ioctl() operations for namespace discovery

Eric, The code proposed in this patch series is pretty small. Is there any chance we could make the 4.10 merge window, if the changes seem acceptable to you? I would like to write code that can answer the question: "what capabilities does process X have in namespace Y"? (where Y is defined by a

[PATCH] staging: comedi: dyna_pci10xx: fixed check patch warnings about memory barrier comments

Added comments before memory barrier Signed-off-by: Devendra Sharma --- drivers/staging/comedi/drivers/dyna_pci10xx.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/staging/comedi/drivers/dyna_pci10xx.c

[PATCH] staging: comedi: dyna_pci10xx: fixed check patch warnings about memory barrier comments

Added comments before memory barrier Signed-off-by: Devendra Sharma --- drivers/staging/comedi/drivers/dyna_pci10xx.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/staging/comedi/drivers/dyna_pci10xx.c b/drivers/staging/comedi/drivers/dyna_pci10xx.c index c9eb26f..c3b5236

Re: [PATCH 3/4] mm: drop unused argument of zap_page_range()

On Fri 16-12-16 17:15:55, Kirill A. Shutemov wrote: > There's no users of zap_page_range() who wants non-NULL 'details'. > Let's drop it. > > Signed-off-by: Kirill A. Shutemov kbuild robot has noticed that you should remove doc part as well * @details: details

[PATCH] x86/mm/pat: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- arch/x86/mm/pat_rbtree.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/x86/mm/pat_rbtree.c

Re: [PATCH 3/4] mm: drop unused argument of zap_page_range()

On Fri 16-12-16 17:15:55, Kirill A. Shutemov wrote: > There's no users of zap_page_range() who wants non-NULL 'details'. > Let's drop it. > > Signed-off-by: Kirill A. Shutemov kbuild robot has noticed that you should remove doc part as well * @details: details of shared cache invalidation

[PATCH] x86/mm/pat: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- arch/x86/mm/pat_rbtree.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/x86/mm/pat_rbtree.c b/arch/x86/mm/pat_rbtree.c index

Re: [PATCH] ARM: dts: sun8i-q8-common: enable bluetooth on SDIO Wi-Fi

On Mon, Dec 19, 2016 at 10:08 PM, Icenowy Zheng wrote: > > > 19.12.2016, 18:09, "Maxime Ripard" : >> On Fri, Dec 16, 2016 at 10:40:00PM +0800, Icenowy Zheng wrote: >>> >> > > _pio { >>> >> > > wifi_pwrseq_pin_q8: wifi_pwrseq_pin@0 { >>>

Re: [PATCH] ARM: dts: sun8i-q8-common: enable bluetooth on SDIO Wi-Fi

On Mon, Dec 19, 2016 at 10:08 PM, Icenowy Zheng wrote: > > > 19.12.2016, 18:09, "Maxime Ripard" : >> On Fri, Dec 16, 2016 at 10:40:00PM +0800, Icenowy Zheng wrote: >>> >> > > _pio { >>> >> > > wifi_pwrseq_pin_q8: wifi_pwrseq_pin@0 { >>> >> > > - pins = "PL6", "PL7", "PL11"; >>> >> > > +

Re: [PATCH 2/4] mm: drop zap_details::check_swap_entries

On Fri 16-12-16 17:15:54, Kirill A. Shutemov wrote: > detail == NULL would give the same functionality as > .check_swap_entries==true. Yes, now that check_swap_entries is the only used flag from there we can safely rely on detail == NULL check. > Signed-off-by: Kirill A. Shutemov

Re: [PATCH 2/4] mm: drop zap_details::check_swap_entries

On Fri 16-12-16 17:15:54, Kirill A. Shutemov wrote: > detail == NULL would give the same functionality as > .check_swap_entries==true. Yes, now that check_swap_entries is the only used flag from there we can safely rely on detail == NULL check. > Signed-off-by: Kirill A. Shutemov Acked-by:

[PATCH v3 5/5] MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK

Since do_IRQ is now invoked on a separate IRQ stack, we select HAVE_IRQ_EXIT_ON_IRQ_STACK so that softirq's may be invoked directly from irq_exit(), rather than requiring do_softirq_own_stack. Signed-off-by: Matt Redfearn --- Changes in v3: None Changes in v2: None

[PATCH v3 5/5] MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK

Since do_IRQ is now invoked on a separate IRQ stack, we select HAVE_IRQ_EXIT_ON_IRQ_STACK so that softirq's may be invoked directly from irq_exit(), rather than requiring do_softirq_own_stack. Signed-off-by: Matt Redfearn --- Changes in v3: None Changes in v2: None arch/mips/Kconfig | 1 + 1

Re: [PATCH 2/2] KVM: x86: flush pending lapic jump label updates on module unload

2016-12-16 14:30-0800, David Matlack: > KVM's lapic emulation uses static_key_deferred (apic_{hw,sw}_disabled). > These are implemented with delayed_work structs which can still be > pending when the KVM module is unloaded. We've seen this cause kernel > panics when the kvm_intel module is quickly

Re: [PATCH 2/2] KVM: x86: flush pending lapic jump label updates on module unload

2016-12-16 14:30-0800, David Matlack: > KVM's lapic emulation uses static_key_deferred (apic_{hw,sw}_disabled). > These are implemented with delayed_work structs which can still be > pending when the KVM module is unloaded. We've seen this cause kernel > panics when the kvm_intel module is quickly

Re: [PATCH v2] ARM: dts: sun8i: add opp-v2 table for A33

Hi, On 19/12/2016 15:06, Icenowy Zheng wrote: > > After proper testing of A23 ccu, the operating points can also apply to A23. > (According to A23 devices' fex) > I disagree. I've looked into using the same operating points for A23 and A33 for CPUfreq and I came to the conclusion that not all

Re: [PATCH v2] ARM: dts: sun8i: add opp-v2 table for A33

Hi, On 19/12/2016 15:06, Icenowy Zheng wrote: > > After proper testing of A23 ccu, the operating points can also apply to A23. > (According to A23 devices' fex) > I disagree. I've looked into using the same operating points for A23 and A33 for CPUfreq and I came to the conclusion that not all

[PATCH v3 2/5] MIPS: Stack unwinding while on IRQ stack

Within unwind stack, check if the stack pointer being unwound is within the CPU's irq_stack and if so use that page rather than the task's stack page. Signed-off-by: Matt Redfearn --- Changes in v3: None Changes in v2: None arch/mips/kernel/process.c | 15

[PATCH v3 3/5] MIPS: Only change $28 to thread_info if coming from user mode

The SAVE_SOME macro is used to save the execution context on all exceptions. If an exception occurs while executing user code, the stack is switched to the kernel's stack for the current task, and register $28 is switched to point to the current_thread_info, which is at the bottom of the stack

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