Re: 4.8-rc4 spews "BUG: sleeping function called from invalid context at fs/dcache.c:757"

On Mon, 2016-08-29 at 16:18 +0100, Al Viro wrote: > On Mon, Aug 29, 2016 at 04:35:46PM +0200, Takashi Iwai wrote: > > > [] dput+0x46/0x400 > ... which should not be called in atomic contexts > > [] follow_down_one+0x27/0x60 > ... and neither should this > > []

Re: 4.8-rc4 spews "BUG: sleeping function called from invalid context at fs/dcache.c:757"

On Mon, 2016-08-29 at 16:18 +0100, Al Viro wrote: > On Mon, Aug 29, 2016 at 04:35:46PM +0200, Takashi Iwai wrote: > > > [] dput+0x46/0x400 > ... which should not be called in atomic contexts > > [] follow_down_one+0x27/0x60 > ... and neither should this > > []

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

On 08/30/2016 01:54 AM, Heiko Stübner wrote: Am Montag, 29. August 2016, 10:35:44 schrieb Doug Anderson: Hi, On Sun, Aug 28, 2016 at 8:21 AM, Heiko Stübner wrote: Hi Xing, Elaine, Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: From: Elaine Zhang

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

On 08/30/2016 01:54 AM, Heiko Stübner wrote: Am Montag, 29. August 2016, 10:35:44 schrieb Doug Anderson: Hi, On Sun, Aug 28, 2016 at 8:21 AM, Heiko Stübner wrote: Hi Xing, Elaine, Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: From: Elaine Zhang The goal is that we can

Re: [PATCH] tpm: fix sparse errors caused by tpm enum tpm_capabilities

On Tue, Aug 30, 2016 at 02:50:49AM +0300, Jarkko Sakkinen wrote: > The enum tpm_capabilites is not a legit constant expression but calls > cpu_to_be32. This commit makes cap_id a separate parameter in order to > provide less confusing API and declares the type as u32. The byter order > conversion

Re: [PATCH] tpm: fix sparse errors caused by tpm enum tpm_capabilities

On Tue, Aug 30, 2016 at 02:50:49AM +0300, Jarkko Sakkinen wrote: > The enum tpm_capabilites is not a legit constant expression but calls > cpu_to_be32. This commit makes cap_id a separate parameter in order to > provide less confusing API and declares the type as u32. The byter order > conversion

[PATCH] tpm: fix invalid constant expressions in tpm.h

The enums tpm_capabilities and tpm_sub_capabilities do not contain legit constant expressions. This commit makes cap_id a separate parameter in order to provide less confusing API and cap_id and subcap_id will be u32 with the cpu byte order. The byte order conversions are handled internally by

[PATCH] tpm: fix invalid constant expressions in tpm.h

The enums tpm_capabilities and tpm_sub_capabilities do not contain legit constant expressions. This commit makes cap_id a separate parameter in order to provide less confusing API and cap_id and subcap_id will be u32 with the cpu byte order. The byte order conversions are handled internally by

Re: [PATCH RFC UGLY] x86,mm,sched: make lazy TLB mode even lazier

On August 29, 2016 4:55:02 PM PDT, Andy Lutomirski wrote: >On Aug 29, 2016 7:54 AM, "Rik van Riel" wrote: >> >> On Sun, 2016-08-28 at 01:11 -0700, Andy Lutomirski wrote: >> > On Aug 25, 2016 9:06 PM, "Rik van Riel" wrote: >> > > >> > >

Re: [PATCH RFC UGLY] x86,mm,sched: make lazy TLB mode even lazier

On August 29, 2016 4:55:02 PM PDT, Andy Lutomirski wrote: >On Aug 29, 2016 7:54 AM, "Rik van Riel" wrote: >> >> On Sun, 2016-08-28 at 01:11 -0700, Andy Lutomirski wrote: >> > On Aug 25, 2016 9:06 PM, "Rik van Riel" wrote: >> > > >> > > Subject: x86,mm,sched: make lazy TLB mode even lazier >> >

Re: [PATCH] printk/nmi: avoid direct printk()-s from __printk_nmi_flush()

On (08/29/16 17:16), Petr Mladek wrote: [..] > The comment above is not longer valid. oh, yes. it shouldn't even be there. > > -static void print_nmi_seq_line(struct nmi_seq_buf *s, int start, int end) > > +static void __print_nmi_seq_line(const char *text, int len) > > Also the name of the

Re: [PATCH v4 resend] mm/slab: Improve performance of gathering slabinfo stats

On Mon, 2016-08-29 at 17:44 -0700, Aruna Ramakrishna wrote: > This patch optimizes 'cat /proc/slabinfo' by maintaining a counter for > total number of allocated slabs per node, per cache. [] > We tested this after > growing the dentry cache to 70GB, and the performance improved from 2s to > 5ms.

