Hi Agustin,
On 29/11/16 22:57, Agustin Vega-Frias wrote:
> Driver for interrupt combiners in the Top-level Control and Status
> Registers (TCSR) hardware block in Qualcomm Technologies chips.
>
> An interrupt combiner in this block combines a set of interrupts by
> OR'ing the individual
Hi Agustin,
On 29/11/16 22:57, Agustin Vega-Frias wrote:
> Driver for interrupt combiners in the Top-level Control and Status
> Registers (TCSR) hardware block in Qualcomm Technologies chips.
>
> An interrupt combiner in this block combines a set of interrupts by
> OR'ing the individual
On Sun, Nov 27, 2016 at 05:37:04AM +0200, Michael S. Tsirkin wrote:
> On Fri, Nov 25, 2016 at 08:25:38AM +0100, Christoph Hellwig wrote:
> > Btw, what's the best way to get any response to this series?
> > But this and the predecessor seem to have completly fallen on deaf
> > ears.
>
> I'm sorry,
On Sun, Nov 27, 2016 at 05:37:04AM +0200, Michael S. Tsirkin wrote:
> On Fri, Nov 25, 2016 at 08:25:38AM +0100, Christoph Hellwig wrote:
> > Btw, what's the best way to get any response to this series?
> > But this and the predecessor seem to have completly fallen on deaf
> > ears.
>
> I'm sorry,
From: Alexandru Gagniuc
Date: Tue, 6 Dec 2016 10:56:51 -0800
> Support for setting the RGMII_IDMODE bit was added in the commit
> referenced below. However, that commit did not add the symmetrical
> clearing of the bit by way of setting it in "mask". Add it here.
>
> Note
From: Alexandru Gagniuc
Date: Tue, 6 Dec 2016 10:56:51 -0800
> Support for setting the RGMII_IDMODE bit was added in the commit
> referenced below. However, that commit did not add the symmetrical
> clearing of the bit by way of setting it in "mask". Add it here.
>
> Note that the
From: Niklas Cassel
Date: Tue, 6 Dec 2016 14:47:15 +0100
> From: Niklas Cassel
>
> From what I can tell, spin_lock(>lock) is not needed, since the
> phy_ethtool_ksettings_set call is not given the priv struct.
>
> phy_start_aneg takes the
From: Niklas Cassel
Date: Tue, 6 Dec 2016 14:47:15 +0100
> From: Niklas Cassel
>
> From what I can tell, spin_lock(>lock) is not needed, since the
> phy_ethtool_ksettings_set call is not given the priv struct.
>
> phy_start_aneg takes the phydev->lock. Calls to phy_adjust_link
> from
- The functions related to I2C master mode of operation were moved
to a single file: i2c-designware-master.c
- Common functions were moved into i2c-designware-common.c
- Common definitions were moved into i2c-designware-core.h (were in core.c)
Signed-off-by: Luis Oliveira
- The functions related to I2C master mode of operation were moved
to a single file: i2c-designware-master.c
- Common functions were moved into i2c-designware-common.c
- Common definitions were moved into i2c-designware-core.h (were in core.c)
Signed-off-by: Luis Oliveira
---
Changes V3->V4:
On Wed, Dec 07, 2016 at 01:52:17PM +, Mark Rutland wrote:
> Hi all
>
> Jeremy noticed a kernel lockup on arm64 when the perf tool was used in
> parallel with hotplug, which I've reproduced on arm64 and x86(-64) with
> v4.9-rc8. In both cases I'm using defconfig; I've tried enabling lockdep
>
On Wed, Dec 07, 2016 at 01:52:17PM +, Mark Rutland wrote:
> Hi all
>
> Jeremy noticed a kernel lockup on arm64 when the perf tool was used in
> parallel with hotplug, which I've reproduced on arm64 and x86(-64) with
> v4.9-rc8. In both cases I'm using defconfig; I've tried enabling lockdep
>
On Tue, Dec 6, 2016 at 10:27 PM, Zhouyi Zhou wrote:
> On Wed, Dec 7, 2016 at 1:02 PM, Cong Wang wrote:
>> On Mon, Dec 5, 2016 at 11:10 PM, Zhouyi Zhou wrote:
>>> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_fcoe.c
>>>
- Add slave definitions to i2c-designware-core
- Changes in Kconfig to auto-enable I2C_SLAVE when compiling the modules
- Add mode property to designware-core.txt that enable the "slave" selection:
- "mode" is an optional property that could be "slave" or "master"
- if "mode" is not set the
On Tue, Dec 6, 2016 at 10:27 PM, Zhouyi Zhou wrote:
> On Wed, Dec 7, 2016 at 1:02 PM, Cong Wang wrote:
>> On Mon, Dec 5, 2016 at 11:10 PM, Zhouyi Zhou wrote:
>>> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_fcoe.c
>>> b/drivers/net/ethernet/intel/ixgbe/ixgbe_fcoe.c
>>> index
- Add slave definitions to i2c-designware-core
- Changes in Kconfig to auto-enable I2C_SLAVE when compiling the modules
- Add mode property to designware-core.txt that enable the "slave" selection:
- "mode" is an optional property that could be "slave" or "master"
- if "mode" is not set the
- Factor out all _master() part of code from i2c-designware-core
and i2c-designware-platdrv to separate functions.
- Standardize all code related with MASTER modes.
Signed-off-by: Luis Oliveira
---
Changes V3->V4: (Andy Shevchenko)
- I have to take off DW_IC_INTR_TX_EMPTY
- Factor out all _master() part of code from i2c-designware-core
and i2c-designware-platdrv to separate functions.
- Standardize all code related with MASTER modes.
Signed-off-by: Luis Oliveira
---
Changes V3->V4: (Andy Shevchenko)
- I have to take off DW_IC_INTR_TX_EMPTY from
- Slave mode selected by compatibility string in platform module
- Changes in Makefile to Kbuild successfully compile i2c-designware-core
with slave functions
Signed-off-by: Luis Oliveira
---
Changes V3->V4: (Andy Shevchenko)
- nothing changed
- Missspelling, comment formatation and fix a string of
the existing code
Signed-off-by: Luis Oliveira
---
Changes V3->V4: (Andy Shevchenko)
- created a commit message
drivers/i2c/busses/i2c-designware-common.c | 2 +-
drivers/i2c/busses/i2c-designware-slave.c | 10
- Missspelling, comment formatation and fix a string of
the existing code
Signed-off-by: Luis Oliveira
---
Changes V3->V4: (Andy Shevchenko)
- created a commit message
drivers/i2c/busses/i2c-designware-common.c | 2 +-
drivers/i2c/busses/i2c-designware-slave.c | 10 ++
2 files
- Slave mode selected by compatibility string in platform module
- Changes in Makefile to Kbuild successfully compile i2c-designware-core
with slave functions
Signed-off-by: Luis Oliveira
---
Changes V3->V4: (Andy Shevchenko)
- nothing changed
drivers/i2c/busses/Makefile |
The purpose of this patch is to enable Linux to be a I2C slave by enabling the
slave functionality in the designware I2C controller. The patch refactors the
original i2c-designware-core and extracts all master functions to a
i2c-designware-master source file as suggested by Andy Shevchenko. It
The purpose of this patch is to enable Linux to be a I2C slave by enabling the
slave functionality in the designware I2C controller. The patch refactors the
original i2c-designware-core and extracts all master functions to a
i2c-designware-master source file as suggested by Andy Shevchenko. It
Hi,
On Wed, Dec 07, 2016 at 06:09:16PM +0100, Heiko Stuebner wrote:
> Am Donnerstag, 1. Dezember 2016, 18:27:28 CET schrieb Brian Norris:
> > Add the dwc3 usb needed node information for rk3399.
> >
> > Signed-off-by: Brian Norris
> > ---
> > Somewhat rewritten from
Hi,
On Wed, Dec 07, 2016 at 06:09:16PM +0100, Heiko Stuebner wrote:
> Am Donnerstag, 1. Dezember 2016, 18:27:28 CET schrieb Brian Norris:
> > Add the dwc3 usb needed node information for rk3399.
> >
> > Signed-off-by: Brian Norris
> > ---
> > Somewhat rewritten from Caesar's reposting (v2) of
On Wed, Dec 07, 2016 at 08:39:02AM +0100, Fabian Frederick wrote:
> Fix the following build errors
I couldn't reproduce it on default config. Can you mention the necessary
environment/defconfig/arch etc.?
Patch itself looks needed. However shouldn't the driver depend also on
GPIOLIB?
Best
On Wed, Dec 07, 2016 at 08:39:02AM +0100, Fabian Frederick wrote:
> Fix the following build errors
I couldn't reproduce it on default config. Can you mention the necessary
environment/defconfig/arch etc.?
Patch itself looks needed. However shouldn't the driver depend also on
GPIOLIB?
Best
according to datasheet complete control register is of 2 bytes.
http://www.analog.com/media/en/technical-documentation/data-sheets/AD5933.pdf
Signed-off-by: Nizam Haider
---
drivers/staging/iio/impedance-analyzer/ad5933.c | 4 ++--
1 file changed, 2 insertions(+), 2
according to datasheet complete control register is of 2 bytes.
http://www.analog.com/media/en/technical-documentation/data-sheets/AD5933.pdf
Signed-off-by: Nizam Haider
---
drivers/staging/iio/impedance-analyzer/ad5933.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Wed, Dec 07, 2016 at 06:12:13PM +0100, Heiko Stuebner wrote:
> Hi Brian,
>
> Am Donnerstag, 1. Dezember 2016, 18:27:30 CET schrieb Brian Norris:
> > Gru is a base dev board for a family of devices, including Kevin. Both
> > utilize Rockchip RK3399, and they share much of their design.
> >
> >
On Wed, Dec 07, 2016 at 06:12:13PM +0100, Heiko Stuebner wrote:
> Hi Brian,
>
> Am Donnerstag, 1. Dezember 2016, 18:27:30 CET schrieb Brian Norris:
> > Gru is a base dev board for a family of devices, including Kevin. Both
> > utilize Rockchip RK3399, and they share much of their design.
> >
> >
From: Santosh Shilimkar
Date: Wed, 7 Dec 2016 09:20:17 -0800
> Newer/Updated tools which can parse this extra info in needs newer
> or an updated kernel which supports and populates these fields.
>
> As mentioned, this particular option used only in verbose mode so
From: Santosh Shilimkar
Date: Wed, 7 Dec 2016 09:20:17 -0800
> Newer/Updated tools which can parse this extra info in needs newer
> or an updated kernel which supports and populates these fields.
>
> As mentioned, this particular option used only in verbose mode so
> am ok to drop this change
On Wed, Dec 07, 2016 at 11:11:08AM -0600, Christoph Lameter wrote:
> On Wed, 7 Dec 2016, Mel Gorman wrote:
>
> > 3.0-era kernels had better fragmentation control, higher success rates at
> > allocation etc. I vaguely recall that it had fewer sources of high-order
> > allocations but I don't
On Wed, Dec 07, 2016 at 11:11:08AM -0600, Christoph Lameter wrote:
> On Wed, 7 Dec 2016, Mel Gorman wrote:
>
> > 3.0-era kernels had better fragmentation control, higher success rates at
> > allocation etc. I vaguely recall that it had fewer sources of high-order
> > allocations but I don't
On Wed, 2016-12-07 at 15:43 +0800, Zhouyi Zhou wrote:
> Signed-off-by: Zhouyi Zhou
> Reviewed-by: Cong Wang
> Reviewed-by: Yuval Shaia
> Reviewed-by: Eric Dumazet
> ---
>
On Wed, 2016-12-07 at 15:43 +0800, Zhouyi Zhou wrote:
> Signed-off-by: Zhouyi Zhou
> Reviewed-by: Cong Wang
> Reviewed-by: Yuval Shaia
> Reviewed-by: Eric Dumazet
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_fcoe.c | 6 +-
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 3 +--
> 2
On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
>
> a "+ int ret;" should be move from [12/15] to here, I have fix the
> problem in my repo, it would happen in next patchset
>
> https://git.linaro.org/people/fu.wei/linux.git/log/?h=topic-gtdt-wakeup-timer_upstream_v18_devel
Fu,
On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote:
>
> a "+ int ret;" should be move from [12/15] to here, I have fix the
> problem in my repo, it would happen in next patchset
>
> https://git.linaro.org/people/fu.wei/linux.git/log/?h=topic-gtdt-wakeup-timer_upstream_v18_devel
Fu, please post v18 to
Fix to avoid possible memory leak and exit file handle
in error paths.
Signed-off-by: Santosh Kumar Singh
---
drivers/media/platform/vim2m.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c
index
Fix to avoid possible memory leak and exit file handle
in error paths.
Signed-off-by: Santosh Kumar Singh
---
drivers/media/platform/vim2m.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c
index a98f679..9fd24b8 100644
---
Hi Brian,
Am Donnerstag, 1. Dezember 2016, 18:27:32 CET schrieb Brian Norris:
> We need to add regulators to the CPU nodes, so cpufreq doesn't think it
> can crank up the clock speed without changing the voltage. However, we
> don't yet have the DT bindings to fully describe the Over Voltage
>
Hi Brian,
Am Donnerstag, 1. Dezember 2016, 18:27:32 CET schrieb Brian Norris:
> We need to add regulators to the CPU nodes, so cpufreq doesn't think it
> can crank up the clock speed without changing the voltage. However, we
> don't yet have the DT bindings to fully describe the Over Voltage
>
On Dec 7, 2016, at 10:20 AM, Quentin Lambert wrote:
> Hi all,
>
> I am looking at the drivers/staging/lustre/lustre/llite/dir.c:
>
> 1469 /* Call mdc_iocontrol */
> 1470 rc = obd_iocontrol(LL_IOC_FID2MDTIDX, exp, sizeof(fid),
> ,
> 1471
On Dec 7, 2016, at 10:20 AM, Quentin Lambert wrote:
> Hi all,
>
> I am looking at the drivers/staging/lustre/lustre/llite/dir.c:
>
> 1469 /* Call mdc_iocontrol */
> 1470 rc = obd_iocontrol(LL_IOC_FID2MDTIDX, exp, sizeof(fid),
> ,
> 1471
Hello Krzysztof,
On 12/07/2016 02:18 PM, Krzysztof Kozlowski wrote:
> I use Patchwork for handling incoming patches. Put its address here so
> submitters could know what is in the queue.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1
Hello Krzysztof,
On 12/07/2016 02:18 PM, Krzysztof Kozlowski wrote:
> I use Patchwork for handling incoming patches. Put its address here so
> submitters could know what is in the queue.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
>
On 12/7/2016 9:05 AM, David Miller wrote:
From: Santosh Shilimkar
Date: Wed, 7 Dec 2016 08:44:04 -0800
On 12/7/2016 7:55 AM, David Miller wrote:
From: Santosh Shilimkar
Date: Tue, 6 Dec 2016 20:01:56 -0800
What level of
On 12/7/2016 9:05 AM, David Miller wrote:
From: Santosh Shilimkar
Date: Wed, 7 Dec 2016 08:44:04 -0800
On 12/7/2016 7:55 AM, David Miller wrote:
From: Santosh Shilimkar
Date: Tue, 6 Dec 2016 20:01:56 -0800
What level of compatability exists here? If we run an old tool on a
new
kernel, or
On 12/6/2016 11:56 PM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> There are 3 separated controllers, one per USB /standard/. With PHY
> drivers in place they can be simply supported with generic drivers.
>
> Signed-off-by: Rafał Miłecki
> ---
> V2: Fix
On 12/6/2016 11:56 PM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> There are 3 separated controllers, one per USB /standard/. With PHY
> drivers in place they can be simply supported with generic drivers.
>
> Signed-off-by: Rafał Miłecki
> ---
> V2: Fix node names and reorder ehci with
I use Patchwork for handling incoming patches. Put its address here so
submitters could know what is in the queue.
Signed-off-by: Krzysztof Kozlowski
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 191887bdc49b..ec5137c39572
I use Patchwork for handling incoming patches. Put its address here so
submitters could know what is in the queue.
Signed-off-by: Krzysztof Kozlowski
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 191887bdc49b..ec5137c39572 100644
---
Hi Brian,
Am Donnerstag, 1. Dezember 2016, 18:27:30 CET schrieb Brian Norris:
> Gru is a base dev board for a family of devices, including Kevin. Both
> utilize Rockchip RK3399, and they share much of their design.
>
> Signed-off-by: Brian Norris
> ---
>
Hi Brian,
Am Donnerstag, 1. Dezember 2016, 18:27:30 CET schrieb Brian Norris:
> Gru is a base dev board for a family of devices, including Kevin. Both
> utilize Rockchip RK3399, and they share much of their design.
>
> Signed-off-by: Brian Norris
> ---
>
On Dec 7, 2016, at 10:33 AM, Dan Carpenter wrote:
> Lustre is kind of a mess with regards to keeping user and kernel
> pointers separate. It's not going to be easy to fix.
Actually I believe I made significant inroads in properly cleaning (almost?)
everything
in this area about a year ago (to
On Wed, 7 Dec 2016, Mel Gorman wrote:
> 3.0-era kernels had better fragmentation control, higher success rates at
> allocation etc. I vaguely recall that it had fewer sources of high-order
> allocations but I don't remember specifics and part of that could be the
> lack of THP at the time. The
On Dec 7, 2016, at 10:33 AM, Dan Carpenter wrote:
> Lustre is kind of a mess with regards to keeping user and kernel
> pointers separate. It's not going to be easy to fix.
Actually I believe I made significant inroads in properly cleaning (almost?)
everything
in this area about a year ago (to
On Wed, 7 Dec 2016, Mel Gorman wrote:
> 3.0-era kernels had better fragmentation control, higher success rates at
> allocation etc. I vaguely recall that it had fewer sources of high-order
> allocations but I don't remember specifics and part of that could be the
> lack of THP at the time. The
Hi Heiko,
On Wed, Dec 07, 2016 at 05:48:24PM +0100, Heiko Stuebner wrote:
> Am Donnerstag, 1. Dezember 2016, 18:27:32 CET schrieb Brian Norris:
> > We need to add regulators to the CPU nodes, so cpufreq doesn't think it
> > can crank up the clock speed without changing the voltage. However, we
>
Hi Heiko,
On Wed, Dec 07, 2016 at 05:48:24PM +0100, Heiko Stuebner wrote:
> Am Donnerstag, 1. Dezember 2016, 18:27:32 CET schrieb Brian Norris:
> > We need to add regulators to the CPU nodes, so cpufreq doesn't think it
> > can crank up the clock speed without changing the voltage. However, we
>
Hi Brian,
Am Donnerstag, 1. Dezember 2016, 18:27:28 CET schrieb Brian Norris:
> Add the dwc3 usb needed node information for rk3399.
>
> Signed-off-by: Brian Norris
> ---
> Somewhat rewritten from Caesar's reposting (v2) of my patch.
>
> Changes:
> * Include USB2 PHY
Hi Brian,
Am Donnerstag, 1. Dezember 2016, 18:27:28 CET schrieb Brian Norris:
> Add the dwc3 usb needed node information for rk3399.
>
> Signed-off-by: Brian Norris
> ---
> Somewhat rewritten from Caesar's reposting (v2) of my patch.
>
> Changes:
> * Include USB2 PHY (which is now in -next)
>
From: Santosh Shilimkar
Date: Wed, 7 Dec 2016 08:44:04 -0800
> On 12/7/2016 7:55 AM, David Miller wrote:
>> From: Santosh Shilimkar
>> Date: Tue, 6 Dec 2016 20:01:56 -0800
>>
>> What level of compatability exists here? If we run an
From: Santosh Shilimkar
Date: Wed, 7 Dec 2016 08:44:04 -0800
> On 12/7/2016 7:55 AM, David Miller wrote:
>> From: Santosh Shilimkar
>> Date: Tue, 6 Dec 2016 20:01:56 -0800
>>
>> What level of compatability exists here? If we run an old tool on a
>> new
>> kernel, or a new tool on an old
From: Jiri Olsa
An upcoming fixdep fix needs all targets at the same area, so they'll
fit under a signal condition block.
Moving PERF-VERSION-FILE target into rules section.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
From: Jiri Olsa
Because there's no need for them in fixdep build.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link:
From: Jiri Olsa
An upcoming fixdep fix needs all targets at the same area, so they'll
fit under a signal condition block.
Moving PERF-VERSION-FILE target into rules section.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link:
From: Jiri Olsa
Because there's no need for them in fixdep build.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link:
http://lkml.kernel.org/r/1481030331-31944-4-git-send-email-jo...@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
1. Add L3 caches events to /sys/devices/hisi_l3c0_2/events/
The events can be selected as shown in perf list
e.g.: For L3C_READ_ALLOCATE event for Super CPU cluster 2 the
event format is -e "hisi_l3c0_2/read_allocate/"
2. Add cpu_mask attribute group for showing the available CPU
for
1. Add L3 caches events to /sys/devices/hisi_l3c0_2/events/
The events can be selected as shown in perf list
e.g.: For L3C_READ_ALLOCATE event for Super CPU cluster 2 the
event format is -e "hisi_l3c0_2/read_allocate/"
2. Add cpu_mask attribute group for showing the available CPU
for
From: David Ahern
Arnaldo reported an unhelpful error message when running perf sched
timehist on a file that did not contain sched tracepoints:
[root@jouet ~]# perf sched timehist
No trace sample to read. Did you call 'perf record -R'?
[root@jouet ~]# perf
From: Namhyung Kim
The -D/--dump-raw-trace option is in the parent option so no need to
repeat it. Also move -f/--force option to parent as it's common to
handle data file.
Signed-off-by: Namhyung Kim
Acked-by: David Ahern
Cc: Andi
On Sat, Dec 03, 2016 at 11:48:33AM -0500, Dave Jones wrote:
> The interesting process here seems to be kworker/u8:17, and the trace
> captures some of what that was doing before that bad page was hit.
I'm travelling next week, so I'm trying to braindump the stuff I've
found so far and
1. Add nodes for hip06 L3 cache to support uncore events.
2. Add nodes for hip06 MN to support uncore events.
Signed-off-by: Shaokun Zhang
Signed-off-by: John Garry
Signed-off-by: Anurup M
---
Le 07/12/2016 à 17:32, Marek Vasut a écrit :
> On 12/07/2016 05:29 PM, Cyrille Pitchen wrote:
>> Le 07/12/2016 à 17:20, Marek Vasut a écrit :
>>> On 12/06/2016 05:52 PM, Cyrille Pitchen wrote:
This patch provides an alternative mean to support memory above 16MiB
(128Mib) by replacing
From: David Ahern
Arnaldo reported an unhelpful error message when running perf sched
timehist on a file that did not contain sched tracepoints:
[root@jouet ~]# perf sched timehist
No trace sample to read. Did you call 'perf record -R'?
[root@jouet ~]# perf evlist -v
From: Namhyung Kim
The -D/--dump-raw-trace option is in the parent option so no need to
repeat it. Also move -f/--force option to parent as it's common to
handle data file.
Signed-off-by: Namhyung Kim
Acked-by: David Ahern
Cc: Andi Kleen
Cc: Jiri Olsa
Cc: Minchan Kim
Cc: Peter Zijlstra
On Sat, Dec 03, 2016 at 11:48:33AM -0500, Dave Jones wrote:
> The interesting process here seems to be kworker/u8:17, and the trace
> captures some of what that was doing before that bad page was hit.
I'm travelling next week, so I'm trying to braindump the stuff I've
found so far and
1. Add nodes for hip06 L3 cache to support uncore events.
2. Add nodes for hip06 MN to support uncore events.
Signed-off-by: Shaokun Zhang
Signed-off-by: John Garry
Signed-off-by: Anurup M
---
arch/arm64/boot/dts/hisilicon/hip06.dtsi | 78
1 file changed, 78
Le 07/12/2016 à 17:32, Marek Vasut a écrit :
> On 12/07/2016 05:29 PM, Cyrille Pitchen wrote:
>> Le 07/12/2016 à 17:20, Marek Vasut a écrit :
>>> On 12/06/2016 05:52 PM, Cyrille Pitchen wrote:
This patch provides an alternative mean to support memory above 16MiB
(128Mib) by replacing
From: Shaokun Zhang
1. Add support to count MN hardware events.
2. Mn events are listed in sysfs at /sys/devices/hisi_mn_2/events/
The events can be selected as shown in perf list
e.g.: For MN_READ_REQUEST event for Super CPU cluster 2 the
event format is -e
On Tue, Dec 06, 2016 at 11:55:08AM +0530, Yury Norov wrote:
> On Mon, Dec 05, 2016 at 04:34:23PM +, Catalin Marinas wrote:
> > On Fri, Oct 21, 2016 at 11:33:15PM +0300, Yury Norov wrote:
> > > New aarch32 ptrace syscall handler is introduced to avoid run-time
> > > detection of the task type.
From: Yannick Brosseau
The fact that the --children option is enabled by default is buried deep
at the end of the help page, in the overhead calculation section. This
make it explicit right where the option is listed, following the same
way other default options are described
From: Yannick Brosseau
The fact that the --children option is enabled by default is buried deep
at the end of the help page, in the overhead calculation section. This
make it explicit right where the option is listed, following the same
way other default options are described
Signed-off-by:
From: Shaokun Zhang
1. Add support to count MN hardware events.
2. Mn events are listed in sysfs at /sys/devices/hisi_mn_2/events/
The events can be selected as shown in perf list
e.g.: For MN_READ_REQUEST event for Super CPU cluster 2 the
event format is -e "hisi_mn_2/read_req/"
On Tue, Dec 06, 2016 at 11:55:08AM +0530, Yury Norov wrote:
> On Mon, Dec 05, 2016 at 04:34:23PM +, Catalin Marinas wrote:
> > On Fri, Oct 21, 2016 at 11:33:15PM +0300, Yury Norov wrote:
> > > New aarch32 ptrace syscall handler is introduced to avoid run-time
> > > detection of the task type.
Removing silly virtio-dev@ list because it's bouncing mail...
On 12/07/2016 08:21 AM, David Hildenbrand wrote:
>> Li's current patches do that. Well, maybe not pfn/length, but they do
>> take a pfn and page-order, which fits perfectly with the kernel's
>> concept of high-order pages.
>
> So we
From: Tan Xiaojun
The Hisilicon Djtag is an independent component which connects
with some other components in the SoC by Debug Bus. This driver
can be configured to access the registers of connecting components
(like L3 cache) during real time debugging.
Signed-off-by:
1. Hip05/06/07 uncore PMU to support different hardware event counters.
2. Hisilicon PMU shall use the DJTAG hardware interface to access
hardware event counters and configuration register.
3. Routines to initialize and setup PMU.
4. Routines to enable/disable/add/del/start/stop hardware event
Add support for Hisilicon SoC hardware event counters
for HIP05/06/07 chip versions.
Signed-off-by: Anurup M
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b224caa..ce86c07 100644
--- a/MAINTAINERS
+++
Update Kconfig for Hip05/06/07 PMU support.
Signed-off-by: Anurup M
Signed-off-by: Shaokun Zhang
Signed-off-by: John Garry
---
drivers/perf/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git
From: Namhyung Kim
The callchain_cursor__copy() function is to save current callchain
captured by a cursor. It'll be used to keep callchains when switching
to idle task for each cpu.
Signed-off-by: Namhyung Kim
Cc: Andi Kleen
Cc:
Removing silly virtio-dev@ list because it's bouncing mail...
On 12/07/2016 08:21 AM, David Hildenbrand wrote:
>> Li's current patches do that. Well, maybe not pfn/length, but they do
>> take a pfn and page-order, which fits perfectly with the kernel's
>> concept of high-order pages.
>
> So we
From: Tan Xiaojun
The Hisilicon Djtag is an independent component which connects
with some other components in the SoC by Debug Bus. This driver
can be configured to access the registers of connecting components
(like L3 cache) during real time debugging.
Signed-off-by: Tan Xiaojun
1. Hip05/06/07 uncore PMU to support different hardware event counters.
2. Hisilicon PMU shall use the DJTAG hardware interface to access
hardware event counters and configuration register.
3. Routines to initialize and setup PMU.
4. Routines to enable/disable/add/del/start/stop hardware event
Add support for Hisilicon SoC hardware event counters
for HIP05/06/07 chip versions.
Signed-off-by: Anurup M
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b224caa..ce86c07 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5725,6
Update Kconfig for Hip05/06/07 PMU support.
Signed-off-by: Anurup M
Signed-off-by: Shaokun Zhang
Signed-off-by: John Garry
---
drivers/perf/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig
index 4d5c5f9..2befa55 100644
---
From: Namhyung Kim
The callchain_cursor__copy() function is to save current callchain
captured by a cursor. It'll be used to keep callchains when switching
to idle task for each cpu.
Signed-off-by: Namhyung Kim
Cc: Andi Kleen
Cc: David Ahern
Cc: Jiri Olsa
Cc: Minchan Kim
Cc: Peter
801 - 900 of 1558 matches
Mail list logo