Re: [Patch v3 03/11] driver/edac/mpc85xx_edac: Drop setting/clearing RFXE bit in HID1

On Tue, Aug 09, 2016 at 04:40:44PM +, york sun wrote: > I want to add this, normally uncorrectable errors don't trigger machine > check on e500v1. RXFE controls different interrupt on e500v2. e500mc > doesn't support RXFE. Together with the reason I explained, I believe > EDAC driver

Re: [PACTH v1] mm, proc: Implement /proc//totmaps

On Tue, Aug 09, 2016 at 12:05:43PM -0400, robert.f...@collabora.com wrote: > From: Sonny Rao > > This is based on earlier work by Thiago Goncales. It implements a new > per process proc file which summarizes the contents of the smaps file > but doesn't display any

Re: [PATCH] mm: memcontrol: only mark charged pages with PageKmemcg

On Mon, 2016-08-08 at 14:20 -0700, Linus Torvalds wrote: > On Mon, Aug 8, 2016 at 1:03 PM, Vladimir Davydov > wrote: > > To distinguish non-slab pages charged to kmemcg we mark them PageKmemcg [..] > > Eric, can you confirm that this fixes your issue? > It is fixing

Re: [RFC] mm: Don't use radix tree writeback tags for pages in swap cache

Hi, Dave, Dave Hansen writes: > On 08/09/2016 09:17 AM, Huang, Ying wrote: >> File pages uses a set of radix tags (DIRTY, TOWRITE, WRITEBACK) to >> accelerate finding the pages with the specific tag in the the radix tree >> during writing back an inode. But for anonymous

RE: [RFC][PATCH 7/7] cpufreq: intel_pstate: Change P-state selection algorithm for Core

On 2016.08.05 17:02 Rafael J. Wysocki wrote: > On 2016.08.03 21:19 Doug Smythies wrote: >> On 2016.07.31 16:49 Rafael J. Wysocki wrote: >> >> >>> +static inline int32_t get_target_pstate_default(struct cpudata *cpu) >>> +{ >>> + struct sample *sample = >sample; >>> + int32_t busy_frac; >>> +

Re: [PATCH 4.6 00/96] 4.6.6-stable review

On Tue, Aug 09, 2016 at 09:19:26AM -0700, Guenter Roeck wrote: > On Tue, Aug 09, 2016 at 10:37:31AM +0200, Greg Kroah-Hartman wrote: > > On Tue, Aug 09, 2016 at 09:33:26AM +0100, Paul Burton wrote: > > > On 09/08/16 09:24, Greg Kroah-Hartman wrote: > > > > On Mon, Aug 08, 2016 at 10:03:39PM -0700,

Re: [PATCH 4.4 00/68] 4.4.17-stable review

On Tue, Aug 09, 2016 at 09:14:29AM -0700, Guenter Roeck wrote: > On Tue, Aug 09, 2016 at 10:21:33AM +0200, Greg Kroah-Hartman wrote: > > On Mon, Aug 08, 2016 at 09:22:24PM -0700, Guenter Roeck wrote: > > > On 08/08/2016 12:10 PM, Greg Kroah-Hartman wrote: > > > > This is the start of the stable

Re: [PATCH 4.6 00/96] 4.6.6-stable review

On Tue, Aug 09, 2016 at 09:10:58AM -0600, Shuah Khan wrote: > On 08/08/2016 01:10 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.6.6 release. > > There are 96 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH v2] net: dsa: b53: constify b53_io_ops structures

The b53_io_ops structures are never modified, so declare them as const. Done with the help of Coccinelle. Signed-off-by: Julia Lawall --- v2: Refer to the right structure in the commit message drivers/net/dsa/b53/b53_common.c |3 ++- drivers/net/dsa/b53/b53_mdio.c

Re: [linux-sunxi] Re: [PATCH v4 3/7] clk: sunxi: add generic multi-parent bus clock gates driver

On Tue, 9 Aug 2016 18:02:47 +0800 Chen-Yu Tsai wrote: > > The 'parent's of the bus gates are of no interest. > > They are supposed to be (no clear documentation) apb1, apb2, ahb1 and > > ahb2, but, as you well noticed in the patch 5/7, these clocks are fixed > > and have no gate.

Re: drivers/spi/spi.c:1160:3-9: preceding lock on line 1153

On Tue, Aug 09, 2016 at 06:35:06PM +0200, Julia Lawall wrote: > On Tue, 9 Aug 2016, Mark Brown wrote: > > On Tue, Aug 09, 2016 at 06:19:13PM +0200, Julia Lawall wrote: > > > Looks worth checking. > > I don't really have any idea what this is trying to tell me, sorry. > The important lines are

