[PATCH v3 11/14] nubus: Rename struct nubus_dev

It is misleading to call a functional resource a "device". In adopting the Linux Driver Model, the struct device will be embedded in struct nubus_board. That will compound the terminlogy problem because drivers will bind with boards, not with functional resources. Avoid this by renaming struct

[PATCH v3 11/14] nubus: Rename struct nubus_dev

It is misleading to call a functional resource a "device". In adopting the Linux Driver Model, the struct device will be embedded in struct nubus_board. That will compound the terminlogy problem because drivers will bind with boards, not with functional resources. Avoid this by renaming struct

Re: [PATCH v3 10/16] iommu: introduce device fault report API

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > Traditionally, device specific faults are detected and handled within > their own device drivers. When IOMMU is enabled, faults such as DMA > related transactions are detected by IOMMU. There is no generic > reporting mechanism to report faults back

Re: [PATCH v3 10/16] iommu: introduce device fault report API

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > Traditionally, device specific faults are detected and handled within > their own device drivers. When IOMMU is enabled, faults such as DMA > related transactions are detected by IOMMU. There is no generic > reporting mechanism to report faults back

[PATCH v3 06/14] nubus: Call proc_mkdir() not more than once per slot directory

This patch fixes the following WARNING. proc_dir_entry 'nubus/a' already registered Modules linked in: CPU: 0 PID: 1 Comm: swapper Tainted: GW 4.13.0-00036-gd57552077387 #1 Stack from 01c1bd9c: 01c1bd9c 003c2c8b 01c1bdc0 0001b0fe 00322f4a 01c43a20 01c43b0c

[PATCH v3 07/14] nubus: Remove redundant code

Eliminate unused values from struct nubus_dev to save wasted memory (a Radius PrecisionColor 24X card has about 95 functional resources and up to six such cards may be fitted). Also remove redundant static variable initialization, an unreachable !MACH_IS_MAC conditional, the unused

[PATCH v3 06/14] nubus: Call proc_mkdir() not more than once per slot directory

This patch fixes the following WARNING. proc_dir_entry 'nubus/a' already registered Modules linked in: CPU: 0 PID: 1 Comm: swapper Tainted: GW 4.13.0-00036-gd57552077387 #1 Stack from 01c1bd9c: 01c1bd9c 003c2c8b 01c1bdc0 0001b0fe 00322f4a 01c43a20 01c43b0c

[PATCH v3 07/14] nubus: Remove redundant code

Eliminate unused values from struct nubus_dev to save wasted memory (a Radius PrecisionColor 24X card has about 95 functional resources and up to six such cards may be fitted). Also remove redundant static variable initialization, an unreachable !MACH_IS_MAC conditional, the unused

[PATCH v3 12/14] nubus: Adopt standard linked list implementation

This increases code re-use and improves readability. Cc: Bartlomiej Zolnierkiewicz Signed-off-by: Finn Thain Tested-by: Stan Johnson --- drivers/net/ethernet/8390/mac8390.c | 7 +++--

[PATCH v3 05/14] nubus: Validate slot resource IDs

While we are here, include the slot number in the related error messages. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 25 +++-- 1 file changed, 19 insertions(+), 6 deletions(-) diff --git

[PATCH 1/2] KVM: MMU: Fix infinite loop when there is no available mmu page

From: Wanpeng Li The below test case can cause infinite loop in kvm when ept=0. #include #include #include #include #include #include #include long r[5]; int main() { r[2] = open("/dev/kvm", O_RDONLY);

[PATCH v3 12/14] nubus: Adopt standard linked list implementation

This increases code re-use and improves readability. Cc: Bartlomiej Zolnierkiewicz Signed-off-by: Finn Thain Tested-by: Stan Johnson --- drivers/net/ethernet/8390/mac8390.c | 7 +++-- drivers/net/ethernet/cirrus/mac89x0.c | 6 +++-- drivers/net/ethernet/natsemi/macsonic.c | 8 +++---

[PATCH v3 05/14] nubus: Validate slot resource IDs

While we are here, include the slot number in the related error messages. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 25 +++-- 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/drivers/nubus/nubus.c b/drivers/nubus/nubus.c

[PATCH 1/2] KVM: MMU: Fix infinite loop when there is no available mmu page

