[tip:perf/core] perf annotate: Fix missing number of samples for source_line_samples

Commit-ID: 99094a5e941fe88d95cbd594e6a41bee24003ecb Gitweb: http://git.kernel.org/tip/99094a5e941fe88d95cbd594e6a41bee24003ecb Author: Taeung Song AuthorDate: Tue, 28 Mar 2017 21:12:05 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Tue,

[tip:perf/core] perf annotate: Fix missing number of samples for source_line_samples

Commit-ID: 99094a5e941fe88d95cbd594e6a41bee24003ecb Gitweb: http://git.kernel.org/tip/99094a5e941fe88d95cbd594e6a41bee24003ecb Author: Taeung Song AuthorDate: Tue, 28 Mar 2017 21:12:05 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 4 Apr 2017 21:08:00 -0300 perf annotate:

[tip:perf/core] perf sdt powerpc: Add argument support

Commit-ID: f5a70801b7832bfcb865e95c39bdef8eac21226f Gitweb: http://git.kernel.org/tip/f5a70801b7832bfcb865e95c39bdef8eac21226f Author: Ravi Bangoria AuthorDate: Tue, 28 Mar 2017 15:17:54 +0530 Committer: Arnaldo Carvalho de Melo

[tip:perf/core] perf sdt powerpc: Add argument support

Commit-ID: f5a70801b7832bfcb865e95c39bdef8eac21226f Gitweb: http://git.kernel.org/tip/f5a70801b7832bfcb865e95c39bdef8eac21226f Author: Ravi Bangoria AuthorDate: Tue, 28 Mar 2017 15:17:54 +0530 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 4 Apr 2017 10:36:59 -0300 perf sdt

[tip:perf/core] perf tools: Handle allocation failures gracefully

Commit-ID: f05082b5479d91ee5c04f311acaa394ce0c5e6d2 Gitweb: http://git.kernel.org/tip/f05082b5479d91ee5c04f311acaa394ce0c5e6d2 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 4 Apr 2017 12:05:37 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf tools: Don't die on a print function

Commit-ID: 9c0899f15766158df8b3bd152f5da0b6c1bd2806 Gitweb: http://git.kernel.org/tip/9c0899f15766158df8b3bd152f5da0b6c1bd2806 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 4 Apr 2017 12:11:07 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf tools: Don't die on a print function

Commit-ID: 9c0899f15766158df8b3bd152f5da0b6c1bd2806 Gitweb: http://git.kernel.org/tip/9c0899f15766158df8b3bd152f5da0b6c1bd2806 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 4 Apr 2017 12:11:07 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 4 Apr 2017 12:11:07 -0300

[tip:perf/core] perf tools: Handle allocation failures gracefully

Commit-ID: f05082b5479d91ee5c04f311acaa394ce0c5e6d2 Gitweb: http://git.kernel.org/tip/f05082b5479d91ee5c04f311acaa394ce0c5e6d2 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 4 Apr 2017 12:05:37 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 4 Apr 2017 12:05:37 -0300

[tip:perf/core] perf tools: Remove die() call

Commit-ID: 427748068a973627b406bf7312342b6fe4742d07 Gitweb: http://git.kernel.org/tip/427748068a973627b406bf7312342b6fe4742d07 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 4 Apr 2017 11:36:22 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf tools: Remove die() call

Commit-ID: 427748068a973627b406bf7312342b6fe4742d07 Gitweb: http://git.kernel.org/tip/427748068a973627b406bf7312342b6fe4742d07 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 4 Apr 2017 11:36:22 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 4 Apr 2017 11:36:22 -0300

Re: [PATCH] cgroup: switch to BUG_ON()

On 2017/3/27 0:24, Nicholas Mc Guire wrote: > Use BUG_ON() rather than an explicit if followed by BUG() for > improved readability and also consistency. > > Signed-off-by: Nicholas Mc Guire > --- > > Found by coccinelle: bugon.cocci > ./kernel/cgroup/cpuset.c:2125:2-5:

Re: [PATCH] cgroup: switch to BUG_ON()

On 2017/3/27 0:24, Nicholas Mc Guire wrote: > Use BUG_ON() rather than an explicit if followed by BUG() for > improved readability and also consistency. > > Signed-off-by: Nicholas Mc Guire > --- > > Found by coccinelle: bugon.cocci > ./kernel/cgroup/cpuset.c:2125:2-5: WARNING: Use BUG_ON

[tip:perf/core] perf vendor events intel: Add missing space in json descriptions

