[PATCH 17/56] staging/lustre: Get rid of lustre_fid typedef

From: Oleg Drokin Replace it with struct lu_fid Signed-off-by: Oleg Drokin --- .../lustre/lustre/include/lustre/lustre_idl.h | 2 +- .../lustre/lustre/include/lustre/lustre_user.h | 24 +++--- 2 files changed, 13

[PATCH 17/56] staging/lustre: Get rid of lustre_fid typedef

From: Oleg Drokin Replace it with struct lu_fid Signed-off-by: Oleg Drokin --- .../lustre/lustre/include/lustre/lustre_idl.h | 2 +- .../lustre/lustre/include/lustre/lustre_user.h | 24 +++--- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git

[PATCH 16/56] staging/lustre: Get rid of object update code

From: Oleg Drokin Object update was originally planned to be used for cross-server updates, so nothing to do with the client. The idea was later significantly reworked anyway so even wire structs should not be retained. This gets rid of update_cmd_t, UPDATE and

[PATCH 23/56] staging/lustre/llite: Get rid of se_stat_t typedef

From: Oleg Drokin Replace it with enum se_stat Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/statahead.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH 21/56] staging/lustre: Get rid of ldlm_ns_type_t typedef

From: Oleg Drokin Replace it with enum ldlm_ns_type Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre_dlm.h | 6 +++--- drivers/staging/lustre/lustre/ldlm/ldlm_lib.c | 2 +-

[PATCH 16/56] staging/lustre: Get rid of object update code

From: Oleg Drokin Object update was originally planned to be used for cross-server updates, so nothing to do with the client. The idea was later significantly reworked anyway so even wire structs should not be retained. This gets rid of update_cmd_t, UPDATE and UPDATE_REPLY rpc and

[PATCH 23/56] staging/lustre/llite: Get rid of se_stat_t typedef

From: Oleg Drokin Replace it with enum se_stat Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/statahead.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/staging/lustre/lustre/llite/statahead.c

[PATCH 21/56] staging/lustre: Get rid of ldlm_ns_type_t typedef

From: Oleg Drokin Replace it with enum ldlm_ns_type Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre_dlm.h | 6 +++--- drivers/staging/lustre/lustre/ldlm/ldlm_lib.c | 2 +- drivers/staging/lustre/lustre/ldlm/ldlm_resource.c | 4 ++-- 3 files changed, 6

[PATCH 13/56] staging/lustre: Get rid of llog_op_type typedef

From: Oleg Drokin Replace with enum llog_op_type Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre/lustre_idl.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 13/56] staging/lustre: Get rid of llog_op_type typedef

From: Oleg Drokin Replace with enum llog_op_type Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre/lustre_idl.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/lustre/lustre/include/lustre/lustre_idl.h

[PATCH 03/56] staging/lustre: Get rid of loc_flags_t typedef

From: Oleg Drokin Replace it with direct reference of enum loc_flags Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lu_object.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 03/56] staging/lustre: Get rid of loc_flags_t typedef

From: Oleg Drokin Replace it with direct reference of enum loc_flags Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lu_object.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/lustre/lustre/include/lu_object.h

[PATCH] irqchip/gicv3-its: Don't allow devices whose ID is outside range

We are not checking whether the requested device identifier fits into table or not. The ITS MAPD command fails if 'Device ID' is outside of device table range. Add a simple validation check to avoid MAPD failures since we are not handling ITS command errors. This change also helps to return an

[PATCH] irqchip/gicv3-its: Don't allow devices whose ID is outside range

We are not checking whether the requested device identifier fits into table or not. The ITS MAPD command fails if 'Device ID' is outside of device table range. Add a simple validation check to avoid MAPD failures since we are not handling ITS command errors. This change also helps to return an

Re: [PATCH v10 1/3] cpufreq: Add mechanism for registering utilization update callbacks

On 02/19/2016 02:35 PM, Rafael J. Wysocki wrote: >> The scheduler hooks for utilization-based cpufreq operation deserve a >> lot more debate I think. They could quite possibly have different >> requirements than hooks which are chosen just to guarantee periodic >> callbacks into sampling-based

Re: [PATCH v10 1/3] cpufreq: Add mechanism for registering utilization update callbacks

On 02/19/2016 02:35 PM, Rafael J. Wysocki wrote: >> The scheduler hooks for utilization-based cpufreq operation deserve a >> lot more debate I think. They could quite possibly have different >> requirements than hooks which are chosen just to guarantee periodic >> callbacks into sampling-based