Re: [PATCH] printk/nmi: avoid direct printk()-s from __printk_nmi_flush()

On (08/29/16 17:16), Petr Mladek wrote: [..] > The comment above is not longer valid. oh, yes. it shouldn't even be there. > > -static void print_nmi_seq_line(struct nmi_seq_buf *s, int start, int end) > > +static void __print_nmi_seq_line(const char *text, int len) > > Also the name of the

Re: [PATCH v4 resend] mm/slab: Improve performance of gathering slabinfo stats

On Mon, 2016-08-29 at 17:44 -0700, Aruna Ramakrishna wrote: > This patch optimizes 'cat /proc/slabinfo' by maintaining a counter for > total number of allocated slabs per node, per cache. [] > We tested this after > growing the dentry cache to 70GB, and the performance improved from 2s to > 5ms.

Re: [PATCH] arm64: dts: rockchip: Explicitly set pclk_pmu_src on rk3399

On 08/30/2016 02:18 AM, Brian Norris wrote: On Mon, Aug 29, 2016 at 11:11:24AM -0700, Doug Anderson wrote: On rk3399 we explicitly set ppll in the device tree to 67600. The ppll has one major child, pclk_pmu_src, that is the parent of lots of other clocks. Right now nobody is setting

Re: [PATCH] arm64: dts: rockchip: Explicitly set pclk_pmu_src on rk3399

On 08/30/2016 02:18 AM, Brian Norris wrote: On Mon, Aug 29, 2016 at 11:11:24AM -0700, Doug Anderson wrote: On rk3399 we explicitly set ppll in the device tree to 67600. The ppll has one major child, pclk_pmu_src, that is the parent of lots of other clocks. Right now nobody is setting

Re: [PATCH v14 04/14] task_isolation: add initial support

On Mon, Aug 15, 2016 at 10:59:55AM -0400, Chris Metcalf wrote: > On 8/11/2016 2:50 PM, Christoph Lameter wrote: > >On Thu, 11 Aug 2016, Frederic Weisbecker wrote: > > > >>Do we need to quiesce vmstat everytime before entering userspace? > >>I thought that vmstat only need to be offlined once and

Re: [PATCH v14 04/14] task_isolation: add initial support

On Mon, Aug 15, 2016 at 10:59:55AM -0400, Chris Metcalf wrote: > On 8/11/2016 2:50 PM, Christoph Lameter wrote: > >On Thu, 11 Aug 2016, Frederic Weisbecker wrote: > > > >>Do we need to quiesce vmstat everytime before entering userspace? > >>I thought that vmstat only need to be offlined once and

Re: [PATCH v4 resend] mm/slab: Improve performance of gathering slabinfo stats