Commit-ID: 3401e8d1e1300742ed41910b9338b9da52689a16 Gitweb: http://git.kernel.org/tip/3401e8d1e1300742ed41910b9338b9da52689a16 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:22:18 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

[tip:perf/core] perf vendor events intel: Add missing space in json descriptions

Commit-ID: 3401e8d1e1300742ed41910b9338b9da52689a16 Gitweb: http://git.kernel.org/tip/3401e8d1e1300742ed41910b9338b9da52689a16 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:22:18 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:35:50 -0700 perf vendor events intel: Add

[tip:perf/core] perf vendor events intel: Add uncore_arb JSON support

Commit-ID: af34cb4fad1ba08db199ef1b0a529549e041dd25 Gitweb: http://git.kernel.org/tip/af34cb4fad1ba08db199ef1b0a529549e041dd25 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:20:28 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

[tip:perf/core] perf vendor events intel: Add uncore_arb JSON support

Commit-ID: af34cb4fad1ba08db199ef1b0a529549e041dd25 Gitweb: http://git.kernel.org/tip/af34cb4fad1ba08db199ef1b0a529549e041dd25 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:20:28 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:35:41 -0700 perf vendor events intel: Add

[tip:perf/core] perf vendor events intel: Add uncore events for Broadwell client

Commit-ID: 092a95d41655bdd31d7d28f1788818724505feb2 Gitweb: http://git.kernel.org/tip/092a95d41655bdd31d7d28f1788818724505feb2 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:17:42 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

[tip:perf/core] perf vendor events intel: Add uncore events for Skylake client

Commit-ID: 92c6de0f10a80e4936fac04148bd3783a7c2b9f8 Gitweb: http://git.kernel.org/tip/92c6de0f10a80e4936fac04148bd3783a7c2b9f8 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:18:15 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

[tip:perf/core] perf vendor events intel: Add uncore events for Broadwell client

Commit-ID: 092a95d41655bdd31d7d28f1788818724505feb2 Gitweb: http://git.kernel.org/tip/092a95d41655bdd31d7d28f1788818724505feb2 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:17:42 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:35:23 -0700 perf vendor events intel: Add

[tip:perf/core] perf vendor events intel: Add uncore events for Skylake client

Commit-ID: 92c6de0f10a80e4936fac04148bd3783a7c2b9f8 Gitweb: http://git.kernel.org/tip/92c6de0f10a80e4936fac04148bd3783a7c2b9f8 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:18:15 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:35:32 -0700 perf vendor events intel: Add

[tip:perf/core] perf vendor events intel: Add uncore events for Haswell client

Commit-ID: 0585c6265e66f952bcb6280cf078e5e120bd367a Gitweb: http://git.kernel.org/tip/0585c6265e66f952bcb6280cf078e5e120bd367a Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:17:02 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

[tip:perf/core] perf vendor events intel: Add uncore events for Haswell client

Commit-ID: 0585c6265e66f952bcb6280cf078e5e120bd367a Gitweb: http://git.kernel.org/tip/0585c6265e66f952bcb6280cf078e5e120bd367a Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:17:02 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:35:15 -0700 perf vendor events intel: Add

[tip:perf/core] perf vendor events intel: Add missing UNC_M_DCLOCKTICKS for Broadwell DE uncore

Commit-ID: 9c4e2e2589c99ed01db6245847b4bd44bc053330 Gitweb: http://git.kernel.org/tip/9c4e2e2589c99ed01db6245847b4bd44bc053330 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:07:53 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

Re: [kernel-hardening] [PATCH v2 1/7] bug: Clarify help text for BUG_ON_DATA_CORRUPTION

> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index 77fadface4f9..5ac4d1148385 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1998,9 +1998,12 @@ config BUG_ON_DATA_CORRUPTION > >   bool "Trigger a BUG when data corruption is detected" > >   select DEBUG_LIST > >  

[tip:perf/core] perf vendor events intel: Add missing UNC_M_DCLOCKTICKS for Broadwell DE uncore

Commit-ID: 9c4e2e2589c99ed01db6245847b4bd44bc053330 Gitweb: http://git.kernel.org/tip/9c4e2e2589c99ed01db6245847b4bd44bc053330 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:07:53 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:32:25 -0700 perf vendor events intel: Add

Re: [kernel-hardening] [PATCH v2 1/7] bug: Clarify help text for BUG_ON_DATA_CORRUPTION

> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index 77fadface4f9..5ac4d1148385 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1998,9 +1998,12 @@ config BUG_ON_DATA_CORRUPTION > >   bool "Trigger a BUG when data corruption is detected" > >   select DEBUG_LIST > >  

[tip:perf/core] perf vendor events intel: Add uncore events for Sandy Bridge client

Commit-ID: 80432c7311dbcf0c814d4923480b055a725b0be2 Gitweb: http://git.kernel.org/tip/80432c7311dbcf0c814d4923480b055a725b0be2 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:12:44 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

[tip:perf/core] perf vendor events intel: Add uncore events for Ivy Bridge client

Commit-ID: bccdcb2a77ba0bef17baf152179e30ca35459a0c Gitweb: http://git.kernel.org/tip/bccdcb2a77ba0bef17baf152179e30ca35459a0c Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:14:02 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017

Re: [PATCH] net: phy: broadcom: Add support for the BCM54210E

On Wed, Apr 5, 2017 at 3:17 PM, Florian Fainelli wrote: > > > On 04/04/2017 10:33 PM, Joel Stanley wrote: >> This device is a single-port RGMII 10/100/1000BASE-T PHY with EEE & WOL. > > This looks good, although Rafal did beat you to it: > >

Re: [PATCH] net: phy: broadcom: Add support for the BCM54210E

On Wed, Apr 5, 2017 at 3:17 PM, Florian Fainelli wrote: > > > On 04/04/2017 10:33 PM, Joel Stanley wrote: >> This device is a single-port RGMII 10/100/1000BASE-T PHY with EEE & WOL. > > This looks good, although Rafal did beat you to it: > > 0fc9ae107669760c2a8658cb5b5876dbe525e08d ("net: phy:

[tip:perf/core] perf vendor events intel: Add uncore events for Sandy Bridge client

Commit-ID: 80432c7311dbcf0c814d4923480b055a725b0be2 Gitweb: http://git.kernel.org/tip/80432c7311dbcf0c814d4923480b055a725b0be2 Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:12:44 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:34:15 -0700 perf vendor events intel: Add

[tip:perf/core] perf vendor events intel: Add uncore events for Ivy Bridge client

Commit-ID: bccdcb2a77ba0bef17baf152179e30ca35459a0c Gitweb: http://git.kernel.org/tip/bccdcb2a77ba0bef17baf152179e30ca35459a0c Author: Andi Kleen AuthorDate: Wed, 29 Mar 2017 17:14:02 -0700 Committer: Andi Kleen CommitDate: Thu, 30 Mar 2017 13:35:01 -0700 perf vendor events intel: Add

Re: [PATCH] net: phy: broadcom: Add support for the BCM54210E

On 04/04/2017 10:33 PM, Joel Stanley wrote: > This device is a single-port RGMII 10/100/1000BASE-T PHY with EEE & WOL. This looks good, although Rafal did beat you to it: 0fc9ae107669760c2a8658cb5b5876dbe525e08d ("net: phy: broadcom: add support for BCM54210E") -- Florian

Re: [PATCH] net: phy: broadcom: Add support for the BCM54210E

On 04/04/2017 10:33 PM, Joel Stanley wrote: > This device is a single-port RGMII 10/100/1000BASE-T PHY with EEE & WOL. This looks good, although Rafal did beat you to it: 0fc9ae107669760c2a8658cb5b5876dbe525e08d ("net: phy: broadcom: add support for BCM54210E") -- Florian

Re: [GIT PULL 00/13] perf/core improvements and fixes

; Merge tag 'perf-core-for-mingo-4.12-20170331' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core > (2017-04-01 12:43:40 +0200) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git >

Re: [GIT PULL 00/13] perf/core improvements and fixes

perf-core-for-mingo-4.12-20170331' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core > (2017-04-01 12:43:40 +0200) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-core-fo

[PATCH] net: phy: broadcom: Add support for the BCM54210E

This device is a single-port RGMII 10/100/1000BASE-T PHY with EEE & WOL. Signed-off-by: Joel Stanley --- drivers/net/phy/broadcom.c | 13 + include/linux/brcmphy.h| 2 ++ 2 files changed, 15 insertions(+) diff --git a/drivers/net/phy/broadcom.c

[PATCH] net: phy: broadcom: Add support for the BCM54210E

This device is a single-port RGMII 10/100/1000BASE-T PHY with EEE & WOL. Signed-off-by: Joel Stanley --- drivers/net/phy/broadcom.c | 13 + include/linux/brcmphy.h| 2 ++ 2 files changed, 15 insertions(+) diff --git a/drivers/net/phy/broadcom.c b/drivers/net/phy/broadcom.c

[PATCH] cs-2000-cp: keep Reserved bit on each register

From: Kuninori Morimoto Thus CS2000 datasheet is indicating below, this patch follows it. WARNING: All "Reserved" registers must maintain their default state to ensure proper functional operation. Signed-off-by: Kuninori Morimoto

[PATCH] cs-2000-cp: keep Reserved bit on each register

From: Kuninori Morimoto Thus CS2000 datasheet is indicating below, this patch follows it. WARNING: All "Reserved" registers must maintain their default state to ensure proper functional operation. Signed-off-by: Kuninori Morimoto --- drivers/clk/clk-cs2000-cp.c | 25

[PATCH 1/1] ARM: dts: armada-xp-linksys-mamba: use wan instead of internet for DSA port

The LEDs for the "wan" port are already labeled "mamba:amber:wan" resp. "mamba:white:wan". So besides being an outlier with regard to the rest of the product line (see table below) changing the label fixes an internal inconsistency as well. This will be visible in user space. Given commit

[PATCH 1/1] ARM: dts: armada-xp-linksys-mamba: use wan instead of internet for DSA port

The LEDs for the "wan" port are already labeled "mamba:amber:wan" resp. "mamba:white:wan". So besides being an outlier with regard to the rest of the product line (see table below) changing the label fixes an internal inconsistency as well. This will be visible in user space. Given commit

Re: net/sched: latent livelock in dev_deactivate_many() due to yield() usage

On Tue, Apr 4, 2017 at 8:20 PM, Mike Galbraith wrote: > - while (some_qdisc_is_busy(dev)) > - yield(); > + swait_event_timeout(swait, !some_qdisc_is_busy(dev), 1); > } I don't see why this is an improvement even if I don't care