[PATCH v8 2/7] powerpc/powernv: Add OPAL support for Nest PMU

Nest Counters can be configured via PORE Engine and OPAL provides an interface to start/stop it. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Anton Blanchard Cc: Daniel Axtens

[PATCH v8 3/7] powerpc/powernv: autoload nest unit driver module

Device tree parsing of nest units and events are separated from pmu code and are placed in powernv/ as "opal-nest.c". Makefile is updated to up pick the file. Code added to "opal.c" to create a platform device for the nest unit. Nest device module code with a probe function to get the nest

[PATCH v8 2/7] powerpc/powernv: Add OPAL support for Nest PMU

Nest Counters can be configured via PORE Engine and OPAL provides an interface to start/stop it. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Anton Blanchard Cc: Daniel Axtens Cc: Stephane Eranian Cc: Sukadev Bhattiprolu Signed-off-by: Madhavan Srinivasan ---

[PATCH v8 3/7] powerpc/powernv: autoload nest unit driver module

Device tree parsing of nest units and events are separated from pmu code and are placed in powernv/ as "opal-nest.c". Makefile is updated to up pick the file. Code added to "opal.c" to create a platform device for the nest unit. Nest device module code with a probe function to get the nest

[PATCH v8 5/7] powerpc/perf: Add event attribute and group to nest pmu

Device tree nest driver module parses the nest unit and its events. It pass the information to nest pmu code which is placed in perf/ as "nest-pmu.c". Inthis patch code added to create only event attributes and attribute groups for the nest pmu. Cc: Michael Ellerman Cc:

[PATCH v8 5/7] powerpc/perf: Add event attribute and group to nest pmu

Device tree nest driver module parses the nest unit and its events. It pass the information to nest pmu code which is placed in perf/ as "nest-pmu.c". Inthis patch code added to create only event attributes and attribute groups for the nest pmu. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt

[PATCH v8 1/7] powerpc/powernv: Data structure and macros definition

Create new header file "nest-pmu.h" to add the data structures and macros needed for the nest pmu support. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Anton Blanchard Cc: Daniel Axtens

[PATCH v8 0/7] powerpc/powernv: Nest Instrumentation support

This patchset enables Nest Instrumentation support on powerpc. POWER8 has per-chip Nest Intrumentation which provides various per-chip metrics like memory, powerbus, Xlink and Alink bandwidth. Nest Instrumentation provides an interface (via PORE Engine) to configure and move the nest counter data

Re: [PATCHSET] cgroup: misc fixes and cleanups

On 2016/2/23 7:05, Tejun Heo wrote: > Hello, > > This patchset contains the following six patches. The first one is a > fix but should be safe to route through for-4.6. The rest are misc > cleanups and improvements which don't cause notable behavior changes. > >

[PATCH v8 1/7] powerpc/powernv: Data structure and macros definition

Create new header file "nest-pmu.h" to add the data structures and macros needed for the nest pmu support. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Anton Blanchard Cc: Daniel Axtens Cc: Stephane Eranian Cc: Sukadev Bhattiprolu Signed-off-by: Madhavan

[PATCH v8 0/7] powerpc/powernv: Nest Instrumentation support

This patchset enables Nest Instrumentation support on powerpc. POWER8 has per-chip Nest Intrumentation which provides various per-chip metrics like memory, powerbus, Xlink and Alink bandwidth. Nest Instrumentation provides an interface (via PORE Engine) to configure and move the nest counter data

Re: [PATCHSET] cgroup: misc fixes and cleanups

On 2016/2/23 7:05, Tejun Heo wrote: > Hello, > > This patchset contains the following six patches. The first one is a > fix but should be safe to route through for-4.6. The rest are misc > cleanups and improvements which don't cause notable behavior changes. > >

[PATCH v8 4/7] powerpc/powernv: detect supported nest units and its events

Parse device tree to detect nest units. Traverse through each nest unit folder to find supported events and corresponding unit/scale files (if any). The nest unit event file from Device Tree will contain the offset in the reserved memory region to get the counter data for a given event. Kernel

[PATCH v8 4/7] powerpc/powernv: detect supported nest units and its events