On 08/29/2016 05:44 PM, Aruna Ramakrishna wrote: On large systems, when some slab caches grow to millions of objects (and many gigabytes), running 'cat /proc/slabinfo' can take up to 1-2 seconds. During this time, interrupts are disabled while walking the slab lists (slabs_full, slabs_partial,

Re: [PATCH v4 resend] mm/slab: Improve performance of gathering slabinfo stats

On 08/29/2016 05:44 PM, Aruna Ramakrishna wrote: On large systems, when some slab caches grow to millions of objects (and many gigabytes), running 'cat /proc/slabinfo' can take up to 1-2 seconds. During this time, interrupts are disabled while walking the slab lists (slabs_full, slabs_partial,

[PATCH v4 resend] mm/slab: Improve performance of gathering slabinfo stats

On large systems, when some slab caches grow to millions of objects (and many gigabytes), running 'cat /proc/slabinfo' can take up to 1-2 seconds. During this time, interrupts are disabled while walking the slab lists (slabs_full, slabs_partial, and slabs_free) for each node, and this sometimes

[PATCH v4 resend] mm/slab: Improve performance of gathering slabinfo stats

On large systems, when some slab caches grow to millions of objects (and many gigabytes), running 'cat /proc/slabinfo' can take up to 1-2 seconds. During this time, interrupts are disabled while walking the slab lists (slabs_full, slabs_partial, and slabs_free) for each node, and this sometimes

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

* Rob Herring [160829 17:24]: > On Mon, Aug 29, 2016 at 5:35 PM, Tony Lindgren wrote: > > It seems we can use the ePAPR 1.1 status fail-sss to do this. > > Quoting "Table 2-4 Values for status property" we have "fail-sss": > > > > "Indicates that the device

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

* Rob Herring [160829 17:24]: > On Mon, Aug 29, 2016 at 5:35 PM, Tony Lindgren wrote: > > It seems we can use the ePAPR 1.1 status fail-sss to do this. > > Quoting "Table 2-4 Values for status property" we have "fail-sss": > > > > "Indicates that the device is not operational. A serious error

Re: [PATCH v2] PCI: altera: Retrain link in rootport mode only

Hi Bjorn, On 8/24/2016 10:54 AM, Bjorn Helgaas wrote: [+cc Ray, Scott, Jon, bcm-kernel-feedback-list] On Wed, Aug 24, 2016 at 03:07:52PM +0800, Ley Foon Tan wrote: On Mon, Aug 22, 2016 at 11:47 PM, Bjorn Helgaas wrote: On Fri, Aug 19, 2016 at 04:24:38PM +0800, Ley Foon

Re: [PATCH v2] PCI: altera: Retrain link in rootport mode only

Hi Bjorn, On 8/24/2016 10:54 AM, Bjorn Helgaas wrote: [+cc Ray, Scott, Jon, bcm-kernel-feedback-list] On Wed, Aug 24, 2016 at 03:07:52PM +0800, Ley Foon Tan wrote: On Mon, Aug 22, 2016 at 11:47 PM, Bjorn Helgaas wrote: On Fri, Aug 19, 2016 at 04:24:38PM +0800, Ley Foon Tan wrote: Altera

Re: [PATCH net-next 3/6] bpf: perf_event progs should only use preallocated maps

On 08/27/2016 04:31 AM, Alexei Starovoitov wrote: Make sure that BPF_PROG_TYPE_PERF_EVENT programs only use preallocated hash maps, since doing memory allocation in overflow_handler can crash depending on where nmi got triggered. Signed-off-by: Alexei Starovoitov Acked-by:

Re: [PATCH net-next 3/6] bpf: perf_event progs should only use preallocated maps

On 08/27/2016 04:31 AM, Alexei Starovoitov wrote: Make sure that BPF_PROG_TYPE_PERF_EVENT programs only use preallocated hash maps, since doing memory allocation in overflow_handler can crash depending on where nmi got triggered. Signed-off-by: Alexei Starovoitov Acked-by: Daniel Borkmann

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Mon, Aug 29, 2016 at 5:35 PM, Tony Lindgren wrote: > We have devices that are in incomplete state, but still need to be > probed to allow properly idling them for PM. Some examples are > devices that are not pinned out on certain packages, or otherwise > unusable on some

Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Mon, Aug 29, 2016 at 5:35 PM, Tony Lindgren wrote: > We have devices that are in incomplete state, but still need to be > probed to allow properly idling them for PM. Some examples are > devices that are not pinned out on certain packages, or otherwise > unusable on some SoCs. > > Setting

Re: [PATCH net-next 2/6] bpf: introduce BPF_PROG_TYPE_PERF_EVENT program type

On 08/27/2016 04:31 AM, Alexei Starovoitov wrote: Introduce BPF_PROG_TYPE_PERF_EVENT programs that can be attached to HW and SW perf events (PERF_TYPE_HARDWARE and PERF_TYPE_SOFTWARE correspondingly in uapi/linux/perf_event.h) The program visible context meta structure is struct

Re: [PATCH net-next 2/6] bpf: introduce BPF_PROG_TYPE_PERF_EVENT program type

On 08/27/2016 04:31 AM, Alexei Starovoitov wrote: Introduce BPF_PROG_TYPE_PERF_EVENT programs that can be attached to HW and SW perf events (PERF_TYPE_HARDWARE and PERF_TYPE_SOFTWARE correspondingly in uapi/linux/perf_event.h) The program visible context meta structure is struct

Re: [PATCH] PCI: rockchip: Correct the register value for clearing client interrupts

On Mon, Aug 29, 2016 at 02:14:11PM -0700, Brian Norris wrote: > I'm pretty sure the bitwise 'or' was meant for the value parameter, not > the register parameter. > > This resolves an interrupt storm, where if we receive any client IRQs > (e.g., correctable errors), we fail to ever clear them

Re: [PATCH] PCI: rockchip: Correct the register value for clearing client interrupts

On Mon, Aug 29, 2016 at 02:14:11PM -0700, Brian Norris wrote: > I'm pretty sure the bitwise 'or' was meant for the value parameter, not > the register parameter. > > This resolves an interrupt storm, where if we receive any client IRQs > (e.g., correctable errors), we fail to ever clear them

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Aug 29, 2016 11:30 AM, "Marcin Nowakowski" wrote: > > Syscall metadata makes an assumption that only a single syscall number > corresponds to a given method. This is true for most archs, but > can break tracing otherwise. > > For MIPS platforms, depending on the

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Aug 29, 2016 11:30 AM, "Marcin Nowakowski" wrote: > > Syscall metadata makes an assumption that only a single syscall number > corresponds to a given method. This is true for most archs, but > can break tracing otherwise. > > For MIPS platforms, depending on the choice of supported ABIs, up to

Re: [PATCH RFC UGLY] x86,mm,sched: make lazy TLB mode even lazier

On Aug 29, 2016 7:54 AM, "Rik van Riel" wrote: > > On Sun, 2016-08-28 at 01:11 -0700, Andy Lutomirski wrote: > > On Aug 25, 2016 9:06 PM, "Rik van Riel" wrote: > > > > > > Subject: x86,mm,sched: make lazy TLB mode even lazier > > > > > > Lazy TLB mode can result

Re: [PATCH RFC UGLY] x86,mm,sched: make lazy TLB mode even lazier

On Aug 29, 2016 7:54 AM, "Rik van Riel" wrote: > > On Sun, 2016-08-28 at 01:11 -0700, Andy Lutomirski wrote: > > On Aug 25, 2016 9:06 PM, "Rik van Riel" wrote: > > > > > > Subject: x86,mm,sched: make lazy TLB mode even lazier > > > > > > Lazy TLB mode can result in an idle CPU being woken up for

Re: Kernel Freeze with American Megatrends BIOS

On Mon, Aug 29, 2016 at 09:55:56PM +0200, Roland Singer wrote: > Just tried it and the system didn't freeze. However it will freeze > after some time (few minutes while working). > > Seams to be pci_read_config_dword. Where is this exactly defined? pci_read_config_dword() is defined in

Re: Kernel Freeze with American Megatrends BIOS

On Mon, Aug 29, 2016 at 09:55:56PM +0200, Roland Singer wrote: > Just tried it and the system didn't freeze. However it will freeze > after some time (few minutes while working). > > Seams to be pci_read_config_dword. Where is this exactly defined? pci_read_config_dword() is defined in

[PATCH] tpm: fix sparse errors caused by tpm enum tpm_capabilities

The enum tpm_capabilites is not a legit constant expression but calls cpu_to_be32. This commit makes cap_id a separate parameter in order to provide less confusing API and declares the type as u32. The byter order conversion is handled internally by tpm1_getcap_cmd. $ make C=2 M=drivers/char/tpm

[PATCH] tpm: fix sparse errors caused by tpm enum tpm_capabilities

The enum tpm_capabilites is not a legit constant expression but calls cpu_to_be32. This commit makes cap_id a separate parameter in order to provide less confusing API and declares the type as u32. The byter order conversion is handled internally by tpm1_getcap_cmd. $ make C=2 M=drivers/char/tpm

Re: [PATCH] bdev: fix NULL pointer dereference in sync()/close() race

Hello, On Mon, Aug 29, 2016 at 11:33:41PM +0200, Vegard Nossum wrote: > On 08/29/2016 09:55 PM, Tejun Heo wrote: > > I think the right thing to do there is doing blkdev_get() / > > blkdev_put() around func() invocation in iterate_bdevs() rather than > > holding bd_mutex across the callback. Can

Re: [PATCH] bdev: fix NULL pointer dereference in sync()/close() race

Hello, On Mon, Aug 29, 2016 at 11:33:41PM +0200, Vegard Nossum wrote: > On 08/29/2016 09:55 PM, Tejun Heo wrote: > > I think the right thing to do there is doing blkdev_get() / > > blkdev_put() around func() invocation in iterate_bdevs() rather than > > holding bd_mutex across the callback. Can

[PATCH] microblaze: move xlnx,compound to default bus matching

Microblaze bus probing is partially broken because "xlnx,compound" is missing from the default bus probe. Add it to the default and remove from the Microblaze arch code. Fixes: 44a7185c2ae6 ("of/platform: Add common method to populate default bus") Signed-off-by: Rob Herring Cc:

[PATCH] microblaze: move xlnx,compound to default bus matching

Microblaze bus probing is partially broken because "xlnx,compound" is missing from the default bus probe. Add it to the default and remove from the Microblaze arch code. Fixes: 44a7185c2ae6 ("of/platform: Add common method to populate default bus") Signed-off-by: Rob Herring Cc: Michal Simek

Re: [PATCH net-next 1/6] bpf: support 8-byte metafield access

On 08/27/2016 04:31 AM, Alexei Starovoitov wrote: The verifier supported only 4-byte metafields in struct __sk_buff and struct xdp_md. The metafields in upcoming struct bpf_perf_event are 8-byte to match register width in struct pt_regs. Teach verifier to recognize 8-byte metafield access. The

Re: [PATCH net-next 1/6] bpf: support 8-byte metafield access

On 08/27/2016 04:31 AM, Alexei Starovoitov wrote: The verifier supported only 4-byte metafields in struct __sk_buff and struct xdp_md. The metafields in upcoming struct bpf_perf_event are 8-byte to match register width in struct pt_regs. Teach verifier to recognize 8-byte metafield access. The

[PATCH 1/4 v2] drm/bridge: adv7511: Move the common data structures to header file

From: Archit Taneja This patch moves the adv7511 data structure to header file so that the audio driver file could use it. Cc: David Airlie Cc: Archit Taneja Cc: Laurent Pinchart Cc: Wolfram

[PATCH 1/4 v2] drm/bridge: adv7511: Move the common data structures to header file

From: Archit Taneja This patch moves the adv7511 data structure to header file so that the audio driver file could use it. Cc: David Airlie Cc: Archit Taneja Cc: Laurent Pinchart Cc: Wolfram Sang Cc: Srinivas Kandagatla Cc: "Ville Syrjälä" Cc: Boris Brezillon Cc: Andy Green Cc: Dave

[PATCH 3/4 v2] drm/bridge: adv7511: Enable the audio data and clock pads on adv7533

From: Srinivas Kandagatla This patch enables the Audio Data and Clock pads to the adv7533 bridge. Without this patch audio can not be played. Cc: David Airlie Cc: Archit Taneja Cc: Laurent Pinchart

[PATCH 3/4 v2] drm/bridge: adv7511: Enable the audio data and clock pads on adv7533

From: Srinivas Kandagatla This patch enables the Audio Data and Clock pads to the adv7533 bridge. Without this patch audio can not be played. Cc: David Airlie Cc: Archit Taneja Cc: Laurent Pinchart Cc: Wolfram Sang Cc: Srinivas Kandagatla Cc: "Ville Syrjälä" Cc: Boris Brezillon Cc: Andy

[PATCH 0/4 v2] Audio support for adv7511 hdmi bridge

This is another swing at getting the adv7511 hdmi bridge audio support reviewed. I've taken the core audio work done by Lars-Peter Clausen, and adapted by Srinivas Kandagatla and Archit Taneja, and tried to rework it to use the hdmi-codec sound driver. This patchset, along with the i2s driver

[PATCH 4/4 v2] drm/bridge: adv7511: Initialize audio packet on adv7533

From: Andy Green Set the initial audio packet settings to allow the audio driver to work. Cc: David Airlie Cc: Archit Taneja Cc: Laurent Pinchart Cc: Wolfram Sang

[PATCH 0/4 v2] Audio support for adv7511 hdmi bridge

This is another swing at getting the adv7511 hdmi bridge audio support reviewed. I've taken the core audio work done by Lars-Peter Clausen, and adapted by Srinivas Kandagatla and Archit Taneja, and tried to rework it to use the hdmi-codec sound driver. This patchset, along with the i2s driver

[PATCH 4/4 v2] drm/bridge: adv7511: Initialize audio packet on adv7533

From: Andy Green Set the initial audio packet settings to allow the audio driver to work. Cc: David Airlie Cc: Archit Taneja Cc: Laurent Pinchart Cc: Wolfram Sang Cc: Srinivas Kandagatla Cc: "Ville Syrjälä" Cc: Boris Brezillon Cc: Andy Green Cc: Dave Long Cc: Guodong Xu Cc: Zhangfei

Re: [PATCH v2] power: bq24735-charger: Request status GPIO with initial input setup

Hi, On Mon, Aug 29, 2016 at 08:15:03PM +0200, Paul Kocialkowski wrote: > This requests the status GPIO with initial input setup. it is required > to read the GPIO status at probe time and thus correctly avoid sending > i2c messages when AC is not plugged. > > When requesting the GPIO without

[PATCH 2/4 v2] drm/bridge: adv7511: Add Audio support.

This patch adds support to Audio for both adv7511 and adv7533 bridge chips. This patch was originally from [1] by Lars-Peter Clausen and was adapted by Archit Taneja and Srinivas Kandagatla . Then I heavily reworked it to

Re: [PATCH v2] power: bq24735-charger: Request status GPIO with initial input setup

Hi, On Mon, Aug 29, 2016 at 08:15:03PM +0200, Paul Kocialkowski wrote: > This requests the status GPIO with initial input setup. it is required > to read the GPIO status at probe time and thus correctly avoid sending > i2c messages when AC is not plugged. > > When requesting the GPIO without

[PATCH 2/4 v2] drm/bridge: adv7511: Add Audio support.

This patch adds support to Audio for both adv7511 and adv7533 bridge chips. This patch was originally from [1] by Lars-Peter Clausen and was adapted by Archit Taneja and Srinivas Kandagatla . Then I heavily reworked it to use the hdmi-codec driver. So credit to them, but blame to me. [1]

[PATCH] blk-mq: abstract tag allocation out into scale_bitmap library

From: Omar Sandoval This is a generally useful data structure, so make it available to anyone else who might want to use it. It's also a nice cleanup separating the allocation logic from the rest of the tag handling logic. The code is behind a new Kconfig option,

[PATCH] blk-mq: abstract tag allocation out into scale_bitmap library

From: Omar Sandoval This is a generally useful data structure, so make it available to anyone else who might want to use it. It's also a nice cleanup separating the allocation logic from the rest of the tag handling logic. The code is behind a new Kconfig option, CONFIG_SCALE_BITMAP, which is

[PATCH 2/2] sdhci-of-arasan: Set controller to test mode when fails-without-test-cd is present

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

Re: [PATCH 2/3] nvme: Pass pointers, not dma addresses, to nvme_get/set_features()

On Mon, Aug 29, 2016 at 9:27 AM, Keith Busch wrote: > On Mon, Aug 29, 2016 at 02:25:45AM -0700, Andy Lutomirski wrote: >> + /* >> + * A controller "page" may be bigger than a Linux page, but we can >> + * be conservative here. >> + */ > > It is the

[PATCH 1/2] sdhci-of-arasan: Add device tree parameter fails-without-test-cd bit

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

[PATCH 2/2] sdhci-of-arasan: Set controller to test mode when fails-without-test-cd is present

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

Re: [PATCH 2/3] nvme: Pass pointers, not dma addresses, to nvme_get/set_features()

On Mon, Aug 29, 2016 at 9:27 AM, Keith Busch wrote: > On Mon, Aug 29, 2016 at 02:25:45AM -0700, Andy Lutomirski wrote: >> + /* >> + * A controller "page" may be bigger than a Linux page, but we can >> + * be conservative here. >> + */ > > It is the actually other way around:

[PATCH 1/2] sdhci-of-arasan: Add device tree parameter fails-without-test-cd bit

The sdhci controller on xilinx zynq devices will not function unless the CD bit is provided. http://www.xilinx.com/support/answers/61064.html In cases where it is impossible to provide the CD bit in hardware, setting the controller to test mode and then setting inserted to true will get the

Re: [PATCH 3/3] nvme: Enable autonomous power state transitions

On Aug 29, 2016 8:07 AM, "J Freyensee" wrote: > > On Mon, 2016-08-29 at 02:25 -0700, Andy Lutomirski wrote: > > NVME devices can advertise multiple power states. These states can > > be either "operational" (the device is fully functional but possibly > > slow)

Re: [PATCH 3/3] nvme: Enable autonomous power state transitions

On Aug 29, 2016 8:07 AM, "J Freyensee" wrote: > > On Mon, 2016-08-29 at 02:25 -0700, Andy Lutomirski wrote: > > NVME devices can advertise multiple power states. These states can > > be either "operational" (the device is fully functional but possibly > > slow) or "non-operational" (the device

Re: [PATCH 3/3] nvme: Enable autonomous power state transitions

On Aug 29, 2016 9:35 AM, "Keith Busch" wrote: > > On Mon, Aug 29, 2016 at 02:25:46AM -0700, Andy Lutomirski wrote: > > + /* > > + * By default, allow up to 25ms of APST-induced latency. This will > > + * have no effect on non-APST supporting controllers (i.e.

Re: [PATCH 3/3] nvme: Enable autonomous power state transitions

On Aug 29, 2016 9:35 AM, "Keith Busch" wrote: > > On Mon, Aug 29, 2016 at 02:25:46AM -0700, Andy Lutomirski wrote: > > + /* > > + * By default, allow up to 25ms of APST-induced latency. This will > > + * have no effect on non-APST supporting controllers (i.e. any > > + *

Re: [PATCH net-next 0/6] perf, bpf: add support for bpf in sw/hw perf_events

On Mon, Aug 29, 2016 at 12:58:00PM +0200, Peter Zijlstra wrote: > On Fri, Aug 26, 2016 at 07:31:18PM -0700, Alexei Starovoitov wrote: > > Hi Peter, Dave, > > > > this patch set is a follow up to the discussion: > > https://lkml.org/lkml/2016/8/4/304 > > Please don't use lkml.org links, that site

Re: [PATCH net-next 0/6] perf, bpf: add support for bpf in sw/hw perf_events

On Mon, Aug 29, 2016 at 12:58:00PM +0200, Peter Zijlstra wrote: > On Fri, Aug 26, 2016 at 07:31:18PM -0700, Alexei Starovoitov wrote: > > Hi Peter, Dave, > > > > this patch set is a follow up to the discussion: > > https://lkml.org/lkml/2016/8/4/304 > > Please don't use lkml.org links, that site

Re: [RFC 2/3] uprobe: drop isdigit() check in create_trace_uprobe

2016-08-30 1:59 GMT+03:00 Steven Rostedt : > On Mon, 29 Aug 2016 18:58:13 -0400 > Steven Rostedt wrote: > >> On Thu, 25 Aug 2016 18:21:09 +0300 >> Dmitry Safonov wrote: >> >> > It's useless. Before: >> > [tracing]# echo 'p:test

Re: [RFC 2/3] uprobe: drop isdigit() check in create_trace_uprobe

2016-08-30 1:59 GMT+03:00 Steven Rostedt : > On Mon, 29 Aug 2016 18:58:13 -0400 > Steven Rostedt wrote: > >> On Thu, 25 Aug 2016 18:21:09 +0300 >> Dmitry Safonov wrote: >> >> > It's useless. Before: >> > [tracing]# echo 'p:test /a:0x0' >> uprobe_events >> > [tracing]# echo 'p:test a:0x0' >>

Re: [RFC 2/3] uprobe: drop isdigit() check in create_trace_uprobe

On Mon, 29 Aug 2016 18:58:13 -0400 Steven Rostedt wrote: > On Thu, 25 Aug 2016 18:21:09 +0300 > Dmitry Safonov wrote: > > > It's useless. Before: > > [tracing]# echo 'p:test /a:0x0' >> uprobe_events > > [tracing]# echo 'p:test a:0x0' >>

Re: [RFC 2/3] uprobe: drop isdigit() check in create_trace_uprobe

On Mon, 29 Aug 2016 18:58:13 -0400 Steven Rostedt wrote: > On Thu, 25 Aug 2016 18:21:09 +0300 > Dmitry Safonov wrote: > > > It's useless. Before: > > [tracing]# echo 'p:test /a:0x0' >> uprobe_events > > [tracing]# echo 'p:test a:0x0' >> uprobe_events > > -bash: echo: write error: No such

Re: [RFC 2/3] uprobe: drop isdigit() check in create_trace_uprobe

On Thu, 25 Aug 2016 18:21:09 +0300 Dmitry Safonov wrote: > It's useless. Before: > [tracing]# echo 'p:test /a:0x0' >> uprobe_events > [tracing]# echo 'p:test a:0x0' >> uprobe_events > -bash: echo: write error: No such file or directory > [tracing]# echo 'p:test

Re: [RFC 2/3] uprobe: drop isdigit() check in create_trace_uprobe

On Thu, 25 Aug 2016 18:21:09 +0300 Dmitry Safonov wrote: > It's useless. Before: > [tracing]# echo 'p:test /a:0x0' >> uprobe_events > [tracing]# echo 'p:test a:0x0' >> uprobe_events > -bash: echo: write error: No such file or directory > [tracing]# echo 'p:test 1:0x0' >> uprobe_events >

Re: [PATCH] perf probe: Move dwarf specific functions to dwarf-aux.c

On Mon, 29 Aug 2016 20:40:01 +0530 Ravi Bangoria wrote: > Move generic dwarf related functions from util/probe-finder.c to > util/dwarf-aux.c. Function names and their prototype are also > changed accordingly. No functionality changes. Code looks OK, could you

Re: [PATCH] perf probe: Move dwarf specific functions to dwarf-aux.c

On Mon, 29 Aug 2016 20:40:01 +0530 Ravi Bangoria wrote: > Move generic dwarf related functions from util/probe-finder.c to > util/dwarf-aux.c. Function names and their prototype are also > changed accordingly. No functionality changes. Code looks OK, could you please add usage comments as same

[PATCH v6] tpm: fix a race condition in tpm2_unseal_trusted()

Unseal and load operations should be done as an atomic operation. This commit introduces unlocked tpm_transmit() so that tpm2_unseal_trusted() can do the locking by itself. v2: Introduced an unlocked unseal operation instead of changing locking strategy in order to make less intrusive bug fix

[PATCH v6] tpm: fix a race condition in tpm2_unseal_trusted()

Unseal and load operations should be done as an atomic operation. This commit introduces unlocked tpm_transmit() so that tpm2_unseal_trusted() can do the locking by itself. v2: Introduced an unlocked unseal operation instead of changing locking strategy in order to make less intrusive bug fix

Re: [PATCHv2 0/2] introduce get_task_exe_file and use it to fix audit_exe_compare

On Tue, Aug 23, 2016 at 10:20 AM, Mateusz Guzik wrote: > audit_exe_compare directly accesses mm->exe_file without making sure the > object is stable. Fixing it using current primitives results in > partially duplicating what proc_exe_link is doing. > > As such, introduce a

Re: [PATCH] thp: reduce usage of huge zero page's atomic counter

On Mon, 29 Aug 2016 14:31:20 +0800 Aaron Lu wrote: > > The global zero page is used to satisfy an anonymous read fault. If > THP(Transparent HugePage) is enabled then the global huge zero page is used. > The global huge zero page uses an atomic counter for reference counting

Re: [PATCHv2 0/2] introduce get_task_exe_file and use it to fix audit_exe_compare

On Tue, Aug 23, 2016 at 10:20 AM, Mateusz Guzik wrote: > audit_exe_compare directly accesses mm->exe_file without making sure the > object is stable. Fixing it using current primitives results in > partially duplicating what proc_exe_link is doing. > > As such, introduce a trivial helper which

Re: [PATCH] thp: reduce usage of huge zero page's atomic counter

On Mon, 29 Aug 2016 14:31:20 +0800 Aaron Lu wrote: > > The global zero page is used to satisfy an anonymous read fault. If > THP(Transparent HugePage) is enabled then the global huge zero page is used. > The global huge zero page uses an atomic counter for reference counting > and is

[PATCH RFC] ARM: dts: samsung: add rga-lvds panel in itop elite

It is actually a lvds panel connected through a rga-lvds bridge. But I really have no idea about what does a port mean in fimd node. Also how should I configure this panel size? I think the i2c found on the panel schematic, but it more likely to be used a touch screen touth. Also the touch screen

[PATCH RFC] ARM: dts: samsung: add rga-lvds panel in itop elite

It is actually a lvds panel connected through a rga-lvds bridge. But I really have no idea about what does a port mean in fimd node. Also how should I configure this panel size? I think the i2c found on the panel schematic, but it more likely to be used a touch screen touth. Also the touch screen

Re: [BISECTED REGRESSION] v4.8-rc: DT/OCTEON driver probing broken

On Sun, Aug 28, 2016 at 7:22 AM, Aaro Koskinen wrote: > Hi, > > On Sun, Aug 28, 2016 at 12:34:06PM +0200, Thorsten Leemhuis wrote: >> Lo! Kefeng, below report made it to the list of regression for 4.8, but >> afaics nothing happened after the initial report. Is there maybe

[PATCH RFC 0/2] net: Iterate over cpu_present_mask during calculation of percpu statistics

Many variables of statistics type are made percpu in kernel. This allows to do not make them atomic or to do not use synchronization. The result value is calculated as sum of values on every possible cpu. The problem is this scales bad. The calculations may took a lot of time. For example, some

Re: [BISECTED REGRESSION] v4.8-rc: DT/OCTEON driver probing broken

On Sun, Aug 28, 2016 at 7:22 AM, Aaro Koskinen wrote: > Hi, > > On Sun, Aug 28, 2016 at 12:34:06PM +0200, Thorsten Leemhuis wrote: >> Lo! Kefeng, below report made it to the list of regression for 4.8, but >> afaics nothing happened after the initial report. Is there maybe some >> reason why it

[PATCH RFC 0/2] net: Iterate over cpu_present_mask during calculation of percpu statistics

Many variables of statistics type are made percpu in kernel. This allows to do not make them atomic or to do not use synchronization. The result value is calculated as sum of values on every possible cpu. The problem is this scales bad. The calculations may took a lot of time. For example, some

Re: kernel BUG at net/unix/garbage.c:149!"

On Sat, Aug 27, 2016 at 11:55 AM, Miklos Szeredi wrote: > > On Wed, Aug 24, 2016 at 11:40 PM, Hannes Frederic Sowa > wrote: > > On 24.08.2016 16:24, Nikolay Borisov wrote: > >> Hello, > >> > >> I hit the following BUG: > >> > >> [1851513.239831]

Re: kernel BUG at net/unix/garbage.c:149!"

On Sat, Aug 27, 2016 at 11:55 AM, Miklos Szeredi wrote: > > On Wed, Aug 24, 2016 at 11:40 PM, Hannes Frederic Sowa > wrote: > > On 24.08.2016 16:24, Nikolay Borisov wrote: > >> Hello, > >> > >> I hit the following BUG: > >> > >> [1851513.239831] [ cut here ] > >>

[PATCH RFC 2/2] net: Iterate over present cpus only during ipstats calculation

Use net_stats callback to iterate only present cpus mask. This gives a signify performance growth on configurations with large number of possible cpus. Signed-off-by: Kirill Tkhai --- net/ipv6/addrconf.c |4 +++- net/ipv6/af_inet6.c | 56

[PATCH RFC 2/2] net: Iterate over present cpus only during ipstats calculation

Use net_stats callback to iterate only present cpus mask. This gives a signify performance growth on configurations with large number of possible cpus. Signed-off-by: Kirill Tkhai --- net/ipv6/addrconf.c |4 +++- net/ipv6/af_inet6.c | 56 +++

[PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

We have devices that are in incomplete state, but still need to be probed to allow properly idling them for PM. Some examples are devices that are not pinned out on certain packages, or otherwise unusable on some SoCs. Setting status = "disabled" cannot be used for this case. Setting "disabled"

Re: [Documentation] State of CPU controller in cgroup v2

Hello, James. On Sat, Aug 20, 2016 at 10:34:14PM -0700, James Bottomley wrote: > I can see that process based is conceptually easier in v2 because you > begin with a process tree, but it would really be a pity to lose the > thread based controls we have now and permanently lose the ability to >

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