Re: net/sched: latent livelock in dev_deactivate_many() due to yield() usage

On Tue, Apr 4, 2017 at 8:20 PM, Mike Galbraith wrote: > - while (some_qdisc_is_busy(dev)) > - yield(); > + swait_event_timeout(swait, !some_qdisc_is_busy(dev), 1); > } I don't see why this is an improvement even if I don't care about the

Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Wed, Apr 5, 2017 at 12:27 PM, NeilBrown wrote: > On Tue, Apr 04 2017, Christoph Hellwig wrote: > >> Looks fine, >> >> Reviewed-by: Christoph Hellwig >> >> But if you actually care about performance in any way I'd suggest >> to use the loop device in direct I/O

Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Wed, Apr 5, 2017 at 12:27 PM, NeilBrown wrote: > On Tue, Apr 04 2017, Christoph Hellwig wrote: > >> Looks fine, >> >> Reviewed-by: Christoph Hellwig >> >> But if you actually care about performance in any way I'd suggest >> to use the loop device in direct I/O mode.. > > The losetup on my

[PATCH] af_unix: Use designated initializers

Prepare to mark sensitive kernel structures for randomization by making sure they're using designated initializers. These were identified during allyesconfig builds of x86, arm, and arm64, and the initializer fixes were extracted from grsecurity. In this case, NULL initialize with { } instead of

[PATCH] af_unix: Use designated initializers

Prepare to mark sensitive kernel structures for randomization by making sure they're using designated initializers. These were identified during allyesconfig builds of x86, arm, and arm64, and the initializer fixes were extracted from grsecurity. In this case, NULL initialize with { } instead of

Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Wed, Apr 5, 2017 at 12:33 PM, NeilBrown wrote: > > When a filesystem is mounted from a loop device, writes are > throttled by balance_dirty_pages() twice: once when writing > to the filesystem and once when the loop_handle_cmd() writes > to the backing file. This

ia64 exceptions (Re: [RFC][CFT][PATCHSET v1] uaccess unification)

On Wed, Mar 29, 2017 at 06:57:06AM +0100, Al Viro wrote: > And again, metag and ia64 parts are simply not there - both architectures > zero-pad in __copy_from_user_inatomic() and that really needs fixing. > In case of metag there's __copy_to_user() breakage as well, AFAICS, and > I've been unable

Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Wed, Apr 5, 2017 at 12:33 PM, NeilBrown wrote: > > When a filesystem is mounted from a loop device, writes are > throttled by balance_dirty_pages() twice: once when writing > to the filesystem and once when the loop_handle_cmd() writes > to the backing file. This double-throttling can trigger

ia64 exceptions (Re: [RFC][CFT][PATCHSET v1] uaccess unification)