[PATCH V5 3/4] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge

Add a driver that create a drm_bridge and a drm_connector for the LVDS to DP++ display bridge of the GE B850v3. There are two physical bridges on the video signal pipeline: a STDP4028(LVDS to DP) and a STDP2690(DP to DP++). The hardware and firmware made it complicated for this binding to

Re: [lkp] [fs] 6141b4d642: xfstests.generic.079.fail

On Tue, Aug 9, 2016 at 9:39 AM, Eryu Guan wrote: > On Tue, Aug 09, 2016 at 11:14:38PM +0800, kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus >> commit

Re: [PATCH] i2c: don't print error when adding adapter fails

On 9 August 2016 at 13:36, Wolfram Sang wrote: > Since v4.8-rc1, the I2C core will print detailed information when adding an > I2C > adapter fails. So, drivers can skip this now. > > I am still undecided if I apply this as a single patch or break it out. But > for

Re: [PATCH v2 1/3] powerpc: Factor out common code in setup-common.c

On Sun, Jul 31, 2016 at 8:40 PM, Nicholas Piggin wrote: > On Thu, 28 Jul 2016 16:07:16 -0700 > Andrey Smirnov wrote: > >> Factor out a small bit of common code in machine_restart(), >> machine_power_off() and machine_halt(). >> >> Signed-off-by:

[PATCH v5 1/5] lib/dlock-list: Distributed and lock-protected lists

Linked list is used everywhere in the Linux kernel. However, if many threads are trying to add or delete entries into the same linked list, it can create a performance bottleneck. This patch introduces a new list APIs that provide a set of distributed lists (one per CPU), each of which is

Re: c6x linker issue on linux-next-20160808 + some linker table work

On Tue, 2016-08-09 at 06:37 -0700, Guenter Roeck wrote: > On 08/09/2016 01:11 AM, Luis R. Rodriguez wrote: > > > > Mark, Aurelien, > > > > I've run into a linker (ld) issue caused by the linker table work I've > > been working on [0]. I looked into this and for the life of me, I > > cannot

[PATCH v7 7/7] perf config: Initialize annotate_browser__opts with default config items

Set default config values for 'annotate' section with 'annotate_config_items[]' instead of actual bool type values. (e.g. using annotate_config_items[CONFIG_ANNOTATE_USE_OFFSET].value.b instead of 'true' bool type value for 'annotate.use_offset'.) Cc: Namhyung Kim Cc: Jiri

[PATCH v7 1/7] perf config: Introduce default_config_section and default_config_item for default config key-value pairs

When initializing default perf config values, we currently use values of actual type(int, bool, char *, etc.). For example, If there isn't a user config value for 'annotate.use_offset' config variable at ~/.perfconfig, default value for it is 'true' bool type value in perf like below. At

Re: [Patch v3 03/11] driver/edac/mpc85xx_edac: Drop setting/clearing RFXE bit in HID1

On 08/09/2016 08:57 AM, york@nxp.com wrote: > On 08/08/2016 11:56 PM, Borislav Petkov wrote: >> On Tue, Aug 09, 2016 at 05:06:39AM +, york sun wrote: >>> It is uncorrectable. DDR controller can only report the error. I don't >>> believe EDAC driver can do more. For the same reason I said

[PATCH] NFC: nfcmrvl: constify nfcmrvl_if_ops structures

The nfcmrvl_if_ops structures are never modified, so declare them as const. Done with the help of Coccinelle. Signed-off-by: Julia Lawall --- drivers/nfc/nfcmrvl/i2c.c |2 +- drivers/nfc/nfcmrvl/main.c|2 +- drivers/nfc/nfcmrvl/nfcmrvl.h |4 ++--

Re: S3 resume regression [1cf4f629d9d2 ("cpu/hotplug: Move online calls to hotplugged cpu")]

On Thu, Jul 14, 2016 at 04:29:42PM +0800, Feng Tang wrote: > if you only want it to work, you can try an old patch > https://bugzilla.kernel.org/attachment.cgi?id=76071 from a similar bug > https://bugzilla.kernel.org/show_bug.cgi?id=41932 > > Alistair Buxton confirmed it work for 3.18 at least >

Re: [PATCH v2 1/3] sched: Avoid that __wait_on_bit_lock() hangs

On 08/06, Bart Van Assche wrote: > > Although this patch works reliably in my tests, the above description > does not explain the hang. I will resend this patch with a better > description. Yes please, I'll ignore this series till then ;) See also another patch I sent a minute ago. Oleg.