From: Wanpeng Li The below test case can cause infinite loop in kvm when ept=0. #include #include #include #include #include #include #include long r[5]; int main() { r[2] = open("/dev/kvm", O_RDONLY); r[3] = ioctl(r[2],

[PATCH 2/2] KVM: X86: Fix load RFLAGS w/o the fixed bit

From: Wanpeng Li *** Guest State *** CR0: actual=0x0030, shadow=0x6010, gh_mask=fff7 CR4: actual=0x2050, shadow=0x, gh_mask=e871 CR3 = 0xfffbc000 RSP = 0x RIP =

[PATCH 2/2] KVM: X86: Fix load RFLAGS w/o the fixed bit

From: Wanpeng Li *** Guest State *** CR0: actual=0x0030, shadow=0x6010, gh_mask=fff7 CR4: actual=0x2050, shadow=0x, gh_mask=e871 CR3 = 0xfffbc000 RSP = 0x RIP = 0x

[PATCH v3 13/14] nubus: Add expansion_type values for various Mac models

Add an expansion slot attribute to allow drivers to properly handle cards like Comm Slot cards and PDS cards without declaration ROMs. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- arch/m68k/include/asm/macintosh.h | 9 ++-

[PATCH v3 13/14] nubus: Add expansion_type values for various Mac models

Add an expansion slot attribute to allow drivers to properly handle cards like Comm Slot cards and PDS cards without declaration ROMs. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- arch/m68k/include/asm/macintosh.h | 9 ++- arch/m68k/mac/config.c | 110

[PATCH v3 14/14] nubus: Add support for the driver model

This patch brings basic support for the Linux Driver Model to the NuBus subsystem. For flexibility, the matching of boards with drivers is left up to the drivers. This is also the approach taken by NetBSD. A board may have many functions, and drivers may have to consider many functional resources

[PATCH v3 14/14] nubus: Add support for the driver model

This patch brings basic support for the Linux Driver Model to the NuBus subsystem. For flexibility, the matching of boards with drivers is left up to the drivers. This is also the approach taken by NetBSD. A board may have many functions, and drivers may have to consider many functional resources

[PATCH v3 03/14] nubus: Use static functions where possible

This fixes a couple of warnings from 'make W=1': drivers/nubus/nubus.c:790: warning: no previous prototype for 'nubus_probe_slot' drivers/nubus/nubus.c:824: warning: no previous prototype for 'nubus_scan_bus' Tested-by: Stan Johnson Signed-off-by: Finn Thain

[PATCH v3 01/14] nubus: Avoid array underflow and overflow

Check array indices. Avoid sprintf. Use buffers of sufficient size. Use appropriate types for array length parameters. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 29 +

[PATCH v3 03/14] nubus: Use static functions where possible

This fixes a couple of warnings from 'make W=1': drivers/nubus/nubus.c:790: warning: no previous prototype for 'nubus_probe_slot' drivers/nubus/nubus.c:824: warning: no previous prototype for 'nubus_scan_bus' Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 4 ++--

[PATCH v3 01/14] nubus: Avoid array underflow and overflow

Check array indices. Avoid sprintf. Use buffers of sufficient size. Use appropriate types for array length parameters. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 29 + drivers/nubus/proc.c | 12 ++-- include/linux/nubus.h

[PATCH v3 00/14] Modernization and fixes for NuBus subsystem

This series begins with cleanups and fixes for the NuBus subsystem and finishes with a patch to add support for the Linux Driver Model. The next series, which requires this one, modernizes the NuBus drivers. Changes since v1: - Added the missing NULL check in nubus_device_remove(). - Squashed the

[PATCH v3 02/14] nubus: Fix up header split