On Wed, Mar 29, 2017 at 06:57:06AM +0100, Al Viro wrote: > And again, metag and ia64 parts are simply not there - both architectures > zero-pad in __copy_from_user_inatomic() and that really needs fixing. > In case of metag there's __copy_to_user() breakage as well, AFAICS, and > I've been unable

RE: [STABLE REGRESSION] iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3

Hi Ritesh, I do not have the environment so should not have a try but I think Srinivas's patch should be Ok for your platform. Please have a try. Thanks a lot! BR Song Hongyan -Original Message- From: Ritesh Raj Sarraf [mailto:r...@researchut.com] Sent: Tuesday, April 4, 2017

RE: [STABLE REGRESSION] iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3

Hi Ritesh, I do not have the environment so should not have a try but I think Srinivas's patch should be Ok for your platform. Please have a try. Thanks a lot! BR Song Hongyan -Original Message- From: Ritesh Raj Sarraf [mailto:r...@researchut.com] Sent: Tuesday, April 4, 2017

Re: [PATCH] mmc: core: add mmc-card hardware reset enable support

Hi, On 04/04/2017 11:16 PM, Richard Leitner wrote: > Some eMMCs disable their hardware reset line (RST_N) by default. To enable > it the host must set the corresponding bit in ECSD. An example for such > a device is the Micron MTFCxGACAANA-4M. > > This patch adds a new mmc-card devicetree

Re: [PATCH] mmc: core: add mmc-card hardware reset enable support

Hi, On 04/04/2017 11:16 PM, Richard Leitner wrote: > Some eMMCs disable their hardware reset line (RST_N) by default. To enable > it the host must set the corresponding bit in ECSD. An example for such > a device is the Micron MTFCxGACAANA-4M. > > This patch adds a new mmc-card devicetree

Watchdog catches hard CPU lock in 4.8.11

This is on a Dell Latitude D830 with 4GB of RAM. I am booting kernel 4.8.11 from a live Linux distribution in a USB stick. The CPU is a Core 2 Duo T7100 capable of 64-bit kernels but this live Linux kernel is 32-bit. The hard drive has Windows 7 and is not involved in this live Linux system.

Watchdog catches hard CPU lock in 4.8.11

This is on a Dell Latitude D830 with 4GB of RAM. I am booting kernel 4.8.11 from a live Linux distribution in a USB stick. The CPU is a Core 2 Duo T7100 capable of 64-bit kernels but this live Linux kernel is 32-bit. The hard drive has Windows 7 and is not involved in this live Linux system.

[PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

When a filesystem is mounted from a loop device, writes are throttled by balance_dirty_pages() twice: once when writing to the filesystem and once when the loop_handle_cmd() writes to the backing file. This double-throttling can trigger positive feedback loops that create significant delays.

[PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

When a filesystem is mounted from a loop device, writes are throttled by balance_dirty_pages() twice: once when writing to the filesystem and once when the loop_handle_cmd() writes to the backing file. This double-throttling can trigger positive feedback loops that create significant delays.

Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Tue, Apr 04 2017, Ming Lei wrote: > On Mon, Apr 3, 2017 at 9:18 AM, NeilBrown wrote: >> >> When a filesystem is mounted from a loop device, writes are >> throttled by balance_dirty_pages() twice: once when writing >> to the filesystem and once when the loop_handle_cmd() writes

RE: [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Wednesday, April 5, 2017 11:54 AM, Michael S. Tsirkin wrote: > On Wed, Apr 05, 2017 at 03:31:36AM +, Wang, Wei W wrote: > > On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > > > The implementation of the current virtio-balloon is not very > > > efficient, because the ballooned pages are

Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Tue, Apr 04 2017, Ming Lei wrote: > On Mon, Apr 3, 2017 at 9:18 AM, NeilBrown wrote: >> >> When a filesystem is mounted from a loop device, writes are >> throttled by balance_dirty_pages() twice: once when writing >> to the filesystem and once when the loop_handle_cmd() writes >> to the

RE: [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Wednesday, April 5, 2017 11:54 AM, Michael S. Tsirkin wrote: > On Wed, Apr 05, 2017 at 03:31:36AM +, Wang, Wei W wrote: > > On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > > > The implementation of the current virtio-balloon is not very > > > efficient, because the ballooned pages are

Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Tue, Apr 04 2017, Christoph Hellwig wrote: > Looks fine, > > Reviewed-by: Christoph Hellwig > > But if you actually care about performance in any way I'd suggest > to use the loop device in direct I/O mode.. The losetup on my test VM is too old to support that :-( I guess it

Re: [PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Tue, Apr 04 2017, Christoph Hellwig wrote: > Looks fine, > > Reviewed-by: Christoph Hellwig > > But if you actually care about performance in any way I'd suggest > to use the loop device in direct I/O mode.. The losetup on my test VM is too old to support that :-( I guess it might be time to

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, 2017-04-05 at 06:51 +0300, Michael S. Tsirkin wrote: > Any issues at all left with this tree? > In particular any regressions? Nothing blatantly obvious in a testdrive that lasted a couple minutes. I'd have to beat on it a bit to look for things beyond the reported, but can't afford to

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, 2017-04-05 at 06:51 +0300, Michael S. Tsirkin wrote: > Any issues at all left with this tree? > In particular any regressions? Nothing blatantly obvious in a testdrive that lasted a couple minutes. I'd have to beat on it a bit to look for things beyond the reported, but can't afford to

Re: [PATCH v6 01/11] powerpc/powernv: Data structure and macros definitions

On Tuesday 04 April 2017 07:18 AM, Daniel Axtens wrote: Hi, +#define IMC_MAX_CHIPS 32 +#define IMC_MAX_PMUS 32 +#define IMC_MAX_PMU_NAME_LEN 256 I've noticed this is used as both the maximum length for event names and event value strings. Would

Re: [PATCH v6 01/11] powerpc/powernv: Data structure and macros definitions

On Tuesday 04 April 2017 07:18 AM, Daniel Axtens wrote: Hi, +#define IMC_MAX_CHIPS 32 +#define IMC_MAX_PMUS 32 +#define IMC_MAX_PMU_NAME_LEN 256 I've noticed this is used as both the maximum length for event names and event value strings. Would

Re: pull-request: wireless-drivers-next 2017-04-03

David Miller writes: > From: Kalle Valo > Date: Tue, 04 Apr 2017 20:48:35 +0300 > >> David Miller writes: >> >>> From: Kalle Valo >>> Date: Mon, 03 Apr 2017 14:26:10 +0300 >>> here few really small

Re: pull-request: wireless-drivers-next 2017-04-03

David Miller writes: > From: Kalle Valo > Date: Tue, 04 Apr 2017 20:48:35 +0300 > >> David Miller writes: >> >>> From: Kalle Valo >>> Date: Mon, 03 Apr 2017 14:26:10 +0300 >>> here few really small fixes. I'm hoping this to be the last pull request for 4.11. Please let

Re: [PATCH ALT4 V2 1/2] audit: show fstype:pathname for entries with anonymous parents

On 2017-04-04 17:19, Paul Moore wrote: > On Tue, Apr 4, 2017 at 5:21 AM, Richard Guy Briggs wrote: > > Tracefs or debugfs were causing hundreds to thousands of null PATH > > records to be associated with the init_module and finit_module SYSCALL > > records on a few modules when

Re: [PATCH ALT4 V2 1/2] audit: show fstype:pathname for entries with anonymous parents

On 2017-04-04 17:19, Paul Moore wrote: > On Tue, Apr 4, 2017 at 5:21 AM, Richard Guy Briggs wrote: > > Tracefs or debugfs were causing hundreds to thousands of null PATH > > records to be associated with the init_module and finit_module SYSCALL > > records on a few modules when the following rule

[PATCH v2 1/2] serial: 8250: Add flag so drivers can avoid THRE probe

The probing of THRE irq behaviour assumes the other end will be reading bytes out of the buffer in order to probe the port at driver init. In some cases the other end cannot be relied upon to read these bytes, so provide a flag for them to skip this step. Bit 16 was chosen as the flags are a int

[PATCH v2 1/2] serial: 8250: Add flag so drivers can avoid THRE probe

The probing of THRE irq behaviour assumes the other end will be reading bytes out of the buffer in order to probe the port at driver init. In some cases the other end cannot be relied upon to read these bytes, so provide a flag for them to skip this step. Bit 16 was chosen as the flags are a int

[PATCH v2 2/2] drivers/serial: Add driver for Aspeed virtual UART

From: Jeremy Kerr This change adds a driver for the 16550-based Aspeed virtual UART device. We use a similar process to the of_serial driver for device probe, but expose some VUART-specific functions through sysfs too. The VUART is two UART 'front ends' connected by their FIFO

[PATCH v2 2/2] drivers/serial: Add driver for Aspeed virtual UART

From: Jeremy Kerr This change adds a driver for the 16550-based Aspeed virtual UART device. We use a similar process to the of_serial driver for device probe, but expose some VUART-specific functions through sysfs too. The VUART is two UART 'front ends' connected by their FIFO (no actual serial

[PATCH v2 0/2] drivers: serial: Aspeed VUART driver

This is v2 of a driver for the Aspeed VUART. This version addresses feedback from Andy and Greg, and adds Rob's ack for the bindings change. The VUART is a serial device on the BMC side of the LPC bus that connects a BMC to it's host processor. We add a flag to the serial core to allow the

[PATCH v2 0/2] drivers: serial: Aspeed VUART driver

This is v2 of a driver for the Aspeed VUART. This version addresses feedback from Andy and Greg, and adds Rob's ack for the bindings change. The VUART is a serial device on the BMC side of the LPC bus that connects a BMC to it's host processor. We add a flag to the serial core to allow the

Re: [PATCH] arm64: perf: Count EL2 events if either of kernel and hyp are not excluded

On Tue, Apr 4, 2017 at 5:56 PM, Will Deacon wrote: > On Tue, Apr 04, 2017 at 05:37:10PM +0530, Ganapatrao Kulkarni wrote: >> On Tue, Apr 4, 2017 at 4:48 PM, Will Deacon wrote: >> > On Tue, Apr 04, 2017 at 04:10:55PM +0530, Ganapatrao Kulkarni wrote: >>

Re: [PATCH] arm64: perf: Count EL2 events if either of kernel and hyp are not excluded

On Tue, Apr 4, 2017 at 5:56 PM, Will Deacon wrote: > On Tue, Apr 04, 2017 at 05:37:10PM +0530, Ganapatrao Kulkarni wrote: >> On Tue, Apr 4, 2017 at 4:48 PM, Will Deacon wrote: >> > On Tue, Apr 04, 2017 at 04:10:55PM +0530, Ganapatrao Kulkarni wrote: >> >> commit d98ecda (arm64: perf: Count EL2

Re: [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Wed, Apr 05, 2017 at 03:31:36AM +, Wang, Wei W wrote: > On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > > The implementation of the current virtio-balloon is not very efficient, > > because > > the ballooned pages are transferred to the host one by one. Here is the > > breakdown of

Re: [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Wed, Apr 05, 2017 at 03:31:36AM +, Wang, Wei W wrote: > On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > > The implementation of the current virtio-balloon is not very efficient, > > because > > the ballooned pages are transferred to the host one by one. Here is the > > breakdown of

Re: [linux-sunxi] [PATCH 03/11] dt-bindings: add device tree binding for X-Powers AXP803 PMIC

On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: > AXP803 is a PMIC produced by Shenzhen X-Powers, with either I2C or RSB > bus. > > Add a compatible for it. > > Signed-off-by: Icenowy Zheng > --- > Documentation/devicetree/bindings/mfd/axp20x.txt | 3 ++- >

Re: [linux-sunxi] [PATCH 03/11] dt-bindings: add device tree binding for X-Powers AXP803 PMIC

On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: > AXP803 is a PMIC produced by Shenzhen X-Powers, with either I2C or RSB > bus. > > Add a compatible for it. > > Signed-off-by: Icenowy Zheng > --- > Documentation/devicetree/bindings/mfd/axp20x.txt | 3 ++- > 1 file changed, 2 insertions(+),

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, Apr 05, 2017 at 05:24:30AM +0200, Mike Galbraith wrote: > On Wed, 2017-04-05 at 06:13 +0300, Michael S. Tsirkin wrote: > > On Wed, Apr 05, 2017 at 05:09:09AM +0200, Mike Galbraith wrote: > > > On Tue, 2017-04-04 at 22:03 +0300, Michael S. Tsirkin wrote: > > > > > > > since I couldn't

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, Apr 05, 2017 at 05:24:30AM +0200, Mike Galbraith wrote: > On Wed, 2017-04-05 at 06:13 +0300, Michael S. Tsirkin wrote: > > On Wed, Apr 05, 2017 at 05:09:09AM +0200, Mike Galbraith wrote: > > > On Tue, 2017-04-04 at 22:03 +0300, Michael S. Tsirkin wrote: > > > > > > > since I couldn't

Re: [linux-sunxi] [PATCH 02/11] arm64: allwinner: a64: add NMI controller on A64

On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: > Allwinner A64 SoC features a NMI controller, which is usually connected > to the AXP PMIC. > > Add support for it. > > Signed-off-by: Icenowy Zheng This might not be the best representation of the R_INTC

Re: [linux-sunxi] [PATCH 02/11] arm64: allwinner: a64: add NMI controller on A64

On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: > Allwinner A64 SoC features a NMI controller, which is usually connected > to the AXP PMIC. > > Add support for it. > > Signed-off-by: Icenowy Zheng This might not be the best representation of the R_INTC block. Though we'd need to change it

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, Apr 05, 2017 at 05:40:06AM +0200, Mike Galbraith wrote: > On Wed, 2017-04-05 at 05:24 +0200, Mike Galbraith wrote: > > On Wed, 2017-04-05 at 06:13 +0300, Michael S. Tsirkin wrote: > > > On Wed, Apr 05, 2017 at 05:09:09AM +0200, Mike Galbraith wrote: > > > > On Tue, 2017-04-04 at 22:03

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, Apr 05, 2017 at 05:40:06AM +0200, Mike Galbraith wrote: > On Wed, 2017-04-05 at 05:24 +0200, Mike Galbraith wrote: > > On Wed, 2017-04-05 at 06:13 +0300, Michael S. Tsirkin wrote: > > > On Wed, Apr 05, 2017 at 05:09:09AM +0200, Mike Galbraith wrote: > > > > On Tue, 2017-04-04 at 22:03

Re: [linux-sunxi] [PATCH 01/11] arm64: allwinner: a64: enable RSB on A64

On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: > Allwinner A64 have a RSB controller like the one on A23/A33 SoCs. > > Add it and its pinmux. > > Signed-off-by: Icenowy Zheng > --- > arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 21 +

Re: [linux-sunxi] [PATCH 01/11] arm64: allwinner: a64: enable RSB on A64

On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: > Allwinner A64 have a RSB controller like the one on A23/A33 SoCs. > > Add it and its pinmux. > > Signed-off-by: Icenowy Zheng > --- > arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 21 + > 1 file changed, 21

Re: [PATCH 1/2] soc: qcom: smsm: Handle probe deferral

On Mon 03 Apr 19:38 PDT 2017, Jonathan Neusch?fer wrote: > On Mon, Mar 27, 2017 at 11:18:29PM -0700, Bjorn Andersson wrote: [..] > > However, for us to reach this point in smsm_probe() the above > > qcom_smem_get() must have returned successfully, i.e. we have SMEM in > > place so there's no need

Re: [PATCH 1/2] soc: qcom: smsm: Handle probe deferral

On Mon 03 Apr 19:38 PDT 2017, Jonathan Neusch?fer wrote: > On Mon, Mar 27, 2017 at 11:18:29PM -0700, Bjorn Andersson wrote: [..] > > However, for us to reach this point in smsm_probe() the above > > qcom_smem_get() must have returned successfully, i.e. we have SMEM in > > place so there's no need

Re: [PATCH] ebpf: verify the output of the JIT

Hi Kees, On Tue, Apr 04, 2017 at 03:17:57PM -0700, Kees Cook wrote: > On Tue, Apr 4, 2017 at 3:08 PM, Tycho Andersen wrote: > > The goal of this patch is to protect the JIT against an attacker with a > > write-in-memory primitive. The JIT allocates a buffer which will

Re: [PATCH] ebpf: verify the output of the JIT

Hi Kees, On Tue, Apr 04, 2017 at 03:17:57PM -0700, Kees Cook wrote: > On Tue, Apr 4, 2017 at 3:08 PM, Tycho Andersen wrote: > > The goal of this patch is to protect the JIT against an attacker with a > > write-in-memory primitive. The JIT allocates a buffer which will eventually > > be marked

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, 2017-04-05 at 05:24 +0200, Mike Galbraith wrote: > On Wed, 2017-04-05 at 06:13 +0300, Michael S. Tsirkin wrote: > > On Wed, Apr 05, 2017 at 05:09:09AM +0200, Mike Galbraith wrote: > > > On Tue, 2017-04-04 at 22:03 +0300, Michael S. Tsirkin wrote: > > > > > > > since I couldn't reproduce,

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, 2017-04-05 at 05:24 +0200, Mike Galbraith wrote: > On Wed, 2017-04-05 at 06:13 +0300, Michael S. Tsirkin wrote: > > On Wed, Apr 05, 2017 at 05:09:09AM +0200, Mike Galbraith wrote: > > > On Tue, 2017-04-04 at 22:03 +0300, Michael S. Tsirkin wrote: > > > > > > > since I couldn't reproduce,

  1   2   3   4   5   6   7   8   9   10   >