Re: [PATCH] net: dsa: b53: constify xfrm_replay structures

On 08/09/2016 10:23 AM, Florian Fainelli wrote: > On 08/09/2016 09:58 AM, Julia Lawall wrote: >> The xfrm_replay structures are never modified, so declare them as const. > > You mean b53_io_ops here, right? Other than that LTGM, but this will > have to wait for "net"next to re_open since this is

Re: [PATCH 8/9] remoteproc: core: Skip resource table integrity checks if there are amendments

On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote: > There is little point wasting CPU cycles completing integrity checking > (i.e. ensuring nothing has changed) on the resource table if we *know* > that it will be changed (by us). In this patch we skip resource table > integrity checks if a

Re: [PATCH v4 2/3] locking/mutex: Enable optimistic spinning of woken task in wait queue

On 08/08/2016 01:29 PM, Peter Zijlstra wrote: On Mon, Jul 18, 2016 at 04:39:25PM -0400, Waiman Long wrote: Ding Tianhong reported a live-lock situation where a constant stream of incoming optimistic spinners blocked a task in the wait list from getting the mutex. This patch attempts to fix

[PATCH] x86/mm: minor warning message cleanup

Capitalize R in RIP. Signed-off-by: Prarit Bhargava Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: x...@kernel.org Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Andrew Morton

Re: [PATCH v2] exynos-drm: Fix unsupported GEM memory type error message to be clear

On Mon, Aug 08, 2016 at 05:48:20PM -0600, Shuah Khan wrote: > Fix unsupported GEM memory type error message to include the memory type > information. > > Signed-off-by: Shuah Khan > --- > Changes since v1: > -- Comment changed to read clearly > >

[PATCH V5 1/4] drm/imx-ldb: Add support to drm-bridge

Add support to attach a drm_bridge to imx-ldb in addition to existing support to attach a LVDS panel. This patch does a simple code refactoring by moving code from for_each_child_of_node iterator to a new function named imx_ldb_panel_ddc(). This was necessary to allow the panel ddc code to run

[PATCH V5 0/4] Add driver for GE B850v3 LVDS/DP++ Bridge

The series adds a driver that creates a drm_bridge and a drm_connector for the LVDS to DP++ display bridge of the GE B850v3. There are two physical bridges on the video signal pipeline: a STDP4028(LVDS to DP) and a STDP2690(DP to DP++). The hardware and firmware made it complicated for this

[RFC 04/11] mm, memcg: Support to charge/uncharge multiple swap entries

From: Huang Ying This patch make it possible to charge or uncharge a set of continuous swap entries in swap cgroup. The number of swap entries is specified via an added parameter. This will be used for THP (Transparent Huge Page) swap support. Where a whole swap cluster

[RFC 03/11] mm, memcg: Add swap_cgroup_iter iterator

From: Huang Ying Swap cgroup uses a discontinuous array to store the information for the swap entries. lookup_swap_cgroup() provides the good encapsulation to access one element of the discontinuous array. To make it easier to access multiple elements of the discontinuous

[PATCH V5 2/4] Documentation/devicetree/bindings: b850v3_lvds_dp

Devicetree bindings documentation for the GE B850v3 LVDS/DP++ display bridge. Cc: Martyn Welch Cc: Martin Donnelly Cc: Javier Martinez Canillas Cc: Enric Balletbo i Serra Cc: Philipp Zabel

[RFC 02/11] swap: Change SWAPFILE_CLUSTER to 512

From: Huang Ying In this patch, the size of swap cluster is changed to that of THP on x86_64 (512). This is for THP (Transparent Huge Page) swap support on x86_64. Where one swap cluster will be used to hold the contents of each THP swapped out. And some information of

Re: [PATCH v2 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization

On Tue, Aug 9, 2016 at 9:54 AM, Borislav Petkov wrote: > On Tue, Aug 09, 2016 at 09:35:54AM -0700, Thomas Garnier wrote: >> Default implementation expects 6 pages maximum are needed for low page >> allocations. If KASLR memory randomization is enabled, the worse case >> of e820

[PATCH v7 0/7] perf config: Introduce default config key-value pairs arrays

Hello, :) When initializing default perf config values, we currently use values of actual type(int, bool, char *, etc.). But I suggest using default config key-value pairs arrays. For example, If there isn't a user config value for 'annotate.use_offset' config variable at ~/.perfconfig, default

[PATCH v7 6/7] perf config: Add default section and item arrays for 'annotate' config