Parse device tree to detect nest units. Traverse through each nest unit folder to find supported events and corresponding unit/scale files (if any). The nest unit event file from Device Tree will contain the offset in the reserved memory region to get the counter data for a given event. Kernel

[PATCH] lib/bug.c: use common WARN helper

The traceoff_on_warning option doesn't have any effect on s390, powerpc, arm64, parisc, and sh because there are two different types of WARN implementations: 1) The above mentioned architectures treat WARN() as a special case of a BUG() exception. They handle warnings in report_bug() in

[PATCH] lib/bug.c: use common WARN helper

The traceoff_on_warning option doesn't have any effect on s390, powerpc, arm64, parisc, and sh because there are two different types of WARN implementations: 1) The above mentioned architectures treat WARN() as a special case of a BUG() exception. They handle warnings in report_bug() in

[PATCH v5 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

Some Lenovo ideapad models lack a physical rfkill switch. On Lenovo models ideapad Y700 Touch-15ISK and ideapad Y700-15ISK, ideapad-laptop would wrongly report all radios as blocked by hardware which caused wireless network connections to fail. Add these models without an rfkill switch to the

[PATCH v5 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

Some Lenovo ideapad models lack a physical rfkill switch. On Lenovo models ideapad Y700 Touch-15ISK and ideapad Y700-15ISK, ideapad-laptop would wrongly report all radios as blocked by hardware which caused wireless network connections to fail. Add these models without an rfkill switch to the

[PATCH 03/12] cgroup: reorder operations in cgroup_mkdir()

Currently, operations to initialize internal objects and create interface directory and files are intermixed in cgroup_mkdir(). We're in the process of refactoring cgroup and css management paths to separate them out to eventually allow cgroups which aren't visible through cgroup fs. This patch

[PATCH 01/12] cgroup: separate out interface file creation from css creation

Currently, interface files are created when a css is created depending on whether @visible is set. This patch separates out the two into separate steps to help code refactoring and eventually allow cgroups which aren't visible through cgroup fs. Move css_populate_dir() out of create_css() and

[PATCH 03/12] cgroup: reorder operations in cgroup_mkdir()

Currently, operations to initialize internal objects and create interface directory and files are intermixed in cgroup_mkdir(). We're in the process of refactoring cgroup and css management paths to separate them out to eventually allow cgroups which aren't visible through cgroup fs. This patch

[PATCH 01/12] cgroup: separate out interface file creation from css creation

Currently, interface files are created when a css is created depending on whether @visible is set. This patch separates out the two into separate steps to help code refactoring and eventually allow cgroups which aren't visible through cgroup fs. Move css_populate_dir() out of create_css() and

[PATCH 02/12] cgroup: explicitly track whether a cgroup_subsys_state is visible to userland

Currently, whether a css (cgroup_subsys_state) has its interface files created is not tracked and assumed to change together with the owning cgroup's lifecycle. cgroup directory and interface creation is being separated out from internal object creation to help refactoring and eventually allow

[PATCHSET cgroup/for-4.6] cgroup: make control mask updates modular and recursive

Hello, Currently, subsystem enabling and disabling in the default hierarchy are implemented as a long chain of interdependent operations in cgroup_subtree_control_write(). The function calculates what need to be done to its children and excute the necessary operations. The function

[PATCH 05/12] cgroup: introduce cgroup_control() and cgroup_ss_mask()

When a controller is enabled and visible on a non-root cgroup is determined by subtree_control and subtree_ss_mask of the parent cgroup. For a root cgroup, by the type of the hierarchy and which controllers are attached to it. Deciding the above on each usage is fragile and unnecessarily

[PATCH 02/12] cgroup: explicitly track whether a cgroup_subsys_state is visible to userland

Currently, whether a css (cgroup_subsys_state) has its interface files created is not tracked and assumed to change together with the owning cgroup's lifecycle. cgroup directory and interface creation is being separated out from internal object creation to help refactoring and eventually allow

[PATCHSET cgroup/for-4.6] cgroup: make control mask updates modular and recursive

Hello, Currently, subsystem enabling and disabling in the default hierarchy are implemented as a long chain of interdependent operations in cgroup_subtree_control_write(). The function calculates what need to be done to its children and excute the necessary operations. The function

[PATCH 05/12] cgroup: introduce cgroup_control() and cgroup_ss_mask()

When a controller is enabled and visible on a non-root cgroup is determined by subtree_control and subtree_ss_mask of the parent cgroup. For a root cgroup, by the type of the hierarchy and which controllers are attached to it. Deciding the above on each usage is fragile and unnecessarily

[PATCH 12/12] cgroup: make cgroup_calc_subtree_ss_mask() take @this_ss_mask

cgroup_calc_subtree_ss_mask() currently takes @cgrp and @subtree_control. @cgrp is used for two purposes - to decide whether it's for default hierarchy and the mask of available subsystems. The former doesn't matter as the results are the same regardless. The latter can be specified directly

[PATCH 06/12] cgroup: factor out cgroup_drain_offline() from cgroup_subtree_control_write()

Factor out async css offline draining into cgroup_drain_offline(). * Nest subsystem walk inside child walk. The child walk will later be converted to subtree walk which is a bit more expensive. * Relocate the draining above subsystem mask preparation, which doesn't create any behavior

[PATCH 11/12] cgroup: Factor out cgroup_{apply|finalize}_control() from cgroup_subtree_control_write()

Factor out cgroup_{apply|finalize}_control() so that control mask update can be done in several simple steps. This patch doesn't introduce behavior changes. Signed-off-by: Tejun Heo --- kernel/cgroup.c | 81 + 1 file

[PATCH 12/12] cgroup: make cgroup_calc_subtree_ss_mask() take @this_ss_mask

cgroup_calc_subtree_ss_mask() currently takes @cgrp and @subtree_control. @cgrp is used for two purposes - to decide whether it's for default hierarchy and the mask of available subsystems. The former doesn't matter as the results are the same regardless. The latter can be specified directly

[PATCH 06/12] cgroup: factor out cgroup_drain_offline() from cgroup_subtree_control_write()

Factor out async css offline draining into cgroup_drain_offline(). * Nest subsystem walk inside child walk. The child walk will later be converted to subtree walk which is a bit more expensive. * Relocate the draining above subsystem mask preparation, which doesn't create any behavior

[PATCH 11/12] cgroup: Factor out cgroup_{apply|finalize}_control() from cgroup_subtree_control_write()

Factor out cgroup_{apply|finalize}_control() so that control mask update can be done in several simple steps. This patch doesn't introduce behavior changes. Signed-off-by: Tejun Heo --- kernel/cgroup.c | 81 + 1 file changed, 58

[PATCH 07/12] cgroup: factor out cgroup_apply_control_disable() from cgroup_subtree_control_write()

Factor out css disabling and hiding into cgroup_apply_control_disable(). * Nest subsystem walk inside child walk. The child walk will later be converted to subtree walk which is a bit more expensive. * Instead of operating on the differential masks @css_enable and @css_disable, simply

[PATCH v8 6/7] powerpc/perf: generic nest pmu event functions

Add set of generic nest pmu related event functions to be used by each nest pmu. Add code to setup format attribute and to register nest pmus. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Anton Blanchard

[PATCH v8 7/7] powerpc/perf: nest pmu cpumask and cpu hotplug support

Adds cpumask attribute to be used by each nest pmu since nest units are per-chip. Only one cpu (first online cpu) from each chip is designated to read counters. On cpu hotplug, dying cpu is checked to see whether it is one of the designated cpus, if yes, next online cpu from the same chip is

[PATCH 07/12] cgroup: factor out cgroup_apply_control_disable() from cgroup_subtree_control_write()

Factor out css disabling and hiding into cgroup_apply_control_disable(). * Nest subsystem walk inside child walk. The child walk will later be converted to subtree walk which is a bit more expensive. * Instead of operating on the differential masks @css_enable and @css_disable, simply

[PATCH v8 6/7] powerpc/perf: generic nest pmu event functions

Add set of generic nest pmu related event functions to be used by each nest pmu. Add code to setup format attribute and to register nest pmus. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Anton Blanchard Cc: Daniel Axtens Cc: Stephane Eranian Cc: Sukadev

[PATCH v8 7/7] powerpc/perf: nest pmu cpumask and cpu hotplug support

Adds cpumask attribute to be used by each nest pmu since nest units are per-chip. Only one cpu (first online cpu) from each chip is designated to read counters. On cpu hotplug, dying cpu is checked to see whether it is one of the designated cpus, if yes, next online cpu from the same chip is

[PATCH 08/12] cgroup: factor out cgroup_apply_control_enable() from cgroup_subtree_control_write()

Factor out css enabling and showing into cgroup_apply_control_enable(). * Nest subsystem walk inside child walk. The child walk will later be converted to subtree walk which is a bit more expensive. * Instead of operating on the differential masks @css_enable, simply enable or show csses

[PATCH 10/12] cgroup: introduce cgroup_{save|propagate|restore}_control()

While controllers are being enabled and disabled in cgroup_subtree_control_write(), the original subsystem masks are stashed in local variables so that they can be restored if the operation fails in the middle. This patch adds dedicated fields to struct cgroup to be used instead of the local

[PATCH 08/12] cgroup: factor out cgroup_apply_control_enable() from cgroup_subtree_control_write()

Factor out css enabling and showing into cgroup_apply_control_enable(). * Nest subsystem walk inside child walk. The child walk will later be converted to subtree walk which is a bit more expensive. * Instead of operating on the differential masks @css_enable, simply enable or show csses

[PATCH 10/12] cgroup: introduce cgroup_{save|propagate|restore}_control()

While controllers are being enabled and disabled in cgroup_subtree_control_write(), the original subsystem masks are stashed in local variables so that they can be restored if the operation fails in the middle. This patch adds dedicated fields to struct cgroup to be used instead of the local

[PATCH 09/12] cgroup: make cgroup_drain_offline() and cgroup_apply_control_{disable|enable}() recursive

The three factored out css management operations - cgroup_drain_offline() and cgroup_apply_control_{disable|enable}() - only depend on the current state of the target cgroups and idempotent and thus can be easily made to operate on the subtree instead of the immediate children. This patch

[PATCH 09/12] cgroup: make cgroup_drain_offline() and cgroup_apply_control_{disable|enable}() recursive

The three factored out css management operations - cgroup_drain_offline() and cgroup_apply_control_{disable|enable}() - only depend on the current state of the target cgroups and idempotent and thus can be easily made to operate on the subtree instead of the immediate children. This patch

[PATCH 04/12] cgroup: factor out cgroup_create() out of cgroup_mkdir()

We're in the process of refactoring cgroup and css management paths to separate them out to eventually allow cgroups which aren't visible through cgroup fs. This patch factors out cgroup_create() out of cgroup_mkdir(). cgroup_create() contains all internal object creation and initialization.

[PATCH 04/12] cgroup: factor out cgroup_create() out of cgroup_mkdir()

We're in the process of refactoring cgroup and css management paths to separate them out to eventually allow cgroups which aren't visible through cgroup fs. This patch factors out cgroup_create() out of cgroup_mkdir(). cgroup_create() contains all internal object creation and initialization.

Re: [PATCH V3 0/5] clk: support clocks which requires parent clock on during operation

oo. Regards Dong Aisheng > [0.00] [ cut here ] > [0.00] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3382 > lock_release+0x2f8/0x334() > [0.00] releasing a pinned lock > [0.00] Modules linked in: > [0.00] CPU: 0 PID: 0

Re: [PATCH V3 0/5] clk: support clocks which requires parent clock on during operation

here ] > [0.00] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3382 > lock_release+0x2f8/0x334() > [0.00] releasing a pinned lock > [0.00] Modules linked in: > [0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted > 4.5.0-rc5-next-201

Re: [PATCHSET] cgroup: misc fixes and cleanups

On Mon, Feb 22, 2016 at 06:05:43PM -0500, Tejun Heo wrote: > 0001-cgroup-fix-error-return-value-of-cgroup_addrm_files.patch > 0002-Revert-cgroup-add-cgroup_subsys-css_e_css_changed.patch > 0003-cgroup-s-child_subsys_mask-subtree_ss_mask.patch >

Re: [PATCHSET] cgroup: misc fixes and cleanups

On Mon, Feb 22, 2016 at 06:05:43PM -0500, Tejun Heo wrote: > 0001-cgroup-fix-error-return-value-of-cgroup_addrm_files.patch > 0002-Revert-cgroup-add-cgroup_subsys-css_e_css_changed.patch > 0003-cgroup-s-child_subsys_mask-subtree_ss_mask.patch >

[PATCH v2 6/6] cgroup: make cgroup subsystem masks u16

>From 6e5c830770f9045a17b1b931c3e11fbd5591e630 Mon Sep 17 00:00:00 2001 From: Tejun Heo Date: Mon, 22 Feb 2016 22:25:47 -0500 After the recent do_each_subsys_mask() conversion, there's no reason to use ulong for subsystem masks. We'll be adding more subsystem masks to

[PATCH v2 6/6] cgroup: make cgroup subsystem masks u16

>From 6e5c830770f9045a17b1b931c3e11fbd5591e630 Mon Sep 17 00:00:00 2001 From: Tejun Heo Date: Mon, 22 Feb 2016 22:25:47 -0500 After the recent do_each_subsys_mask() conversion, there's no reason to use ulong for subsystem masks. We'll be adding more subsystem masks to persistent data

Re: [PATCH v5] powerpc32: provide VIRT_CPU_ACCOUNTING

On Mon, 2016-02-22 at 20:15 -0600, Scott Wood wrote: > On Tue, 2016-02-23 at 13:04 +1100, Michael Ellerman wrote: > > On Tue, 2016-02-16 at 15:21 -0600, Scott Wood wrote: > > > On Thu, 2016-02-11 at 17:16 +0100, Christophe Leroy wrote: > > > > This patch provides VIRT_CPU_ACCOUTING to PPC32

Re: [PATCH v5] powerpc32: provide VIRT_CPU_ACCOUNTING

On Mon, 2016-02-22 at 20:15 -0600, Scott Wood wrote: > On Tue, 2016-02-23 at 13:04 +1100, Michael Ellerman wrote: > > On Tue, 2016-02-16 at 15:21 -0600, Scott Wood wrote: > > > On Thu, 2016-02-11 at 17:16 +0100, Christophe Leroy wrote: > > > > This patch provides VIRT_CPU_ACCOUTING to PPC32

Freezable workqueue blocks non-freezable workqueue during the system resume process

Hi Tejun Heo and Florian Mickler, I have a question that during the system resume process, the freezable workqueue can be thawed if there is a non-freezable workqueue is blocked (At uninterruptable state)? My case like below, I have a USB OTG (Micro-AB) cable is at USB Micro-B port, and there is

Freezable workqueue blocks non-freezable workqueue during the system resume process

Hi Tejun Heo and Florian Mickler, I have a question that during the system resume process, the freezable workqueue can be thawed if there is a non-freezable workqueue is blocked (At uninterruptable state)? My case like below, I have a USB OTG (Micro-AB) cable is at USB Micro-B port, and there is

Re: [PATCH] tracing: don't macro-expand arguments before stringification in TP_printk

On Wed, 16 Dec 2015 01:28:12 +0100 Rasmus Villemoes wrote: > Bah, just found 0462b5664b (ftrace: Output REC->var instead of > __entry->var for trace format). There's some magic here I don't > understand, but I'm wondering if '__entry' wouldn't do just as well as > 'REC'

Re: [PATCH] tracing: don't macro-expand arguments before stringification in TP_printk

On Wed, 16 Dec 2015 01:28:12 +0100 Rasmus Villemoes wrote: > Bah, just found 0462b5664b (ftrace: Output REC->var instead of > __entry->var for trace format). There's some magic here I don't > understand, but I'm wondering if '__entry' wouldn't do just as well as > 'REC' for the tools that try to

Re: [PATCH v2 4/4] dmaengine: pxa_dma: fix the maximum requestor line

On Mon, Feb 15, 2016 at 09:57:48PM +0100, Robert Jarzmik wrote: > The current number of requestor lines is limited to 31. This was an > error of a previous commit, as this number is platform dependent, and is > actually : > - for pxa25x: 40 requestor lines > - for pxa27x: 75 requestor lines > -

Re: [PATCH v2 4/4] dmaengine: pxa_dma: fix the maximum requestor line

On Mon, Feb 15, 2016 at 09:57:48PM +0100, Robert Jarzmik wrote: > The current number of requestor lines is limited to 31. This was an > error of a previous commit, as this number is platform dependent, and is > actually : > - for pxa25x: 40 requestor lines > - for pxa27x: 75 requestor lines > -

Re: [PATCH v2 4/4] dmaengine: xilinx_vdma: Improve channel idle checking

On Mon, Feb 22, 2016 at 11:24:37AM +0530, Kedareswara rao Appana wrote: > This patch improves the channel idle cheking by introduing ^ typo > a new varibale in chan private structure. ^^^ here too :( and there is no description how this

Re: [PATCH v2 4/4] dmaengine: xilinx_vdma: Improve channel idle checking

On Mon, Feb 22, 2016 at 11:24:37AM +0530, Kedareswara rao Appana wrote: > This patch improves the channel idle cheking by introduing ^ typo > a new varibale in chan private structure. ^^^ here too :( and there is no description how this

Re: [PATCH v2 2/4] dmaengine: xilinx_vdma: Simplify spin lock handling

On Mon, Feb 22, 2016 at 11:24:35AM +0530, Kedareswara rao Appana wrote: > This patch simplifies the spin lock handling in the driver. But sadly doesn't describe how? > > Signed-off-by: Kedareswara rao Appana > --- > Changes for v2: > ---> splitted the changes into multiple

Re: [PATCH v2 2/4] dmaengine: xilinx_vdma: Simplify spin lock handling

On Mon, Feb 22, 2016 at 11:24:35AM +0530, Kedareswara rao Appana wrote: > This patch simplifies the spin lock handling in the driver. But sadly doesn't describe how? > > Signed-off-by: Kedareswara rao Appana > --- > Changes for v2: > ---> splitted the changes into multiple patches. > >

Re: [PATCH v3 00/12] pwm: add support for atomic update

Mark, On Mon, Feb 22, 2016 at 1:24 PM, Mark Brown wrote: > On Mon, Feb 22, 2016 at 11:15:09AM -0800, Doug Anderson wrote: > >> Note that historically I remember that Linus Torvalds has stated that >> there is no stable API within the Linux kernel and that forcing the >>

Re: [PATCH v3 00/12] pwm: add support for atomic update

Mark, On Mon, Feb 22, 2016 at 1:24 PM, Mark Brown wrote: > On Mon, Feb 22, 2016 at 11:15:09AM -0800, Doug Anderson wrote: > >> Note that historically I remember that Linus Torvalds has stated that >> there is no stable API within the Linux kernel and that forcing the >> in-kernel API to never

Re: [PATCH v3 00/11] KVM: x86: track guest page access

+Kevin On 02/22/2016 06:05 PM, Xiao Guangrong wrote: > > On 02/19/2016 08:00 PM, Paolo Bonzini wrote: >> >> I still have a doubt: how are you going to handle invalidation of GPU >> shadow page tables if a device (emulated in QEMU or even vhost) does DMA >> to the PPGTT? > > I think Jike is the

Re: [PATCH v3 00/11] KVM: x86: track guest page access

+Kevin On 02/22/2016 06:05 PM, Xiao Guangrong wrote: > > On 02/19/2016 08:00 PM, Paolo Bonzini wrote: >> >> I still have a doubt: how are you going to handle invalidation of GPU >> shadow page tables if a device (emulated in QEMU or even vhost) does DMA >> to the PPGTT? > > I think Jike is the

Re: call_usermodehelper in containers

On Fri, 2016-02-19 at 13:14 +0800, Ian Kent wrote: > On Thu, 2016-02-18 at 14:45 -0600, Eric W. Biederman wrote: > > Ian Kent writes: > > > > > On Thu, 2016-02-18 at 14:36 +0800, Ian Kent wrote: > > > > On Thu, 2016-02-18 at 12:43 +0900, Kamezawa Hiroyuki wrote: > > > > > On

Re: call_usermodehelper in containers

On Fri, 2016-02-19 at 13:14 +0800, Ian Kent wrote: > On Thu, 2016-02-18 at 14:45 -0600, Eric W. Biederman wrote: > > Ian Kent writes: > > > > > On Thu, 2016-02-18 at 14:36 +0800, Ian Kent wrote: > > > > On Thu, 2016-02-18 at 12:43 +0900, Kamezawa Hiroyuki wrote: > > > > > On 2016/02/18 11:57,

Re: 4.4-final: 28 bioset threads on small notebook

On Tue, Feb 23, 2016 at 6:58 AM, Kent Overstreet wrote: > On Sun, Feb 21, 2016 at 05:40:59PM +0800, Ming Lei wrote: >> On Sun, Feb 21, 2016 at 2:43 PM, Ming Lin-SSI wrote: >> >>-Original Message- >> > >> > So it's almost already "per

Re: 4.4-final: 28 bioset threads on small notebook

On Tue, Feb 23, 2016 at 6:58 AM, Kent Overstreet wrote: > On Sun, Feb 21, 2016 at 05:40:59PM +0800, Ming Lei wrote: >> On Sun, Feb 21, 2016 at 2:43 PM, Ming Lin-SSI wrote: >> >>-Original Message- >> > >> > So it's almost already "per request_queue" >> >> Yes, that is because of the

Re: [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource

On Mon, Feb 22, 2016 at 6:38 PM, Christopher Hall wrote: > On Thu, 18 Feb 2016 13:11:33 -0800, Andy Lutomirski wrote: >>> >>> +#define X86_FEATURE_INVARIANT_TSC (7*32+4) /* Intel Invariant TSC */ > > > This is removed. It was basically an alias for

Re: [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource

On Mon, Feb 22, 2016 at 6:38 PM, Christopher Hall wrote: > On Thu, 18 Feb 2016 13:11:33 -0800, Andy Lutomirski wrote: >>> >>> +#define X86_FEATURE_INVARIANT_TSC (7*32+4) /* Intel Invariant TSC */ > > > This is removed. It was basically an alias for NONSTOP_TSC and not needed. > >> >>> +/* >>> +

RE: [RFC PATCH v3 3/3] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers

Hi Mark > -Original Message- > From: Gabriele Paoloni > Sent: 10 February 2016 22:45 > To: Mark Rutland > Cc: Guohanjun (Hanjun Guo); Wangzhou (B); liudongdong (C); Linuxarm; > qiujiang; bhelg...@google.com; a...@arndb.de; lorenzo.pieral...@arm.com; > t...@semihalf.com;

RE: [RFC PATCH v3 3/3] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers

Hi Mark > -Original Message- > From: Gabriele Paoloni > Sent: 10 February 2016 22:45 > To: Mark Rutland > Cc: Guohanjun (Hanjun Guo); Wangzhou (B); liudongdong (C); Linuxarm; > qiujiang; bhelg...@google.com; a...@arndb.de; lorenzo.pieral...@arm.com; > t...@semihalf.com;

Re: [PATCH] staging: rtl8723au: use list_first_entry*

Geliang Tang writes: > Use list_first_entry*() instead of container_of() to simplify the code. > > Signed-off-by: Geliang Tang > --- > drivers/staging/rtl8723au/core/rtw_recv.c | 49 > +-- >

Re: [PATCH] staging: rtl8723au: use list_first_entry*

Geliang Tang writes: > Use list_first_entry*() instead of container_of() to simplify the code. > > Signed-off-by: Geliang Tang > --- > drivers/staging/rtl8723au/core/rtw_recv.c | 49 > +-- > drivers/staging/rtl8723au/core/rtw_xmit.c | 26 +--- > 2 files

Re: [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource

On Thu, 18 Feb 2016 13:11:33 -0800, Andy Lutomirski wrote: +#define X86_FEATURE_INVARIANT_TSC (7*32+4) /* Intel Invariant TSC */ This is removed. It was basically an alias for NONSTOP_TSC and not needed. +/* + * Convert ART to TSC given numerator/denominator found in

Re: [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource

On Thu, 18 Feb 2016 13:11:33 -0800, Andy Lutomirski wrote: +#define X86_FEATURE_INVARIANT_TSC (7*32+4) /* Intel Invariant TSC */ This is removed. It was basically an alias for NONSTOP_TSC and not needed. +/* + * Convert ART to TSC given numerator/denominator found in detect_art() + */

RE: [PATCH] amdgpu: fix NULL pointer dereference at tonga_check_states_equal

Reviewed-by: Rex Zhu Best Regards Rex Zhu -Original Message- From: Bradley Pankow [mailto:btpan...@gmail.com] Sent: Tuesday, February 23, 2016 9:12 AM To: Deucher, Alexander; Zhu, Rex; Zhou, Jammy Cc: dri-de...@lists.freedesktop.org; linux-kernel@vger.kernel.org;

RE: [PATCH] amdgpu: fix NULL pointer dereference at tonga_check_states_equal

Reviewed-by: Rex Zhu Best Regards Rex Zhu -Original Message- From: Bradley Pankow [mailto:btpan...@gmail.com] Sent: Tuesday, February 23, 2016 9:12 AM To: Deucher, Alexander; Zhu, Rex; Zhou, Jammy Cc: dri-de...@lists.freedesktop.org; linux-kernel@vger.kernel.org; Bradley Pankow

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