On Tue, Dec 08, 2015 at 02:32:03PM +, Lee Jones wrote:
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Lee Jones
Acked-by: Rob Herring
> ---
> .../devicetree/bindings/cpufreq/cpufreq-st.txt | 91
> ++
> 1 file changed, 91 insertions(+)
> create mode 100644
From: Arnd Bergmann
Date: Tue, 08 Dec 2015 16:17:29 +0100
> The pq_mdio driver can now be built for ARM64, where we get a format
> string warning:
>
> drivers/net/ethernet/freescale/fsl_pq_mdio.c: In function 'fsl_pq_mdio_probe':
> drivers/net/ethernet/freescale/fsl_pq_mdio.c:467:25: warning:
On Tue, Dec 08, 2015 at 02:52:06PM +0100, Neil Armstrong wrote:
> Add generic caps properties to the binding in order to support
> future macb/gem implementations with the generic macb compatible form.
>
> Signed-off-by: Neil Armstrong
Acked-by: Rob Herring
> ---
>
From: Peter Wu
Date: Tue, 8 Dec 2015 12:17:42 +0100
> When an interface is brought up which was previously suspended (via
> runtime PM), it would hang. This happens because napi_disable is called
> before napi_enable.
>
> Solve this by avoiding napi_enable in the resume during open function
>
I'm experiencing a spot of trouble with this commit:
commit aad730d0704545ad97654bd929b0aba05adb1436
Author: Takashi Iwai
Date: Mon Dec 2 13:33:57 2013 +0100
ALSA: hda - Always do delayed probes for HD-audio devices
That adds some code:
#ifndef CONFIG_SND_HDA_I915
if
The UniPhier System Bus is an external bus that connects on-board
devices to the UniPhier SoC. Each bank (chip select) is dynamically
mapped to the CPU-viewed address base via the bus controller. The
bus controller must be configured before any access to the bus.
This driver parses the "ranges"
On Tue, Dec 08, 2015 at 01:45:04PM +0100, Maxime Coquelin wrote:
> Signed-off-by: Maxime Coquelin
> ---
> .../bindings/pinctrl/st,stm32-pinctrl.txt | 126
> +
> 1 file changed, 126 insertions(+)
> create mode 100644
>
Dongsheng Yang writes:
> On 12/09/2015 10:26 AM, Dongsheng Yang wrote:
>> On 10/25/2015 05:54 AM, Shayan Pooya wrote:
>>> I noticed the following core_pattern behavior in my linux box while
>>> running docker containers. I am not sure if it is bug, but it is
>>> inconsistent and not documented.
On Tue, Dec 08, 2015 at 05:49:10PM +0800, Yong Wu wrote:
> This patch add smi binding document.
>
> Signed-off-by: Yong Wu
Acked-by: Rob Herring
> ---
> .../memory-controllers/mediatek,smi-common.txt | 24 +
> .../memory-controllers/mediatek,smi-larb.txt | 25
>
On Tue, Dec 08, 2015 at 05:49:09PM +0800, Yong Wu wrote:
> This patch add mediatek iommu dts binding document.
>
> Signed-off-by: Yong Wu
> ---
> .../devicetree/bindings/iommu/mediatek,iommu.txt | 68 +
> include/dt-bindings/memory/mt8173-larb-port.h | 111
>
On 09/12/2015 01:12, Mark Brown wrote:
On Thu, Dec 03, 2015 at 05:31:51PM +0800, Xiubo Li wrote:
There will be some warning like the following when checking new
patches near this code:
"WARNING: Missing a blank line after declarations"
This patch will suppress this warning.
On Tue, Dec 08, 2015 at 02:13:19PM +0800, Herbert Xu wrote:
> On Mon, Dec 07, 2015 at 07:58:25AM +0100, Stefan Priebe - Profihost AG wrote:
> >
> > Thanks, good. Can you help me to get this fix upstream into the stable
> > lines?
>
> Sure. Greg, please apply this patch to fix up the backport for
On 2015/12/9 11:19, Taku Izumi wrote:
> This patch extends existing "kernelcore" option and
> introduces kernelcore=mirror option. By specifying
> "mirror" instead of specifying the amount of memory,
> non-mirrored (non-reliable) region will be arranged
> into ZONE_MOVABLE.
>
> v1 -> v2:
> -
On Mon, Dec 07, 2015 at 06:21:56PM +0100, Bjørn Mork wrote:
> Greg Kroah-Hartman writes:
>
> > 4.1-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
> >
> > [ Upstream commit
On Mon, Dec 07, 2015 at 01:14:57PM -0800, Guenter Roeck wrote:
> On Mon, Dec 07, 2015 at 09:04:54AM -0500, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.10.94 release.
> > There are 31 patches in this series, all will be posted as a response
> > to this one.
On Mon, Dec 07, 2015 at 01:16:05PM -0800, Guenter Roeck wrote:
> On Mon, Dec 07, 2015 at 09:26:12AM -0500, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.14.58 release.
> > There are 37 patches in this series, all will be posted as a response
> > to this one.
On Mon, Dec 07, 2015 at 01:28:44PM -0800, Guenter Roeck wrote:
> On Mon, Dec 07, 2015 at 10:00:13AM -0500, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.3.1 release.
> > There are 125 patches in this series, all will be posted as a response
> > to this one.
On 09/12/2015 01:05, Mark Brown wrote:
On Thu, Dec 03, 2015 at 10:19:10AM +0800, Xiubo Li wrote:
If the cache is not used by the device driver, there is not need to
check the striding of the registers. It will just return 0 from
regcache_init() and let the register striding be checked in
Hi Lorenzo,
On 8 December 2015 at 22:07, Lorenzo Pieralisi
wrote:
> On Tue, Dec 08, 2015 at 09:08:24PM +0800, Fu Wei wrote:
>> Hi Lorenzo,
>>
>>
>>
>> On 8 December 2015 at 20:52, Hanjun Guo wrote:
>> > Hi Lorenzo,
>> >
>> > On 12/08/2015 08:34 PM, Lorenzo Pieralisi wrote:
>> >>
>> >> On Tue,
On Mon, Dec 07, 2015 at 01:36:16PM -0800, Guenter Roeck wrote:
> On Mon, Dec 07, 2015 at 09:54:50AM -0500, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.2.7 release.
> > There are 124 patches in this series, all will be posted as a response
> > to this one.
Dear Xishi,
Thanks for reviewing.
> -Original Message-
> From: Xishi Qiu [mailto:qiuxi...@huawei.com]
> Sent: Wednesday, December 09, 2015 11:26 AM
> To: Izumi, Taku/泉 拓
> Cc: linux-kernel@vger.kernel.org; linux...@kvack.org; tony.l...@intel.com;
> Kamezawa, Hiroyuki/亀澤 寛之;
On Mon, Dec 07, 2015 at 11:10:22PM +0100, Christian Borntraeger wrote:
> On 12/07/2015 04:01 PM, Greg Kroah-Hartman wrote:
> > 4.3-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: David Hildenbrand
> >
> > commit
On Mon, Dec 07, 2015 at 01:26:57PM -0800, Guenter Roeck wrote:
> On Mon, Dec 07, 2015 at 09:34:54AM -0500, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.1.14 release.
> > There are 95 patches in this series, all will be posted as a response
> > to this one.
According to arch/sh/kernel/syscalls_64.S and common sense,
__NR_fgetxattr has to be defined to 259, but it doesn't.
Instead, it's defined to 269, which is of course used
by another syscall, __NR_sched_setaffinity in this case.
This bug was found by strace test suite.
Signed-off-by: Dmitry V.
This patch extends existing "kernelcore" option and
introduces kernelcore=mirror option. By specifying
"mirror" instead of specifying the amount of memory,
non-mirrored (non-reliable) region will be arranged
into ZONE_MOVABLE.
v1 -> v2:
- Refine so that the following case also can be
handled
On Tue, Dec 08, 2015 at 10:26:53AM +0530, Sudip Mukherjee wrote:
> On Mon, Dec 07, 2015 at 09:54:50AM -0500, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.2.7 release.
> > There are 124 patches in this series, all will be posted as a response
> > to this one.
Currently each zone's zone_start_pfn is calculated at
free_area_init_core(). However zone's range is fixed at
the time when invoking zone_spanned_pages_in_node().
This patch changes each zone->zone_start_pfn is
calculated at zone_spanned_pages_in_node().
Signed-off-by: Taku Izumi
---
On Mon, Dec 07, 2015 at 03:09:13PM +0100, Cyrille Pitchen wrote:
> This patch documents the DT bindings for the driver of the Atmel QSPI
> controller embedded inside sama5d2x SoCs.
>
> Signed-off-by: Cyrille Pitchen
Acked-by: Rob Herring
> ---
> .../devicetree/bindings/mtd/atmel-quadspi.txt
From: Yanjiang Jin
Use boot_cpu_type() instead of current_cpu_type() in oprofile_arch_init()
to avoid the below warning, cpu_type is consistent in a MIPS SMP system.
BUG: using smp_processor_id() in preemptible [] code: insmod/952
caller is oprofile_arch_init+0x30/0x194 [oprofile]
CPU:
Xeon E7 v3 based systems supports Address Range Mirroring
and UEFI BIOS complied with UEFI spec 2.5 can notify which
ranges are mirrored (reliable) via EFI memory map.
Now Linux kernel utilize its information and allocates
boot time memory from reliable region.
My requirement is:
- allocate
From: Yanjiang Jin
Reproduction steps:
1. Build a MIPS BSP with CONFIG_OPROFILE=m, I am using Cavium's CN78XX board to
test;
2. Boot the board;
3. modprobe oprofile in shell.
Yanjiang Jin (1):
MIPS: oprofile: Fix a preemption issue
arch/mips/oprofile/common.c | 2 +-
1 file changed, 1
On Mon, Dec 07, 2015 at 10:19:32AM -0700, Shuah Khan wrote:
> On 12/07/2015 08:00 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.3.1 release.
> > There are 125 patches in this series, all will be posted as a response
> > to this one. If anyone has any
From: Kejian Yan
Date: Tue, 8 Dec 2015 11:02:31 +0800
> here is the patch raising the performance of XGE by:
> 1)changes the way page management method for enet momery, and
> 2)reduces the count of rmb, and
> 3)adds Memory prefetching
>
> Signed-off-by: Kejian Yan
Applied.
--
To unsubscribe
From: Tejun Heo
Date: Mon, 7 Dec 2015 17:38:47 -0500
> 0001-0003 are prepatory patches in kernfs and cgroup. These patches
> are available in the following branch which will stay stable.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
> for-4.5-ancestor-test
Pulled into
On 09-12-15, 08:27, Viresh Kumar wrote:
> Good work Lee, looks mostly okay. Few nits below.
Also, it may make sense to quit early of opp-v2 isn't present in your
/cpus/cpuX node. As we wouldn't be using any of this then.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe
Hi Suzuki,
On 8 December 2015 at 23:53, Suzuki K. Poulose wrote:
> On 08/12/15 07:03, fu@linaro.org wrote:
>>
>> From: Tomasz Nowicki
>>
>> This commit provides APEI arch-specific bits for aarch64
>>
>> Meanwhile, add a new subfunction "hest_ia_init" for
>> "acpi_disable_cmcff" which is
Good day, hoping you read this email and respond to me in good time.I do not
intend to solicit for funds but your time and energy in using my own resources
to assist the less privileged becauseI am medically ill and confined at the
moment hence I request your indulgence.I will give you a
Good work Lee, looks mostly okay. Few nits below.
On 08-12-15, 14:32, Lee Jones wrote:
> The bootloader is charged with the responsibility to provide platform
> specific Dynamic Voltage and Frequency Scaling (DVFS) information via
> Device Tree. This driver takes the supplied configuration and
>
On 12/08/15 at 10:57pm, Daniel Kiper wrote:
> Provide just print_crashkernel_region_size() stub. This way
> we can properly build kexec utility on cris arch even
> if the functionality is not available on it.
>
> Signed-off-by: Daniel Kiper
> ---
> kexec/arch/cris/kexec-cris.c |5 +
> 1
On Wed, Dec 02, 2015 at 12:02:45PM -0800, Tim Chen wrote:
>
> +/*
> + * CRYPTO_ALG_ASYNC flag is passed to indicate we have an ablk
> + * scatter-gather walk.
> + */
> +
> +static struct crypto_alg aes_cbc_mb_alg = {
> + .cra_name = "__cbc-aes-aesni-mb",
> + .cra_driver_name
On 12/08/15 at 10:57pm, Daniel Kiper wrote:
> Provide just print_crashkernel_region_size() stub. This way
> we can properly build kexec utility on ppc64 arch even
> if the functionality is not available on it.
Ditto as ppc, you can read procfs file to get the values..
>
> Signed-off-by: Daniel
On 12/08/15 at 10:57pm, Daniel Kiper wrote:
> Provide just print_crashkernel_region_size() stub. This way
> we can properly build kexec utility on ppc arch even
> if the functionality is not available on it.
The functionality is available by reading device tree nodes in procfs..
>
>
On 12/09/2015 10:26 AM, Dongsheng Yang wrote:
On 10/25/2015 05:54 AM, Shayan Pooya wrote:
I noticed the following core_pattern behavior in my linux box while
running docker containers. I am not sure if it is bug, but it is
inconsistent and not documented.
If the core_pattern is set on the
From: Julia Lawall
Date: Tue, 8 Dec 2015 21:18:25 +0100
> The xgene_mac_ops and xgene_port_ops structures are never modified, so
> declare them as const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
Applied to net-next, thanks.
--
To unsubscribe from this list: send
The kerneldoc for request_firmware_nowait() says that it may call the
provided cont() callback with @fw == NULL, if the firmware request
fails. However, this is not the case when called with an empty string
(""). This case is short-circuited by the 'name[0] == '\0'' check
introduced in commit
On 2015/12/9 10:25, Xishi Qiu wrote:
> On 2015/11/27 23:04, Taku Izumi wrote:
>
>> This patch extends existing "kernelcore" option and
>> introduces kernelcore=reliable option. By specifying
>> "reliable" instead of specifying the amount of memory,
>> non-reliable region will be arranged into
Now that we've added a 'trigger_async_request' knob to test the
request_firmware_nowait() API, let's use it. Also add tests for the
empty ("") string, since there have been a couple errors in that
handling already.
Since we know have real wasy that the sysfs write might fail, let's add
the
On 12/09/15 at 10:38am, Herbert Xu wrote:
> On Wed, Dec 09, 2015 at 03:36:32AM +0100, Thomas Graf wrote:
> >
> > Without knowing your exact implementation plans: introducing an
> > additional reference indirection for every lookup will have a
> > huge performance penalty as well.
> >
> > Is your
We might want to test for bugs like that found in commit f9692b2699bd
("firmware: fix possible use after free on name on asynchronous
request"), where the asynchronous request API had race conditions.
Let's add a simple file that will launch the async request, then wait
until it's complete and
On 08-12-15, 14:32, Lee Jones wrote:
> +/**
> + * SMP Operations
> + */
Why do you need a documentation style comment here?
> static void write_pen_release(int val)
> {
> pen_release = val;
> @@ -161,3 +166,11 @@ struct smp_operations __initdata sti_smp_ops = {
>
On Wed, Dec 09, 2015 at 03:36:32AM +0100, Thomas Graf wrote:
>
> Without knowing your exact implementation plans: introducing an
> additional reference indirection for every lookup will have a
> huge performance penalty as well.
>
> Is your plan to only introduce the master table after an
>
request_firmware() failures currently won't get reported at all (the
error code is discarded). What's more, we get confusing messages, like:
# echo -n notafile > /sys/devices/virtual/misc/test_firmware/trigger_request
[ 8280.311856] test_firmware: loading 'notafile'
[ 8280.317042]
On 12/09/15 at 10:24am, Herbert Xu wrote:
> On Wed, Dec 09, 2015 at 03:18:26AM +0100, Thomas Graf wrote:
> >
> > Assuming that we only encounter this scenario with very large
> > table sizes, it might be OK to assume that deferring the actual
> > resize via the worker thread while continuing to
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/i915/intel_pm.c
between commits:
344df9809f45 ("drm/i915/skl: Disable coarse power gating up until F0")
6704d4552853 ("drm/i915/skl: Double RC6 WRL always on")
from the drm-intel-fixes tree and commit:
On 09-12-15, 02:15, Rafael J. Wysocki wrote:
> If there are only the two patches, why don't you ask Lee to include them
> into the series he's working on? The dependency would be clear then too.
His series was already out, and it was really about STi's cpufreq
driver and so I have resent my two
On 10/25/2015 05:54 AM, Shayan Pooya wrote:
I noticed the following core_pattern behavior in my linux box while
running docker containers. I am not sure if it is bug, but it is
inconsistent and not documented.
If the core_pattern is set on the host, the containers will observe
and use the
OPP bindings (for few properties) allow a platform to choose a
value/range among a set of available options. The options are present as
opp--, where the platform needs to supply the string.
The OPP properties which allow such an option are: opp-microvolt and
opp-microamp.
Add support to the
OPP bindings allow a platform to enable OPPs based on the version of the
hardware they are used for.
Add support to the OPP-core to parse these bindings, by introducing
dev_pm_opp_{set|put}_supported_hw() APIs.
Signed-off-by: Viresh Kumar
---
drivers/base/power/opp/core.c | 148
Hi Rafael,
These patches parse the newly added opp-supported-hw/opp--
bindings.
Rebased over: Latest pm/linux-next
Tested-on: Exynos 5250, dual core A15.
V2->V3:
- Stephen had an interesting point to make for V2, as the patches
created the dev_opp first and then updated it within the OPP-list
On 2015/11/27 23:04, Taku Izumi wrote:
> This patch extends existing "kernelcore" option and
> introduces kernelcore=reliable option. By specifying
> "reliable" instead of specifying the amount of memory,
> non-reliable region will be arranged into ZONE_MOVABLE.
>
> v1 -> v2:
> - Refine so that
On Wed, Dec 09, 2015 at 03:18:26AM +0100, Thomas Graf wrote:
>
> Assuming that we only encounter this scenario with very large
> table sizes, it might be OK to assume that deferring the actual
> resize via the worker thread while continuing to insert above
> 100% utilization in atomic context is
Hi Arnaldo,
Here is a series of patches for perf refcnt debugger and
some fixes.
In this series I've replaced all atomic reference counters
with the refcnt interface, including dso, map, map_groups,
thread, cpu_map, comm_str, cgroup_sel, thread_map, and
perf_mmap.
refcnt debugger (or refcnt
This is a kind of debugging feature for atomic reference counter.
The reference counters are widely used in perf tools but not well
debugged. It sometimes causes memory leaks but no one has noticed
the issue, since it is hard to debug such un-reclaimed objects.
This refcnt interface provides
Make refcnt to use a hash table to reduce search overhead
on refcnt_root. This hash is based on passed object address.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/refcnt.c | 71 --
1 file changed, 49 insertions(+), 22 deletions(-)
diff
Report refcnt per object(class) summary numbers if
any leaks exist, not only the total number.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/refcnt.c | 44
1 file changed, 44 insertions(+)
diff --git a/tools/perf/util/refcnt.c
Make 'map_groups' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
E.g.
# ./perf top --stdio
^q
REFCNT: BUG: Unreclaimed objects found.
REFCNT: Total 3615 objects are not reclaimed.
"map" leaks 3373 objects
"dso" leaks 232 objects
Make 'map' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
E.g.
./perf probe vfs_read
Added new event:
probe:vfs_read (on vfs_read)
You can now use it in all perf tools, such as:
perf record -e probe:vfs_read -aR sleep 1
Make 'dso' object to use refcnt interface for debug.
This can find refcnt related memory leaks on dsos.
E.g.
# ./perf probe vfs_read
Added new event:
probe:vfs_read (on vfs_read)
You can now use it in all perf tools, such as:
perf record -e probe:vfs_read -aR
Make 'comm_str' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
# ./perf top --stdio
^q
REFCNT: BUG: Unreclaimed objects found.
REFCNT: Total 3369 objects are not reclaimed.
"dso" leaks 193 objects
"map" leaks 3154 objects
Make 'perf_mmap' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/evlist.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
Make 'thread_map' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/thread_map.c | 28 +++-
1 file changed, 15 insertions(+), 13 deletions(-)
diff --git
Make 'cgroup_sel' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/cgroup.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/cgroup.c
Fix dso__load_sym to put dso because dsos__add already got it.
Refcnt debugger explain the problem:
[0]
Unreclaimed dso: 0x19dd200
Refcount +1 => 1 at
./perf(dso__new+0x1ff) [0x4a62df]
./perf(dso__load_sym+0xe89) [0x503509]
./perf(dso__load_vmlinux+0xbf)
Fix map_groups__clone to put cloned map after
inserting it to the map_groups.
Refcnt debugger shows:
[0]
Unreclaimed map: 0x2a27ee0
Refcount +1 => 1 at
./perf(map_groups__clone+0x8d) [0x4bb7ed]
./perf(thread__fork+0xbe) [0x4c1f9e]
Fix __machine__addnew_vdso to put dso after add to dsos because
the dso is already gotten by the dsos via __dsos__add().
This function is called finally from machine__findnew_vdso()
which locks machine->dsos.lock. And before unlock it, the
function gets the dso's refcnt. Thus we can ensure that
Since perf_session__register_idle_thread() got the idle thread,
caller functions have to put it afterwards.
Note that since the thread was already inserted to the session
list, it will be released when the session is released.
Also, in perf_session__register_idle_thread() failure path,
the thread
Since the __map_groups__insert got the given map, we don't
need to keep it. So put the maps.
Refcnt debugger shows that the map_groups__fixup_overlappings
got a map twice but the group released it once. This pattern
usually indicates the leak happens in caller site.
[0]
Fix machine.vmlinux_maps to make sure to clear the old one
if it is renewal. This can leak the previous maps on the
vmlinux_maps because those are just overwritten.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/machine.c |5 +
1 file changed, 5 insertions(+)
diff --git
Fix write_numa_topology to put cpu_map instead of free because
cpu_map is managed based on refcnt.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/header.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
index
Since hists__init doesn't set the destructor of
hists_evsel (which is an extended evsel structure),
when hists_evsel is released, the extended part of
the hists_evsel is not deleted (note that the
hists_evsel object itself is freed).
This fixes it to add a destructor for hists__evsel
and to set
Hello Krzysztof,
On 12/08/2015 09:34 PM, Krzysztof Kozlowski wrote:
> On 08.12.2015 22:41, Javier Martinez Canillas wrote:
>> On 12/08/2015 05:13 AM, Krzysztof Kozlowski wrote:
>>>
>>> This looks like a very-non-atomic way of handling a change. You added
>>> opp tables to exynos5420 before so at
Make 'cpu_map' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
Signed-off-by: Masami Hiramatsu
---
tools/perf/util/cpumap.c | 33 +
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/tools/perf/util/cpumap.c
Fix cmd_stat() to release cpu_map objects (aggr_map and
cpus_aggr_map) afterwards.
refcnt debugger shows that the cmd_stat initializes cpu_map
but not puts it.
# ./perf stat -v ls
REFCNT: BUG: Unreclaimed objects found.
[0]
Unreclaimed cpu_map@0x29339c0
Refcount
Make 'thread' object to use refcnt interface for debug.
This can find refcnt related memory leaks.
E.g.
# ./perf top --stdio
^q
REFCNT: BUG: Unreclaimed objects found.
REFCNT: Total 3525 objects are not reclaimed.
"map" leaks 3285 objects
"dso" leaks 225 objects
Add refcnt debug filter for filtering the debug objects.
Developers can set the target object name (or glob pattern)
to PERF_REFCNT_DEBUG_FILTER environment variable.
E.g.
# PERF_REFCNT_DEBUG_FILTER=dso ./perf ...
This traces only the dso object. This also removes
unused name arguments from
On 12/05/15 at 03:06pm, Herbert Xu wrote:
> Unless we can make __vmalloc work with BH disabled, I guess we'll
> have to go back to multi-level lookups unless someone has a better
> suggestion.
Assuming that we only encounter this scenario with very large
table sizes, it might be OK to assume
From: Scott Wood
Date: Tue, 8 Dec 2015 16:44:38 -0600
> On Tue, 2015-12-08 at 14:18 -0600, Andy Fleming wrote:
>> On Thu, Dec 3, 2015 at 1:19 AM, wrote:
>> > From: Igal Liberman
>> >
>> > This patch adds the Ethernet MAC driver supporting the three
>> > different types of MACs: dTSEC, tGEC
From: valdis.kletni...@vt.edu
Date: Tue, 08 Dec 2015 16:54:17 -0500
> On Tue, 08 Dec 2015 12:34:09 +0100, Florian Westphal said:
>> Valdis Kletnieks wrote:
>>
>> [ CC Pablo ]
>>
>> > Seen this in 2 boots out of two on next-20151207 when IPV6 networking
>> > was available. It was stable when no
On 08-12-15, 22:52, Arnd Bergmann wrote:
> This driver is the only one that calls regulator_sync_voltage(), but it
> can currently be built with CONFIG_REGULATOR disabled, producing
> this build error:
>
> drivers/cpufreq/tegra124-cpufreq.c: In function 'tegra124_cpu_switch_to_pllx':
>
Some edp screen do not have hpd signal, so we can't just return
failed when hpd plug in detect failed.
This is an hardware property, so we need add a devicetree property
"analogix,need-force-hpd" to indicate this sutiation.
Signed-off-by: Yakir Yang
Tested-by: Javier Martinez Canillas
---
On Wed, Dec 2, 2015 at 1:05 PM, Jerry Hoemann wrote:
> Add ioctl command ND_CMD_CALL_DSM to acpi_nfit_ctl and __nd_ioctl which
> allow kernel to call a nvdimm's _DSM as a passthru without using the
> marshaling code of the nd_cmd_desc.
>
> Signed-off-by: Jerry Hoemann
> ---
>
Add dt binding documentation for rockchip display port PHY.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v10.1:
- Add the ack from Rob Herring
- Correct the title of this rockchip dp phy document(Rob)
Changes in v9: None
Changes in v8:
- Remove
cpufreq governors evaluate load at sampling rate and based on that they
update frequency for a group of CPUs belonging to the same cpufreq
policy.
This is required to be done in a single thread for all policy->cpus, but
because we don't want to wakeup idle CPUs to do just that, we use
deferrable
Rockchip DP driver is a helper driver of analogix_dp coder driver,
so most of the DT property should be descriped in analogix_dp document.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v10.1:
- Add the ack from Rob Herring
Changes in v10: None
Analogix dp driver is split from exynos dp driver, so we just
make an copy of exynos_dp.txt, and then simplify exynos_dp.txt
Beside update some exynos dtsi file with the latest change
according to the devicetree binding documents.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
Tested-by:
> 68e115b19a01 ("cpufreq: governor: replace per-cpu delayed work with timers")
>
> I have used the pm tree from next-20151208 for today.
Yeah, it missed this stupid change. Sorry about that.
diff --git a/drivers/cpufreq/cpufreq_governor.c
b/drivers/cpufreq/cpufreq_governor
I have used the pm tree from next-20151208 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
Since there will be several places checking if fwnode.type
is equal FWNODE_IRQCHIP, this patch adds a convenient function
for this purpose.
Signed-off-by: Suravee Suthikulpanit
---
drivers/irqchip/irq-gic.c | 2 +-
include/linux/irqdomain.h | 5 +
kernel/irq/irqdomain.c| 2 +-
3 files
This patch adds an accessor function to retrieve struct irqchip_fwid.name.
Signed-off-by: Suravee Suthikulpanit
---
include/linux/irqdomain.h | 1 +
kernel/irq/irqdomain.c| 18 ++
2 files changed, 19 insertions(+)
diff --git a/include/linux/irqdomain.h
This patch replaces the struct device_node with struct fwnode_handle
since this structure is common between DT and ACPI.
It also refactors gicv2m_init_one() to prepare for ACPI support.
There should be no functional changes.
Signed-off-by: Suravee Suthikulpanit
---
101 - 200 of 1788 matches
Mail list logo