Actual values for default configs of 'annotate' section is like below. (at ui/browsers/annoate.c) static struct annotate_browser_opt { bool hide_src_code, use_offset, jump_arrows, show_linenr, show_nr_jumps,

[PATCH v7 3/7] perf config: Add default section and item arrays for 'colors' config

Actual values for default configs of 'colors' section is like below. (at ui/browser.c) static struct ui_browser_colorset { const char *name, *fg, *bg; int colorset; } ui_browser__colorsets[] = { { .colorset = HE_COLORSET_TOP, .name =

[PATCH v7 4/7] perf config: Use combined {fore,back}ground colors value instead of each two color

To easily set default config values into actual variables for 'colors' config, it would be better that actual variables for each 'colors' config have only one value like 'default_config_item' type. If we use combined {fore,back}ground colors values in ui_browser_colorset, it smoothly work to

Re: [PACTH v1] mm, proc: Implement /proc//totmaps

On Tue, Aug 9, 2016 at 9:29 AM, Mateusz Guzik wrote: > On Tue, Aug 09, 2016 at 12:05:43PM -0400, robert.f...@collabora.com wrote: >> From: Sonny Rao >> >> This is based on earlier work by Thiago Goncales. It implements a new >> per process proc file

Re: [PATCH V3] printk: Create pr_ functions

On Tue, 2016-08-09 at 19:01 +0200, Geert Uytterhoeven wrote: > Hi Joe, Hi Geert > On Fri, Jun 24, 2016 at 5:46 AM, Joe Perches wrote: > > Using functions instead of macros can reduce overall code size > > by eliminating unnecessary "KERN_SOH" prefixes from > > format strings.

Re: [PATCH 1/9] remoteproc: core: Ensure error message is clear

On Tue, 09 Aug 2016, Bjorn Andersson wrote: > On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote: > > > Before this patch, the dma_alloc_coherent() failure path printed out: > > > > "dma_alloc_coherent err: 16760832" > > > > ... alluding to the Linux error code being 16760832, but seeing as > >

Re: [PATCHv2 3/4] pci: Determine actual VPD size on first access

On Tue, Aug 9, 2016 at 5:54 AM, Alexey Kardashevskiy wrote: > On 10/02/16 08:04, Bjorn Helgaas wrote: >> On Wed, Jan 13, 2016 at 12:25:34PM +0100, Hannes Reinecke wrote: >>> PCI-2.2 VPD entries have a maximum size of 32k, but might actually >>> be smaller than that. To figure out

Re: [PATCH v9 0/9] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

Hi Tomasz On 9 August 2016 at 19:03, Tomasz Nowicki wrote: > Hi Fu, > > Are you planing to respin the series based on v4.8-rc1 ? My IORT patches > depend on this series since they will end up in the same drivers/acpi/arm64/ > > I think patches are in good shape so we need to

Re: [PATCH v2 2/3] powerpc: Call chained reset handlers during reset

On Sun, Jul 31, 2016 at 8:47 PM, Nicholas Piggin wrote: > On Thu, 28 Jul 2016 16:07:17 -0700 > Andrey Smirnov wrote: > >> Call out to all restart handlers that were added via >> register_restart_handler() API when restarting the machine. >> >>

Re: [PATCH] sched: Avoid that __wait_on_bit_lock() hangs

On 08/08, Bart Van Assche wrote: > > No external modules were loaded when I triggered the lockup Heh. Could you test the patch below? Oleg. --- x/kernel/sched/wait.c +++ x/kernel/sched/wait.c @@ -283,7 +283,7 @@ void abort_exclusive_wait(wait_queue_hea if (!list_empty(>task_list))

[PATCH 2/4] ARM: dts: da850: Add an aemif node

Currently the davinci da8xx boards use the mach-davinci aemif code. Instantiating an aemif node into the DT allows to use the ti-aemif memory driver and is another step to better DT support. Also it will allow to properly pass the emif timings via DT. Signed-off-by: Karl Beldan

Re: [PATCH 2/9] remoteproc: core: Trivial: Improve error checking, spelling and debug prints

On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote: > Trivial patch to clean up a couple of minor misgivings. > > Signed-off-by: Lee Jones Acked-by: Bjorn Andersson Although as I hope to stack this series ontop of the auto-boot there will be some

Re: [PATCH v2] net: dsa: b53: constify b53_io_ops structures

On 08/09/2016 10:09 AM, Julia Lawall wrote: > The b53_io_ops structures are never modified, so declare them as const. > > Done with the help of Coccinelle. > > Signed-off-by: Julia Lawall Acked-by: Florian Fainelli -- Florian

RE: [PATCH] megaraid_sas: Fix probing cards without io port

> > that does not io port resource allocated from BIOS, and kernel can not > > assign one as io port shortage. > > > > The driver is only looking for MEM, and should not fail. > > > It turns out megasas_init_fw() etc are using bar index as mask. > > index 1 is used as mask 1, so that

Re: [PATCH 3/9] remoteproc: core: Remove pointless OOM print

On Tue, 09 Aug 2016, Bjorn Andersson wrote: > On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote: > > > These types of error prints are superfluous. The system will > > pick up on OOM issues and let the user know. > > > > Signed-off-by: Lee Jones > > Acked-by: Bjorn

Re: [PATCH 2/9] remoteproc: core: Trivial: Improve error checking, spelling and debug prints

On Tue, 09 Aug 2016, Bjorn Andersson wrote: > On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote: > > > Trivial patch to clean up a couple of minor misgivings. > > > > Signed-off-by: Lee Jones > > Acked-by: Bjorn Andersson You can just take it.

Re: [RFC][PATCH 0/3] tracing: Add Hardware Latency detector tracer

On Thu, 4 Aug 2016 11:30:33 -0400 Steven Rostedt wrote: > Note, I'm currently working on adding code to detect NMIs to this as > well. And perhaps even tracing SMI counters. Just to show what caused > the latency, as latency isn't measured by the counters (that I know of). >

Re: [PATCH] hwrng: core - Allow for multiple simultaneous active hwrng devices

Hi Keith, On Tue, Aug 09, 2016 at 10:58:05AM -0700, Keith Packard wrote: > Jason Cooper writes: > > Perhaps a /dev/hwrng[0-9] per rng? That would lend itself nicely to a > > sysfs interface for per device quality, rate, and enabled attributes. > > e.g.

[RFC 01/11] swap: Add swap_cluster_list

From: Huang Ying This is a code clean up patch without functionality changes. The swap_cluster_list data structure and its operations is introduced to provide some better encapsulation for free cluster and discard cluster list operations. This avoid some code duplication,

Re: [PATCH v2 00/10] usb: ulpi: remove "dev" field from struct ulpi_ops

On Tue, Aug 09, 2016 at 06:55:18PM +0300, Tal Shorer wrote: > On Tue, Aug 9, 2016 at 5:04 PM, Greg KH wrote: > > On Mon, Aug 01, 2016 at 09:15:48PM +0300, Tal Shorer wrote: > >> struct ulpi_ops is defined as follows: > >> > >> struct ulpi_ops { > >> struct

[PATCH V5 4/4] dts/imx6q-b850v3: Use GE B850v3 LVDS/DP++ Bridge

Configures the GE B850v3 LVDS/DP++ bridge on the dts file. Cc: Martyn Welch Cc: Martin Donnelly Cc: Javier Martinez Canillas Cc: Enric Balletbo i Serra Cc: Philipp Zabel

[PATCH v3 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization

Default implementation expects 6 pages maximum are needed for low page allocations. If KASLR memory randomization is enabled, the worse case of e820 layout would require 12 pages (no large pages). It is due to the PUD level randomization and the variable e820 memory layout. This bug was found

[PATCH v3 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization

Initialize KASLR memory randomization after max_pfn is initialized. Also ensure the size is rounded up. Could have create problems on machines with more than 1Tb of memory on certain random addresses. Fixes: 021182e52fe0 ("Enable KASLR for physical mapping memory regions") Signed-off-by: Thomas

Re: [PATCH] hwrng: core - Allow for multiple simultaneous active hwrng devices

Hi Keith, Herbert, On Tue, Aug 09, 2016 at 05:50:58PM +0800, Herbert Xu wrote: > On Mon, Jul 25, 2016 at 01:07:35PM -0700, Keith Packard wrote: > > Instead of having only one hwrng feeding /dev/random at a time, maintain > > a list of devices and cycle between them when filling the entropy pool.

Re: [PATCH 07/11] tools: Sync cpufeatures.h and vmx.h with the kernel

On Tue, Aug 09, 2016 at 01:01:30PM -0300, Arnaldo Carvalho de Melo wrote: > From: Arnaldo Carvalho de Melo > > There were changes related to the deprecation of the "pcommit" > instruction: > > fd1d961dd681 ("x86/insn: remove pcommit") > dfa169bbee00 ("Revert "KVM: x86: add

[PATCH v7 2/7] perf config: Add macros assigning key-value pairs to default_config_item

In near future, default_config_item arrays will be added (e.g. const struct default_config_item colors_config_items[]) To simply assign config key-value pairs to default_config_item, add macros that are CONF_VAR() and CONF_*_VAR() for each type. Cc: Namhyung Kim Cc: Jiri

[PATCH v7 5/7] perf config: Initialize ui_browser__colorsets with default config items

Set default config values for 'colors' section with 'colors_config_items[]' instead of actual const char * type values. (e.g. using colors_config_item[CONFIG_COLORS_TOP].value.s instead of "red, default" string value for 'colors.top') Cc: Namhyung Kim Cc: Jiri Olsa

RE: [RFC PATCH 2/3] net: macb: Add support for 1588 for Zynq Ultrascale+ MPSoC

Hi Nicolas, 1588 implementation in cadence GEM IP we have in Zynq Ultascale+ MPSoC is Different to the one in Zynq SOC. In earlier version, all timestamp values will be stored in registers and there is no specific Mechanism to distinguish the received ethernet frame that contains time stamp

Re: [PATCH] dm9000: Fix irq trigger type setup on non-dt platforms

Sylwester Nawrocki writes: > Commit b5a099c67a1c36b "net: ethernet: davicom: fix devicetree irq > resource" causes an interrupt storm after the ethernet interface > is activated on S3C24XX platform (ARM non-dt), due to the interrupt > trigger type not being set properly.

Re: [RFC 00/11] THP swap: Delay splitting THP during swapping out

Hi, All, "Huang, Ying" writes: > From: Huang Ying > > This patchset is based on 8/4 head of mmotm/master. > > This is the first step for Transparent Huge Page (THP) swap support. > The plan is to delaying splitting THP step by step and avoid

Re: [PATCH 1/9] remoteproc: core: Ensure error message is clear

On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote: > Before this patch, the dma_alloc_coherent() failure path printed out: > > "dma_alloc_coherent err: 16760832" > > ... alluding to the Linux error code being 16760832, but seeing as > Linux error codes are all negative, this looks like a

Re: [PATCH] net: dsa: b53: constify xfrm_replay structures

On Tue, 9 Aug 2016, Florian Fainelli wrote: > On 08/09/2016 09:58 AM, Julia Lawall wrote: > > The xfrm_replay structures are never modified, so declare them as const. > > You mean b53_io_ops here, right? Oops. I sent a v2. julia > Other than that LTGM, but this will > have to wait for

4.7.0: RCU stall in nf_conntrack

Hi, I just experienced network hangup with 4.7.0, it happened shortly after resume from hibernate: [201988.443552] INFO: rcu_preempt detected stalls on CPUs/tasks: [201988.443556] Tasks blocked on level-0 rcu_node (CPUs 0-3): P14563 [201988.443557] (detected by 3, t=18002

Re: [PATCH V3] printk: Create pr_ functions

On Tue, 2016-08-09 at 19:01 +0200, Geert Uytterhoeven wrote: > On Fri, Jun 24, 2016 at 5:46 AM, Joe Perches wrote: > > Using functions instead of macros can reduce overall code size > > by eliminating unnecessary "KERN_SOH" prefixes from > > format strings. > This change, commit

Re: [PATCH] hwrng: core - Allow for multiple simultaneous active hwrng devices

Jason Cooper writes: > Perhaps a /dev/hwrng[0-9] per rng? That would lend itself nicely to a > sysfs interface for per device quality, rate, and enabled attributes. > e.g. /sys/class/hw_random/hwrng0/{device/,quality,rate,enabled} I was interested in the data being

[RFC][PATCH 5/3] tracing: Add smi counting to HWLAT

If an arch supports counting of SMIs (like newer intel chips do), then it can implement arch_smi_count() to return the number of SMIs that were triggered. The hwlat detector will call this function to get the current number of SMIs, and then after a period, it will read that function again, and

[PATCH] xfrm: constify xfrm_replay structures

The xfrm_replay structures are never modified, so declare them as const. Done with the help of Coccinelle. Signed-off-by: Julia Lawall --- include/net/xfrm.h |2 +- net/xfrm/xfrm_replay.c |6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v5 2/5] fsnotify: Simplify inode iteration on umount

From: Jan Kara fsnotify_unmount_inodes() played complex tricks to pin next inode in the sb->s_inodes list when iterating over all inodes. If we switch to keeping current inode pinned somewhat longer, we can make the code much simpler and standard. Signed-off-by: Jan Kara

[PATCH v5 5/5] lib/dlock-list: Make sibling CPUs share the same linked list

The dlock list needs one list for each of the CPUs available. However, for sibling CPUs, they are sharing the L2 and probably L1 caches too. As a result, there is not much to gain in term of avoiding cacheline contention while increasing the cacheline footprint of the L1/L2 caches as separate

[PATCH v5 3/5] vfs: Remove unnecessary list_for_each_entry_safe() variants

From: Jan Kara evict_inodes() and invalidate_inodes() use list_for_each_entry_safe() to iterate sb->s_inodes list. However, since we use i_lru list entry for our local temporary list of inodes to destroy, the inode is guaranteed to stay in sb->s_inodes list while we hold

Re: [PATCH v4 3/3] pcie-designware: fix typo

Hi Joao, On Tue, Aug 09, 2016 at 05:35:34PM +0100, Joao Pinto wrote: > Simple fix typo. This patch actually does more than fix a typo. Not sure if you intended to split this into separate patches, or to write a better changelog for this one. If these code changes are related and we have a good

Re: [PATCH v2 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization

On Tue, Aug 09, 2016 at 09:35:54AM -0700, Thomas Garnier wrote: > Default implementation expects 6 pages maximum are needed for low page > allocations. If KASLR memory randomization is enabled, the worse case > of e820 layout would require 12 pages (no large pages). It is due to the > PUD level

[PATCH v5 4/5] vfs: Use dlock list for superblock's inode list

When many threads are trying to add or delete inode to or from a superblock's s_inodes list, spinlock contention on the list can become a performance bottleneck. This patch changes the s_inodes field to become a dlock list which is a distributed set of lists with per-list spinlocks. As a result,

[PATCH v5 0/5] vfs: Use dlock list for SB's s_inodes list

v4->v5: - Rebased the patch to 4.8-rc1 (changes to fs/fs-writeback.c was dropped). - Use kcalloc() instead of percpu_alloc() to allocate the dlock list heads structure as suggested by Christoph Lameter. - Replaced patch 5 by another one that made sibling CPUs use the same dlock list

[PATCH v4 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization

Default implementation expects 6 pages maximum are needed for low page allocations. If KASLR memory randomization is enabled, the worse case of e820 layout would require 12 pages (no large pages). It is due to the PUD level randomization and the variable e820 memory layout. This bug was found

[PATCH v4 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization

Initialize KASLR memory randomization after max_pfn is initialized. Also ensure the size is rounded up. It could have create problems on machines with more than 1Tb of memory on certain random addresses. Fixes: 021182e52fe0 ("Enable KASLR for physical mapping memory regions") Signed-off-by:

Re: [PATCH 2/2] powerpc/pseries: Dynamically increase RMA size

Paul Clarke [p...@us.ibm.com] wrote: > Only nits from me...(see below) Paul, I agree with your comments and fixed them. Here is the updated patch. --- >From f9e9e8460206bc3fa7eaa741b9a2bde22870b9e0 Mon Sep 17 00:00:00 2001 From: root Date: Thu, 4 Aug 2016 23:13:37

Re: [RFC][PATCH 4/3] tracing: Add NMI tracing in hwlat detector

On Fri, 5 Aug 2016 17:40:43 +0200 Sebastian Andrzej Siewior wrote: > > For x86, it has its own NMI safe sched_clock. I could make this "NMI" > > code depend on: > > > > #ifndef CONFIG_GENERIC_SCHED_CLOCK > > that would be nice. That would be disable approx $(git grep >

Re: [PATCH] net: dsa: b53: constify xfrm_replay structures

On 08/09/2016 09:58 AM, Julia Lawall wrote: > The xfrm_replay structures are never modified, so declare them as const. You mean b53_io_ops here, right? Other than that LTGM, but this will have to wait for "net"next to re_open since this is more of a cleanup than bugfix. Thanks! -- Florian

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On Mon, Aug 08, 2016 at 10:29:05AM -0400, David Long wrote: > On 08/08/2016 07:13 AM, Daniel Thompson wrote: > >On 04/08/16 05:47, David Long wrote: > >>From b451caa1adaf1d03e08a44b5dad3fca31cebd97a Mon Sep 17 00:00:00 2001 > >>From: "David A. Long" > >>Date: Thu, 4 Aug 2016

[RFC] dm-crypt: add ability to use keys from the kernel key retention service

The kernel key service is a generic way to store keys for the use of other subsystems. Currently there is no way to use kernel keys in dm-crypt. This patch aims to fix that. Instead of key userspace may pass a key description with preceding ':'. So message that constructs encryption mapping now

Re: [Patch v3 03/11] driver/edac/mpc85xx_edac: Drop setting/clearing RFXE bit in HID1

On 08/08/2016 11:56 PM, Borislav Petkov wrote: > On Tue, Aug 09, 2016 at 05:06:39AM +, york sun wrote: >> It is uncorrectable. DDR controller can only report the error. I don't >> believe EDAC driver can do more. For the same reason I said we can leave >> RXFE as is, even for e500v1 case (with

Re: [PATCH 3/9] remoteproc: core: Remove pointless OOM print

On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote: > These types of error prints are superfluous. The system will > pick up on OOM issues and let the user know. > > Signed-off-by: Lee Jones Acked-by: Bjorn Andersson Although, I think we should

Re: [PATCH v4 1/3] locking/mutex: Add waiter parameter to mutex_optimistic_spin()

On 08/08/2016 01:26 PM, Peter Zijlstra wrote: On Mon, Jul 18, 2016 at 04:39:24PM -0400, Waiman Long wrote: @@ -302,22 +306,42 @@ static inline bool mutex_try_to_acquire(struct mutex *lock) * * Returns true when the lock was taken, otherwise false, indicating * that we need to jump to

Re: [PATCH v7 4/4] nmi_backtrace: generate one-line reports for idle cpus

On 8/9/2016 6:37 AM, Lorenzo Pieralisi wrote: On Mon, Aug 08, 2016 at 05:48:28PM +0100, Mark Rutland wrote: Hi, [adding Lorenzo] On Mon, Aug 08, 2016 at 12:03:38PM -0400, Chris Metcalf wrote: When doing an nmi backtrace of many cores, most of which are idle, the output is a little

[v2 PATCH] clk: rockchip: mark rk3399 hdcp_noc and vio_noc as critical

Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With this modification, the aclk_vio_noc should be put into critical list, since it is required by VOP. And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc, pclk_hdcp_noc. Mark them as critical to avoid someone close

Re: [PATCH v7 4/4] nmi_backtrace: generate one-line reports for idle cpus

On 8/9/2016 8:43 AM, Petr Mladek wrote: On Mon 2016-08-08 12:03:38, Chris Metcalf wrote: When doing an nmi backtrace of many cores, most of which are idle, the output is a little overwhelming and very uninformative. Suppress messages for cpus that are idling when they are interrupted and just

Re: [PATCH v5 5/5] lib/dlock-list: Make sibling CPUs share the same linked list

Hi Waiman, [auto build test ERROR on linus/master] [also build test ERROR on v4.8-rc1 next-20160809] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Waiman-Long/vfs-Use-dlock-list-for-SB-s

Re: [PATCH 1/7] ima: on soft reboot, restore the measurement list

On Tue, 2016-08-09 at 10:19 -0300, Thiago Jung Bauermann wrote: > Am Dienstag, 09 August 2016, 09:01:13 schrieb Mimi Zohar: > > > > On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote: > > > > > > Mimi Zohar writes: > > > > > > > > diff --git

[PATCH v3 11/13] net: ethernet: ti: cpsw: move platform data and slaves info to cpsw_common

These data are common for net devs in dual_emac mode. No need to hold it for every priv instance, so move them under cpsw_common. Signed-off-by: Ivan Khoronzhuk --- drivers/net/ethernet/ti/cpsw.c | 265 + 1 file changed, 137

[PATCH v3 13/13] net: ethernet: ti: cpsw: move ale, cpts and drivers params under cpsw_common

The ale, cpts, version, rx_packet_max, bus_freq, interrupt pacing parameters are common per net device that uses the same h/w. So, move them to common driver structure. Signed-off-by: Ivan Khoronzhuk --- drivers/net/ethernet/ti/cpsw.c | 235

[PATCH v3 07/13] net: ethernet: ti: cpsw: replace pdev on dev

No need to hold pdev link when only dev is needed. This allows to simplify a bunch of cpsw->pdev->dev now and farther. Signed-off-by: Ivan Khoronzhuk --- drivers/net/ethernet/ti/cpsw.c | 65 ++ 1 file changed, 34 insertions(+),

[PATCH v3 10/13] net; ethernet: ti: cpsw: move irq stuff under cpsw_common

The irq data are common for net devs in dual_emac mode. So no need to hold these data in every priv struct, move them under cpsw_common. Also delete irq_num var, as after optimization it's not needed. Correct number of irqs to 2, as anyway, driver is using only 2, at least for now. Signed-off-by:

[PATCH v3 09/13] net: ethernet: ti: cpsw: move cpdma resources to cpsw_common

Every net device private struct holds links to shared cpdma resources. No need to save and every time synchronize these resources per net dev. So, move it to common driver struct. Signed-off-by: Ivan Khoronzhuk --- drivers/net/ethernet/ti/cpsw.c | 97

  1   2   3   4   5   6   7   8   9   10   >