Due to the '#ifdef __KERNEL__' being located in the wrong place, some definitions from the kernel API were placed in the UAPI header during the scripted header split. Fix this. Also, remove the duplicate comment which is only relevant to the UAPI header. Fixes: 607ca46e97a1 ("UAPI: (Scripted)

[PATCH v3 02/14] nubus: Fix up header split

Due to the '#ifdef __KERNEL__' being located in the wrong place, some definitions from the kernel API were placed in the UAPI header during the scripted header split. Fix this. Also, remove the duplicate comment which is only relevant to the UAPI header. Fixes: 607ca46e97a1 ("UAPI: (Scripted)

[PATCH v3 00/14] Modernization and fixes for NuBus subsystem

This series begins with cleanups and fixes for the NuBus subsystem and finishes with a patch to add support for the Linux Driver Model. The next series, which requires this one, modernizes the NuBus drivers. Changes since v1: - Added the missing NULL check in nubus_device_remove(). - Squashed the

Re: [PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

On 12/5/2017 2:46 PM, Byungchul Park wrote: On 12/5/2017 2:30 PM, Matthew Wilcox wrote: On Mon, Dec 04, 2017 at 02:16:19PM +0900, Byungchul Park wrote: For now, wait_for_completion() / complete() works with lockdep, add lock_page() / unlock_page() and its family to lockdep support. Changes

Re: [PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

On 12/5/2017 2:46 PM, Byungchul Park wrote: On 12/5/2017 2:30 PM, Matthew Wilcox wrote: On Mon, Dec 04, 2017 at 02:16:19PM +0900, Byungchul Park wrote: For now, wait_for_completion() / complete() works with lockdep, add lock_page() / unlock_page() and its family to lockdep support. Changes

Re: Regression in e1000e since Kernel 4.14.3

On Tue, Dec 05, 2017 at 07:18:34AM +0100, Greg KH wrote: > On Tue, Dec 05, 2017 at 12:47:10AM +0100, Gabriel C wrote: > > On 04.12.2017 23:10, rwar...@gmx.de wrote: > > > > > Hallo > > > > > > someone and I got an regression with e1000e since kernel 4.14.3 and it > > > seems there is 4.14.4 on

Re: Regression in e1000e since Kernel 4.14.3

On Tue, Dec 05, 2017 at 07:18:34AM +0100, Greg KH wrote: > On Tue, Dec 05, 2017 at 12:47:10AM +0100, Gabriel C wrote: > > On 04.12.2017 23:10, rwar...@gmx.de wrote: > > > > > Hallo > > > > > > someone and I got an regression with e1000e since kernel 4.14.3 and it > > > seems there is 4.14.4 on

Re: PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)

On 2017-12-04 13:33 -0500, Nick Bowler wrote: > On 2017-12-04 10:04 +, Jose Abreu wrote: > > Hmmm, my first thought was that audio is being configured first > > because of the phy lock wait time, I've seen this happening before. > > > > Lets try this: > > - Disable all alsa clients (e.g.

Re: PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)

On 2017-12-04 13:33 -0500, Nick Bowler wrote: > On 2017-12-04 10:04 +, Jose Abreu wrote: > > Hmmm, my first thought was that audio is being configured first > > because of the phy lock wait time, I've seen this happening before. > > > > Lets try this: > > - Disable all alsa clients (e.g.

Re: Regression in e1000e since Kernel 4.14.3

On Tue, Dec 05, 2017 at 12:47:10AM +0100, Gabriel C wrote: > On 04.12.2017 23:10, rwar...@gmx.de wrote: > > > Hallo > > > > someone and I got an regression with e1000e since kernel 4.14.3 and it > > seems there is 4.14.4 on the way without a fix. > > > > > > bug report is here: > > > >

Re: Regression in e1000e since Kernel 4.14.3

On Tue, Dec 05, 2017 at 12:47:10AM +0100, Gabriel C wrote: > On 04.12.2017 23:10, rwar...@gmx.de wrote: > > > Hallo > > > > someone and I got an regression with e1000e since kernel 4.14.3 and it > > seems there is 4.14.4 on the way without a fix. > > > > > > bug report is here: > > > >

Re: [PATCH] thermal: tegra: delete unneeded of_node_put

On Mon, 4 Dec 2017, Eduardo Valentin wrote: > On Mon, Jul 17, 2017 at 04:42:38PM +0200, Julia Lawall wrote: > > > > > > On Mon, 17 Jul 2017, Jon Hunter wrote: > > > > > > > > On 15/07/17 09:42, Julia Lawall wrote: > > > > Device node iterators perform an of_node_put on each iteration, so > > >

Re: [PATCH] thermal: tegra: delete unneeded of_node_put

On Mon, 4 Dec 2017, Eduardo Valentin wrote: > On Mon, Jul 17, 2017 at 04:42:38PM +0200, Julia Lawall wrote: > > > > > > On Mon, 17 Jul 2017, Jon Hunter wrote: > > > > > > > > On 15/07/17 09:42, Julia Lawall wrote: > > > > Device node iterators perform an of_node_put on each iteration, so > > >

[PATCH v6 01/11] perf util: Define a structure for per-thread shadow stats

Perf has a set of static variables to record the runtime shadow metrics stats. While if we want to record the runtime shadow stats for per-thread, it will be the limitation. This patch creates a structure and the next patches will use this structure to update the runtime shadow stats for

[PATCH v6 04/11] perf util: Update per-thread shadow stats

The functions perf_stat__update_shadow_stats() is called to update the shadow stats on a set of static variables. But the static variables are the limitations to be extended to support per-thread shadow stats. This patch lets the perf_stat__update_shadow_stats() support to update the shadow

[PATCH v6 01/11] perf util: Define a structure for per-thread shadow stats

Perf has a set of static variables to record the runtime shadow metrics stats. While if we want to record the runtime shadow stats for per-thread, it will be the limitation. This patch creates a structure and the next patches will use this structure to update the runtime shadow stats for

[PATCH v6 04/11] perf util: Update per-thread shadow stats

The functions perf_stat__update_shadow_stats() is called to update the shadow stats on a set of static variables. But the static variables are the limitations to be extended to support per-thread shadow stats. This patch lets the perf_stat__update_shadow_stats() support to update the shadow

[PATCH v6 02/11] perf stat: Extend rbtree to support per-thread shadow stats

Previously the rbtree was used to link generic metrics. This patches adds new ctx/type/stat into rbtree keys because we will use this rbtree to maintain shadow metrics to replace original a couple of static arrays for supporting per-thread shadow stats. Signed-off-by: Jin Yao

[PATCH v6 05/11] perf util: Print per-thread shadow stats

The function perf_stat__print_shadow_statss() is called to print the shadow stats on a set of static variables. But the static variables are the limitations to support per-thread shadow stats. This patch lets the perf_stat__print_shadow_stats() support to print the shadow stats from a input

[PATCH v6 06/11] perf util: Remove a set of shadow stats static variables

In previous patches, we have reconstructed the code and let it not access the static variables directly. This patch removes these static variables. Signed-off-by: Jin Yao --- tools/perf/util/stat-shadow.c | 68 ++-

[PATCH v6 02/11] perf stat: Extend rbtree to support per-thread shadow stats

Previously the rbtree was used to link generic metrics. This patches adds new ctx/type/stat into rbtree keys because we will use this rbtree to maintain shadow metrics to replace original a couple of static arrays for supporting per-thread shadow stats. Signed-off-by: Jin Yao ---

[PATCH v6 05/11] perf util: Print per-thread shadow stats

The function perf_stat__print_shadow_statss() is called to print the shadow stats on a set of static variables. But the static variables are the limitations to support per-thread shadow stats. This patch lets the perf_stat__print_shadow_stats() support to print the shadow stats from a input

[PATCH v6 06/11] perf util: Remove a set of shadow stats static variables

In previous patches, we have reconstructed the code and let it not access the static variables directly. This patch removes these static variables. Signed-off-by: Jin Yao --- tools/perf/util/stat-shadow.c | 68 ++- tools/perf/util/stat.h| 1 + 2

[PATCH v6 09/11] perf util: Enumerate all threads from /proc

This patch calls thread_map__new_all_cpus() to enumerate all threads from /proc if per-thread flag is enabled. Signed-off-by: Jin Yao --- tools/perf/tests/thread-map.c | 2 +- tools/perf/util/evlist.c | 3 ++- tools/perf/util/thread_map.c | 5 -

[PATCH v6 03/11] perf util: Create the runtime_stat init/exit function

It mainly initializes and releases the rblist which is defined in struct runtime_stat. For the original rblist 'runtime_saved_values', it's still kept there for keeping the patch bisectable. The rblist 'runtime_saved_values' will be removed in later patch at switching time. Signed-off-by: Jin

[PATCH v6 09/11] perf util: Enumerate all threads from /proc

This patch calls thread_map__new_all_cpus() to enumerate all threads from /proc if per-thread flag is enabled. Signed-off-by: Jin Yao --- tools/perf/tests/thread-map.c | 2 +- tools/perf/util/evlist.c | 3 ++- tools/perf/util/thread_map.c | 5 - tools/perf/util/thread_map.h | 2 +- 4

[PATCH v6 03/11] perf util: Create the runtime_stat init/exit function

It mainly initializes and releases the rblist which is defined in struct runtime_stat. For the original rblist 'runtime_saved_values', it's still kept there for keeping the patch bisectable. The rblist 'runtime_saved_values' will be removed in later patch at switching time. Signed-off-by: Jin

[PATCH v6 00/11] perf stat: Enable '--per-thread' on all thread

v6: --- Update according to Arnaldo's comments. 1. In 'perf util: Define a structure for runtime shadow stats' Remove '#include "evsel.h"' 2. In 'perf stat: Extend rbtree to support per-thread shadow stats' Change patch subject to 'perf stat: Extend rbtree to support per-thread shadow stats'.

[PATCH v6 11/11] perf stat: Resort '--per-thread' result

There are many threads reported if we enable '--per-thread' globally. 1. Most of the threads are not counted or counting value 0. This patch removes these threads. 2. We also resort the threads in display according to the counting value. It's useful for user to see the hottest threads easily.

[PATCH v6 08/11] perf stat: Update or print per-thread stats

If the stats pointer in stat_config structure is not null, it will update the per-thread stats or print the per-thread stats on this buffer. Signed-off-by: Jin Yao --- tools/perf/builtin-stat.c | 9 +++-- tools/perf/util/stat.c| 11 --- 2 files changed,

[PATCH v6 00/11] perf stat: Enable '--per-thread' on all thread

v6: --- Update according to Arnaldo's comments. 1. In 'perf util: Define a structure for runtime shadow stats' Remove '#include "evsel.h"' 2. In 'perf stat: Extend rbtree to support per-thread shadow stats' Change patch subject to 'perf stat: Extend rbtree to support per-thread shadow stats'.

[PATCH v6 11/11] perf stat: Resort '--per-thread' result

There are many threads reported if we enable '--per-thread' globally. 1. Most of the threads are not counted or counting value 0. This patch removes these threads. 2. We also resort the threads in display according to the counting value. It's useful for user to see the hottest threads easily.

[PATCH v6 08/11] perf stat: Update or print per-thread stats

If the stats pointer in stat_config structure is not null, it will update the per-thread stats or print the per-thread stats on this buffer. Signed-off-by: Jin Yao --- tools/perf/builtin-stat.c | 9 +++-- tools/perf/util/stat.c| 11 --- 2 files changed, 15 insertions(+), 5

[PATCH v6 10/11] perf stat: Remove --per-thread pid/tid limitation

Currently, if we execute 'perf stat --per-thread' without specifying pid/tid, perf will return error. root@skl:/tmp# perf stat --per-thread The --per-thread option is only available when monitoring via -p -t options. -p, --pidstat events on existing process id -t, --tid

[PATCH v6 07/11] perf stat: Allocate shadow stats buffer for threads

After perf_evlist__create_maps() being executed, we can get all threads from /proc. And via thread_map__nr(), we can also get the number of threads. With the number of threads, the patch allocates a buffer which will record the shadow stats for these threads. The buffer pointer is saved in

[PATCH v6 10/11] perf stat: Remove --per-thread pid/tid limitation

Currently, if we execute 'perf stat --per-thread' without specifying pid/tid, perf will return error. root@skl:/tmp# perf stat --per-thread The --per-thread option is only available when monitoring via -p -t options. -p, --pidstat events on existing process id -t, --tid

[PATCH v6 07/11] perf stat: Allocate shadow stats buffer for threads

After perf_evlist__create_maps() being executed, we can get all threads from /proc. And via thread_map__nr(), we can also get the number of threads. With the number of threads, the patch allocates a buffer which will record the shadow stats for these threads. The buffer pointer is saved in

Re: [PATCH 1/1] mm/page_owner: ignore everything below the IRQ entry point

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on mmotm/master] [also build test ERROR on v4.15-rc2 next-20171204] [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

Re: [PATCH 1/1] mm/page_owner: ignore everything below the IRQ entry point

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on mmotm/master] [also build test ERROR on v4.15-rc2 next-20171204] [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

Re: [PATCH v10 3/6] clk: qcom: Add A53 PLL support

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: > The CPUs on Qualcomm MSM8916-based platforms are clocked by two PLLs, > a primary (A53) CPU PLL and a secondary fixed-rate GPLL0. These sources > are connected to a mux and half-integer divider, which is feeding the > CPU cores. > > This patch

Re: [PATCH v10 3/6] clk: qcom: Add A53 PLL support

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: > The CPUs on Qualcomm MSM8916-based platforms are clocked by two PLLs, > a primary (A53) CPU PLL and a secondary fixed-rate GPLL0. These sources > are connected to a mux and half-integer divider, which is feeding the > CPU cores. > > This patch

Re: [PATCH v10 2/6] mailbox: qcom: Create APCS child device for clock controller

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: > There is a clock controller functionality provided by the APCS hardware > block of msm8916 devices. The device-tree would represent an APCS node > with both mailbox and clock provider properties. > Create a platform child device for the clock

Re: [PATCH v10 2/6] mailbox: qcom: Create APCS child device for clock controller

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: > There is a clock controller functionality provided by the APCS hardware > block of msm8916 devices. The device-tree would represent an APCS node > with both mailbox and clock provider properties. > Create a platform child device for the clock

Re: [PATCH v10 6/6] clk: qcom: Add APCS clock controller support

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: [..] > diff --git a/drivers/clk/qcom/apcs-msm8916.c b/drivers/clk/qcom/apcs-msm8916.c > new file mode 100644 > index ..f71039ff2347 > --- /dev/null > +++ b/drivers/clk/qcom/apcs-msm8916.c > @@ -0,0 +1,149 @@ > +/* > + * Qualcomm APCS

Re: [PATCH v10 6/6] clk: qcom: Add APCS clock controller support

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: [..] > diff --git a/drivers/clk/qcom/apcs-msm8916.c b/drivers/clk/qcom/apcs-msm8916.c > new file mode 100644 > index ..f71039ff2347 > --- /dev/null > +++ b/drivers/clk/qcom/apcs-msm8916.c > @@ -0,0 +1,149 @@ > +/* > + * Qualcomm APCS

Re: [LKP] [lkp-robot] [fs/locks] 52306e882f: stress-ng.lockofd.ops_per_sec -11% regression

On Wed, Nov 08, 2017 at 03:22:33PM +0800, Aaron Lu wrote: > On Thu, Sep 28, 2017 at 04:02:23PM +0800, kernel test robot wrote: > > > > Greeting, > > > > FYI, we noticed a -11% regression of stress-ng.lockofd.ops_per_sec due to > > commit: > > > > > > commit:

Re: [LKP] [lkp-robot] [fs/locks] 52306e882f: stress-ng.lockofd.ops_per_sec -11% regression

On Wed, Nov 08, 2017 at 03:22:33PM +0800, Aaron Lu wrote: > On Thu, Sep 28, 2017 at 04:02:23PM +0800, kernel test robot wrote: > > > > Greeting, > > > > FYI, we noticed a -11% regression of stress-ng.lockofd.ops_per_sec due to > > commit: > > > > > > commit:

[PATCHv2 2/2] mtd: m25p80: restore the status of SPI flash when stop using it

From: Hou Zhiqiang Implement .shutdown function to restore the status in reboot process, and add the same operation to the .remove function. Signed-off-by: Hou Zhiqiang --- V2: - Changed code format slightly. drivers/mtd/devices/m25p80.c | 9

[PATCHv2 2/2] mtd: m25p80: restore the status of SPI flash when stop using it

From: Hou Zhiqiang Implement .shutdown function to restore the status in reboot process, and add the same operation to the .remove function. Signed-off-by: Hou Zhiqiang --- V2: - Changed code format slightly. drivers/mtd/devices/m25p80.c | 9 + 1 file changed, 9 insertions(+) diff

[PATCHv2 1/2] mtd: spi-nor: add an API to restore the status of SPI flash chip

From: Hou Zhiqiang Add this API to restore the status of SPI flash chip to the default such as addressing mode, whenever detach the driver from device or reboot the system. Signed-off-by: Hou Zhiqiang --- V2: - Changed the API name and added the

[PATCHv2 1/2] mtd: spi-nor: add an API to restore the status of SPI flash chip

From: Hou Zhiqiang Add this API to restore the status of SPI flash chip to the default such as addressing mode, whenever detach the driver from device or reboot the system. Signed-off-by: Hou Zhiqiang --- V2: - Changed the API name and added the comments and kernel document for it. - Export

[PATCHv2 0/2] mtd: m25p80: restore the addressing mode when stop using the flash

From: Hou Zhiqiang To be compatible with legacy device, reset the addressing mode to the default mode. Such as Freescale eSPI boot, it copies the images from SPI flash without firing a reset signal previously, so the reboot command will fail without reseting the addressing

[PATCHv2 0/2] mtd: m25p80: restore the addressing mode when stop using the flash

From: Hou Zhiqiang To be compatible with legacy device, reset the addressing mode to the default mode. Such as Freescale eSPI boot, it copies the images from SPI flash without firing a reset signal previously, so the reboot command will fail without reseting the addressing mode of SPI flash.

Re: [PATCH v10 5/6] dt-bindings: mailbox: qcom: Document the APCS clock binding

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: > Update the binding documentation for APCS to mention that the APCS > hardware block also expose a clock controller functionality. > > The APCS clock controller is a mux and half-integer divider. It has the > main CPU PLL as an input and

Re: [PATCH v10 5/6] dt-bindings: mailbox: qcom: Document the APCS clock binding

On Fri 01 Dec 09:02 PST 2017, Georgi Djakov wrote: > Update the binding documentation for APCS to mention that the APCS > hardware block also expose a clock controller functionality. > > The APCS clock controller is a mux and half-integer divider. It has the > main CPU PLL as an input and

Re: [PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

On 12/5/2017 2:30 PM, Matthew Wilcox wrote: On Mon, Dec 04, 2017 at 02:16:19PM +0900, Byungchul Park wrote: For now, wait_for_completion() / complete() works with lockdep, add lock_page() / unlock_page() and its family to lockdep support. Changes from v1 - Move lockdep_map_cross outside of

Re: [PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

On 12/5/2017 2:30 PM, Matthew Wilcox wrote: On Mon, Dec 04, 2017 at 02:16:19PM +0900, Byungchul Park wrote: For now, wait_for_completion() / complete() works with lockdep, add lock_page() / unlock_page() and its family to lockdep support. Changes from v1 - Move lockdep_map_cross outside of

Re: [PATCH v3 07/16] iommu/vt-d: assign PFSID in device TLB invalidation

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > When SRIOV VF device IOTLB is invalidated, we need to provide > the PF source SID such that IOMMU hardware can gauge the depth > of invalidation queue which is shared among VFs. This is needed > when device invalidation throttle (DIT) capability is

Re: [PATCH v3 07/16] iommu/vt-d: assign PFSID in device TLB invalidation

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > When SRIOV VF device IOTLB is invalidated, we need to provide > the PF source SID such that IOMMU hardware can gauge the depth > of invalidation queue which is shared among VFs. This is needed > when device invalidation throttle (DIT) capability is

Re: [PATCH v3 06/16] iommu/vt-d: add svm/sva invalidate function

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > This patch adds Intel VT-d specific function to implement > iommu passdown invalidate API for shared virtual address. > > The use case is for supporting caching structure invalidation > of assigned SVM capable devices. Emulated IOMMU exposes queue >

Re: [PATCH v3 06/16] iommu/vt-d: add svm/sva invalidate function

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > This patch adds Intel VT-d specific function to implement > iommu passdown invalidate API for shared virtual address. > > The use case is for supporting caching structure invalidation > of assigned SVM capable devices. Emulated IOMMU exposes queue >

Re: [PATCH] cpufreq: powernv: Define methods to parse positive & negative pstates

On 30-11-17, 10:13, Shilpasri G Bhat wrote: > From: "Gautham R. Shenoy" > > Pstates are 8bit values but on POWER8 they are negative and on POWER9 > they are positive. This patch adds helper routines to differentiate > the sign to read the correct pstate value. > >

Re: [PATCH] cpufreq: powernv: Define methods to parse positive & negative pstates

On 30-11-17, 10:13, Shilpasri G Bhat wrote: > From: "Gautham R. Shenoy" > > Pstates are 8bit values but on POWER8 they are negative and on POWER9 > they are positive. This patch adds helper routines to differentiate > the sign to read the correct pstate value. > > Signed-off-by: Gautham R.

Re: [PATCH 1/1] mm/page_owner: ignore everything below the IRQ entry point

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on mmotm/master] [also build test ERROR on v4.15-rc2 next-20171204] [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

Re: [PATCH 1/1] mm/page_owner: ignore everything below the IRQ entry point

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on mmotm/master] [also build test ERROR on v4.15-rc2 next-20171204] [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

Re: [PATCH V1 4/4] qcom: spmi-wled: Add auto-calibration logic support

On Thu 16 Nov 04:18 PST 2017, Kiran Gunda wrote: > The auto-calibration algorithm checks if the current WLED sink > configuration is valid. It tries enabling every sink and checks > if the OVP fault is observed. Based on this information it > detects and enables the valid sink configuration. Auto

Re: [PATCH V1 4/4] qcom: spmi-wled: Add auto-calibration logic support

On Thu 16 Nov 04:18 PST 2017, Kiran Gunda wrote: > The auto-calibration algorithm checks if the current WLED sink > configuration is valid. It tries enabling every sink and checks > if the OVP fault is observed. Based on this information it > detects and enables the valid sink configuration. Auto

[PATCH V2 3/4] cpu_cooling: Keep only one of_cpufreq*cooling_register() helper

of_cpufreq_cooling_register() isn't used by anyone and so can be removed, but then we would be left with two routines: cpufreq_cooling_register() and of_cpufreq_power_cooling_register() that would look odd. Remove current implementation of of_cpufreq_cooling_register() and rename

[PATCH V2 1/4] cpu_cooling: Make of_cpufreq_power_cooling_register() parse DT

All the callers of of_cpufreq_power_cooling_register() have almost identical code and it makes more sense to move that code into the helper as its all about reading DT properties. This got rid of lot of redundant code. Acked-by: Eduardo Valentin Signed-off-by: Viresh Kumar

[PATCH V2 4/4] cpu_cooling: Drop static-power related stuff

No one has used it for the last two and half years (since it was introduced by commit c36cf0717631 ("thermal: cpu_cooling: implement the power cooling device API")), get rid of it. Cc: Javi Merino Cc: Punit Agrawal Acked-by: Eduardo Valentin

[PATCH V2 3/4] cpu_cooling: Keep only one of_cpufreq*cooling_register() helper

of_cpufreq_cooling_register() isn't used by anyone and so can be removed, but then we would be left with two routines: cpufreq_cooling_register() and of_cpufreq_power_cooling_register() that would look odd. Remove current implementation of of_cpufreq_cooling_register() and rename

[PATCH V2 1/4] cpu_cooling: Make of_cpufreq_power_cooling_register() parse DT

All the callers of of_cpufreq_power_cooling_register() have almost identical code and it makes more sense to move that code into the helper as its all about reading DT properties. This got rid of lot of redundant code. Acked-by: Eduardo Valentin Signed-off-by: Viresh Kumar ---

[PATCH V2 4/4] cpu_cooling: Drop static-power related stuff

No one has used it for the last two and half years (since it was introduced by commit c36cf0717631 ("thermal: cpu_cooling: implement the power cooling device API")), get rid of it. Cc: Javi Merino Cc: Punit Agrawal Acked-by: Eduardo Valentin Signed-off-by: Viresh Kumar ---

[PATCH V2 0/4] cpu_cooling: cooling dev registration cleanups

Hi, This cleans up the helpers exposed by cpu_cooling driver and its users and removes a lot of code (around 280 lines effectively). Lots of unused code is removed. Tested on Hikey6220 and based over pm/linux-next. V1->V2: - Fixed a compilation warning when CONFIG_CPU_THERMAL isn't selected.

[PATCH V2 2/4] cpu_cooling: Remove unused cpufreq_power_cooling_register()

It isn't used by anyone, drop it. Acked-by: Eduardo Valentin Signed-off-by: Viresh Kumar --- Documentation/thermal/cpu-cooling-api.txt | 24 +++- drivers/thermal/cpu_cooling.c | 30 --

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