On Mon, 29 Oct 2012 16:15:50 +0100, Stephane Eranian wrote:
This patch adds the --mem-mode option to perf report.
This mode requires a perf.data file created with memory
access samples.
Signed-off-by: Stephane Eranian eran...@google.com
---
[snip]
+ cost = mi-cost;
+ if (!cost)
+
On 10/30/2012 01:44 PM, Peter Zijlstra wrote:
On Tue, 2012-10-30 at 11:27 +0530, Raghavendra K T wrote:
Okay, now IIUC, usage of *any* global measure is bad?
Yep, people like to carve up their machines, esp. now that they're
somewhat bigger than they used to be. This can result in very
Thanks.
Let me check.
-Original Message-
From: jonghwa3@samsung.com [mailto:jonghwa3@samsung.com]
Sent: Wednesday, October 31, 2012 2:06 PM
To: Jonghwan Choi
Cc: 'open list'; 'Amit Daniel Kachhap'; 'Zhang Rui'; 'Sachin Kamat'
Subject: Re: [PATCH 2/2] therma: exynos: Supports
Sorry, I can not see the original post of this patch.
Can you resend it so that I can apply it?
-Original Message-
From: kuninori morimoto [mailto:kuninori.morimoto...@gmail.com] On
Behalf Of Kuninori Morimoto
Sent: Wednesday, October 31, 2012 11:21 AM
To: Andrew Morton; Zhang, Rui;
Hi all,
Changes since 20121030:
The v4l-dvb tree still had its build failure so I used the version from
next-20121026.
The block tree gained a conflict against Linus' tree.
The arm-soc tree gained a conflict against the staging tree.
From c3b53a5733fdea35807f4513255bca05e3aee5c5 Mon Sep 17 00:00:00 2001
From: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
Date: Tue, 30 Oct 2012 23:05:05 -0700
Subject: [PATCH] perf: x86 filter_events() - use hw event id ?
The -event_map() operation expects to index through the _hardware event
Am Mittwoch, den 31.10.2012, 13:59 +0800 schrieb Yuanhan Liu:
On Mon, Oct 29, 2012 at 01:59:35PM -0700, Andrew Morton wrote:
On Fri, 26 Oct 2012 15:56:57 +0800
Yuanhan Liu yuanhan@linux.intel.com wrote:
Say, if we want to allocate a filo with size of 6 bytes, it would be safer
to
On 10/26/2012 08:08 AM, Paton J. Lewis wrote:
From: Paton J. Lewis pale...@adobe.com
It is not currently possible to reliably delete epoll items when using the
same epoll set from multiple threads. After calling epoll_ctl with
EPOLL_CTL_DEL, another thread might still be executing code
Use kuid_t and kgid_t in struct fuse_conn and struct fuse_mount_data.
The connection between between a fuse filesystem and a fuse daemon is
established when a fuse filesystem is mounted and provided with a file
descriptor the fuse daemon created by opening /dev/fuse.
For now restrict the
On Wed, Oct 31, 2012 at 11:19:44, Paul Walmsley wrote:
On Wed, 31 Oct 2012, Hiremath, Vaibhav wrote:
As far as lck clock node is concerned, we had deliberately dropped all leaf-
node clocks from the clock tree, please refer to the description mentioned
in -
Peter Zijlstra [pet...@infradead.org] wrote:
| On Tue, 2012-10-16 at 11:31 -0700, Sukadev Bhattiprolu wrote:
| On a side note, how does the kernel on x86 use the 'config' information in
| say /sys/bus/event_source/devices/cpu/format/cccr ? On Power7, the raw
| code encodes the information such
On 10/30/2012 05:47 PM, Andrew Theurer wrote:
On Mon, 2012-10-29 at 19:36 +0530, Raghavendra K T wrote:
In some special scenarios like #vcpu = #pcpu, PLE handler may
prove very costly, because there is no need to iterate over vcpus
and do unsuccessful yield_to burning CPU.
Similarly, when we
Hi,
Looks like a nice feature :-)
Without something like this, we had been spending time on
writing test drivers, to actually test our thermal framework code.
BTW, against which tree this patch was generated ?
Rui's -next or master or Linux-next ?
Some comments below, on a quick glance..
TMU urgently sends active-high signal (thermal trip) to PMU,
and thermal tripping by hardware logic i.e PMU is performed.
Thermal tripping means that PMU cut off the whole power of SoC
by controlling external voltage regulator.
Signed-off-by: Jonghwan Choi jhbird.c...@samsung.com
---
[0]bit is used to enable/disable tmu core. [1] bit is a reserved bit.
Signed-off-by: Jonghwan Choi jhbird.c...@samsung.com
---
drivers/thermal/exynos_thermal.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/thermal/exynos_thermal.c
On Wed, Oct 31, 2012 at 07:30:33AM +0100, Stefani Seibold wrote:
Am Mittwoch, den 31.10.2012, 13:59 +0800 schrieb Yuanhan Liu:
On Mon, Oct 29, 2012 at 01:59:35PM -0700, Andrew Morton wrote:
On Fri, 26 Oct 2012 15:56:57 +0800
Yuanhan Liu yuanhan@linux.intel.com wrote:
Say, if
On Wed, 31 Oct 2012 07:30:33 +0100 Stefani Seibold stef...@seibold.net wrote:
Yes, and I guess the same to give them a 64-element one.
If there's absolutely no prospect that the kfifo code will ever support
100-byte fifos then I guess we should rework the API so that the caller
On Tue, Oct 30, 2012 at 07:43:07PM -0700, Greg Kroah-Hartman wrote:
On Wed, Oct 31, 2012 at 11:39:48AM +0900, Minchan Kim wrote:
Greg, what do you think about LTSI?
Is it proper feature to add it? For it, still do I need ACK from mm
developers?
It's already in LTSI, as it's in the 3.4
On 10/22/2012 04:04 PM, Ezequiel Garcia wrote:
When freeing objects, the slob allocator currently free empty pages
calling __free_pages(). However, page-size kmallocs are disposed
using put_page() instead.
It makes no sense to call put_page() for kernel pages that are provided
by the object
On Fri, Oct 19, 2012 at 1:41 AM, Ezequiel Garcia elezegar...@gmail.com wrote:
This field was being used to store size allocation so it could be
retrieved by ksize(). However, it is a bad practice to not mark a page
as a slab page and then use fields for special purposes.
There is no need to
On Mon, 29 Oct 2012 16:15:52 +0100, Stephane Eranian wrote:
This new command is a wrapper on top of perf record and
perf report to make it easier to configure for memory
access profiling.
So this new command will be run only on speicific (PEBS 2?) Intel
machines, right? Is there anything we
Those functions are availabe only when CONFIG_GPIOLIB is set. So, we
should not call them under !CONFIG_GPIOLIB block.
This would fix following build errros:
include/asm-generic/gpio.h: In function 'gpio_get_value_cansleep':
include/asm-generic/gpio.h:220:2: error: implicit declaration of
There are 2 issues with current code:
1. redefinition of 'gpio_cansleep':
include/linux/gpio.h:60:19: error: redefinition of 'gpio_cansleep'
include/asm-generic/gpio.h:212:19: note: previous definition of 'gpio_cansleep'
was here
The root cause is include/linux/gpio.h has a defintion of it. And
At 10/30/2012 04:46 AM, David Rientjes Wrote:
On Mon, 29 Oct 2012, Lai Jiangshan wrote:
We have N_NORMAL_MEMORY for standing for the nodes that have normal memory
with
zone_type = ZONE_NORMAL.
And we have N_HIGH_MEMORY for standing for the nodes that have normal or high
memory.
(In
From: Lai Jiangshan la...@cn.fujitsu.com
This patch is part2 of the following patchset:
https://lkml.org/lkml/2012/10/29/319
Part1 is here:
https://lkml.org/lkml/2012/10/31/30
This patch only does some cleanup, and no logic change. It can be applied
without the other parts.
Lai
From: Lai Jiangshan la...@cn.fujitsu.com
use [index] = init_value
use N_x instead of hardcode.
Make it more readability and easier to add new state.
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
drivers/base/node.c | 20 ++--
1 file changed, 10 insertions(+), 10
Hi Ezequiel,
On Thu, Sep 27, 2012 at 8:49 AM, tip-bot for Ezequiel Garcia
elezegar...@gmail.com wrote:
Commit-ID: 8781915ad2716adcd8cd5cc52cee791fc8b00fdf
Gitweb: http://git.kernel.org/tip/8781915ad2716adcd8cd5cc52cee791fc8b00fdf
Author: Ezequiel Garcia elezegar...@gmail.com
I've renamed the topic.
On (10/30/12 20:55), Nitin Gupta wrote:
==
zram: Fix use-after-free in partial I/O case
When the compressed size of a page exceeds a threshold, the page is
stored as-is i.e. in uncompressed form. In the partial I/O i.e.
non-PAGE_SIZE'ed I/O case, however, the
On Wed, Oct 24, 2012 at 12:43 PM, Lai Jiangshan la...@cn.fujitsu.com wrote:
SLUB only fucus on the nodes which has normal memory, so ignore the other
node's hot-adding and hot-removing.
Aka: if some memroy of a node(which has no onlined memory) is online,
but this new memory onlined is not
Smatch is a C static analysis tool, but with a lot of kernel
specific checks. It's been 8 months since I did a Smatch release so
probably another one was due.
The main interesting thing right now is the value tracking across
function boundaries with the database. But also there was a some
work
On Tue, 30 Oct 2012 08:05:45 -0400, Dhaval Giani wrote:
On Tue, Oct 30, 2012 at 3:42 AM, Namhyung Kim namhy...@kernel.org wrote:
Hi Dhaval,
On Mon, 29 Oct 2012 12:45:53 -0400, Dhaval Giani wrote:
On Mon, Oct 29, 2012 at 12:01 PM, Dhaval Giani dhaval.gi...@gmail.com
wrote:
Hi,
As part of
On Wed, Oct 31, 2012 at 03:00:54PM +0800, Yuanhan Liu wrote:
There are 2 issues with current code:
1. redefinition of 'gpio_cansleep':
include/linux/gpio.h:60:19: error: redefinition of 'gpio_cansleep'
include/asm-generic/gpio.h:212:19: note: previous definition of
'gpio_cansleep' was here
On Tue, 30 Oct 2012 08:53:38 -0700, Arnaldo Carvalho de Melo wrote:
Em Tue, Oct 30, 2012 at 08:45:28AM -0600, David Ahern escreveu:
On 10/30/12 1:24 AM, Namhyung Kim wrote:
On Mon, 29 Oct 2012 10:31:41 -0600, David Ahern wrote:
stdio based implementations of ui_ based functions for the
On Wed, Oct 31, 2012 at 03:12:36PM +0800, Fengguang Wu wrote:
On Wed, Oct 31, 2012 at 03:00:54PM +0800, Yuanhan Liu wrote:
There are 2 issues with current code:
1. redefinition of 'gpio_cansleep':
include/linux/gpio.h:60:19: error: redefinition of 'gpio_cansleep'
When do code reviewing, found no special requirement to
use spin_lock_irqsave/spin_unlock_irqrestore, because
alarmtimer_get_rtcdev() is called by posix clock interface.
So would like to use mutex to replace it.
Signed-off-by: liu chuansheng chuansheng@intel.com
---
kernel/time/alarmtimer.c
Some posix clock interface directly use the variable rtcdev,
cleanup it here by alarmtimer_get_rtcdev().
Signed-off-by: liu chuansheng chuansheng@intel.com
---
kernel/time/alarmtimer.c | 13 ++---
1 files changed, 6 insertions(+), 7 deletions(-)
diff --git
Hi Greg,
On 30 October 2012 16:02, Greg Kroah-Hartman gre...@linuxfoundation.org wrote:
OK.
Greg, do these patches look OK to you to move to live under
drivers/mailbox?
Um, I don't know, I wasn't paying attention here, sorry.
As part of plat-omap code cleanup, I was planning to move
On Tue, 2012-10-30 at 23:40 -0700, Sukadev Bhattiprolu wrote:
So instead of the names I came up with in this patch,
stalled-cycles-fixed-point
we could use the name used in the CPU spec - 'cmplu_stall_fxu' in the arch
specific code ?
You could, but I would advise against it. Human readable
On Tue, 30 Oct 2012 10:01:10 +0100, Ingo Molnar wrote:
* Peter Zijlstra a.p.zijls...@chello.nl wrote:
On Tue, 2012-10-30 at 15:59 +0900, Namhyung Kim wrote:
Yes, the callchain part needs to be improved. Peter's idea
indeed looks good to me too.
FWIW, I think this is exactly what
When CONFIG_RTC_CLASS is not defined, implementing the POSIX clock
interface with null function is enough.
Signed-off-by: liu chuansheng chuansheng@intel.com
---
kernel/time/alarmtimer.c | 78 ++---
1 files changed, 59 insertions(+), 19 deletions(-)
Support to use ELM as BCH 4 8 bit error correction module. Also performance
enhancement by adding single shot read_page and write_page functions for the
nand flashes with page size less than 4 KB.
ELM module can be used to correct errors reported by BCH 4, 8 16 bit
ECC scheme. For now only 4 8
Update number of errors using nand ecc strength.
Also add macro definitions BCH8_ERROR_MAX BCH4_ERROR_MAX
Signed-off-by: Philip, Avinash avinashphi...@ti.com
---
:100644 100644 5c8978e... a02be29... M drivers/mtd/nand/omap2.c
drivers/mtd/nand/omap2.c | 12
1 files changed, 8
On Fri, 5 Oct 2012, Christoph Lameter wrote:
On Fri, 5 Oct 2012, Arnd Bergmann wrote:
Without this patch, building ARM collie_defconfig results in:
mm/slob.c: In function '__kmalloc_node':
mm/slob.c:431:152: warning: comparison of distinct pointer types lacks a
cast [enabled by
The ELM hardware module can be used to speedup BCH 4/8/16 ECC scheme
error correction.
For now only 4 8 bit support is added
Signed-off-by: Philip, Avinash avinashphi...@ti.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Rob Herring rob.herr...@calxeda.com
Cc: Rob Landley r...@landley.net
---
On Tue, 2012-10-30 at 20:45 -0700, Paul E. McKenney wrote:
This commit therefore adds the ability
for selected CPUs (rcu_nocbs= boot parameter) to have their
callbacks
offloaded to kthreads, inspired by Joe Korty's and Jim Houston's JRCU.
If the rcu_nocb_poll boot parameter is also specified,
ELM module can be used for hardware error correction of BCH 4 8 bit.
Also support read write page in one shot by adding custom read_page
write_page methods. This helps in optimizing code for NAND flashes with
page size less than 4 KB.
New structure member is_elm_used is added to know the
On Tue, 30 Oct 2012, Johannes Weiner wrote:
On Tue, Oct 30, 2012 at 02:29:25PM +0800, Zhouping Liu wrote:
On 10/29/2012 01:56 AM, Johannes Weiner wrote:
On Fri, Oct 26, 2012 at 11:08:00AM +0200, Peter Zijlstra wrote:
On Fri, 2012-10-26 at 17:07 +0800, Zhouping Liu wrote:
[ 180.918591]
tasklet_kill_immediate() is no longer used, just remove it.
Signed-off-by: Xiaotian Feng dannyf...@tencent.com
Cc: Thomas Gleixner t...@linutronix.de
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Paul E. McKenney paul...@linux.vnet.ibm.com
Cc: Andrew Morton a...@linux-foundation.org
Cc: Josh
On Saturday 27 October 2012, Michal Simek wrote:
diff --git a/arch/arm/include/asm/pgtable.h b/arch/arm/include/asm/pgtable.h
index 08c1231..72904a2 100644
--- a/arch/arm/include/asm/pgtable.h
+++ b/arch/arm/include/asm/pgtable.h
@@ -40,7 +40,7 @@
*/
#define VMALLOC_OFFSET
On Tuesday 30 October 2012, Michal Simek wrote:
On 10/29/2012 07:56 PM, Josh Cartwright wrote:
Suggested cleanup by Arnd Bergmann. Move the ttc timer.c code to
drivers/clocksource, and out of the mach-zynq directory.
The common.h (which only held the timer declaration) was renamed to
On Monday 29 October 2012, Richard Cochran wrote:
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
Don't get me wrong. If I had time for this it could be different.
Unfortunately IXP4xx is a legacy arch, and for me it's simply a hobby at
this point. Given the raised
Hi,
The container hotplug handler container_notify_cb() didn't implement
the hot-remove functionality. So, these 3 patches implement it like
the following way:
patch 1. Do not use kacpid_wq/kacpid_notify_wq to handle container hotplug
event,
use kacpi_hotplug_wq instead to avoid
As the comments in __acpi_os_execute() said:
We can't run hotplug code in keventd_wq/kacpid_wq/kacpid_notify_wq
because the hotplug code may call driver .remove() functions,
which invoke flush_scheduled_work/acpi_os_wait_events_complete
to flush these workqueues.
Hi Yinghai,
alloc_acpi_hp_work() just puts the hutplug work onto kacpi_hotplug_wq.
As mentioned by Toshi Kani, this job has been done in acpi_os_hotplug_execute().
So we should use it instead of alloc_acpi_hp_work().
This patch adds a acpi_hp_cb_data struct, which encapsulates the hotplug
event
This patch introduces a new function container_device_remove() to do
the container hot-remove job. It works like the following:
1. call acpi_bus_trim(device, 0) to stop the container device,
which means to unbind ACPI drivers first before remove devices.
(This feature is introduced by Lu
At Tue, 30 Oct 2012 20:34:00 +0100,
Ondrej Zary wrote:
On Wednesday 17 October 2012 08:57:39 Takashi Iwai wrote:
At Sun, 14 Oct 2012 21:09:23 +0200,
Ondrej Zary wrote:
set_pro_rate() is called from hw_params() but not from prepare(),
breaking running PCM on suspend/resume. Call it
On Tue, Oct 30, 2012 at 07:55:44PM +, Philippe Reynes wrote:
Hi Sascha,
+ osc26m {
+ compatible = fsl,imx-osc26m, fixed-clock;
+ clock-frequency = 33554432;
Is this really correct? The Datasheet specificies 26MHz, some boards
have 27Mhz, but 33?
On Thu, 25 Oct 2012, Kirill A. Shutemov wrote:
vec is 0x in virtio_pci__specific_io_out() on crash.
Let's add proper bounds checking there. It doesn't not solves the issue
with booting crashkernel, but fix lkvm crash.
There's no sign-off for the patch. Kirill, care to update the patch
On Wed, Oct 31, 2012 at 08:25:21AM +0100, Peter Zijlstra wrote:
On Tue, 2012-10-30 at 20:45 -0700, Paul E. McKenney wrote:
This commit therefore adds the ability
for selected CPUs (rcu_nocbs= boot parameter) to have their
callbacks
offloaded to kthreads, inspired by Joe Korty's and Jim
On 2012년 10월 31일 15:45, R, Durgadoss wrote:
Hi,
Looks like a nice feature :-)
Without something like this, we had been spending time on
writing test drivers, to actually test our thermal framework code.
Yes, fortunately, Exynos SOCs emulation mode makes our life better. ; )
BTW, against
From: Lai Jiangshan la...@cn.fujitsu.com
We have N_NORMAL_MEMORY for standing for the nodes that have normal memory with
zone_type = ZONE_NORMAL.
And we have N_HIGH_MEMORY for standing for the nodes that have normal or high
memory.
But we don't have any word to stand for the nodes that have
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Since we introduced N_MEMORY, we update
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Hi,
(Adding more people to CC.)
On Tue, Oct 16, 2012 at 2:17 PM, Matthieu CASTET
matthieu.cas...@parrot.com wrote:
From: Matthieu CASTET castet.matth...@free.fr
on cortexA8 (omap3) ralign is 64 and __alignof__(unsigned long long) is 8.
So we always disable debug.
This patch is based on
From: Lai Jiangshan la...@cn.fujitsu.com
update nodemasks management for N_MEMORY
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
Documentation/memory-hotplug.txt | 5 ++-
include/linux/memory.h | 1 +
mm/memory_hotplug.c | 87
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
From: Lai Jiangshan la...@cn.fujitsu.com
This patch is part3 of the following patchset:
https://lkml.org/lkml/2012/10/29/319
Part1 is here:
https://lkml.org/lkml/2012/10/31/30
Part2 is here:
http://marc.info/?l=linux-kernelm=135166705909544w=2
You can apply this patchset without
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
On 30.10.12 at 18:03, Olaf Hering o...@aepfle.de wrote:
On Tue, Oct 30, Jan Beulich wrote:
And iirc you're doing this relocation because otherwise the newly
booting kernel image may get overwritten at an (from its
perspective) arbitrary location. What I'm trying to point out is
that the
From: Lai Jiangshan la...@cn.fujitsu.com
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
(Adding Peter and Michael to CC.)
On Mon, Oct 29, 2012 at 12:49 PM, Glauber Costa glom...@parallels.com wrote:
We currently provide lockdep annotation for kmalloc caches, and also
caches that have SLAB_DEBUG_OBJECTS enabled. The reason for this is that
we can quite frequently nest in the
If tasklet_disable() is called before related tasklet handled,
tasklet_kill will never be finished. tasklet_kill is enough.
Signed-off-by: Xiaotian Feng dannyf...@tencent.com
Cc: Dmitry Torokhov dmitry.torok...@gmail.com
Cc: Tony Lindgren t...@atomide.com
Cc: Sourav Poddar sourav.pod...@ti.com
If tasklet_disable() is called before related tasklet handled,
tasklet_kill will never be finished. tasklet_kill is enough.
Signed-off-by: Xiaotian Feng dannyf...@tencent.com
Cc: Li Yang le...@freescale.com
Cc: Felipe Balbi ba...@ti.com
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
Cc:
If tasklet_disable() is called before related tasklet handled,
tasklet_kill will never be finished. tasklet_kill is enough.
Signed-off-by: Xiaotian Feng dannyf...@tencent.com
Cc: Jon Maloy jon.ma...@ericsson.com
Cc: Allan Stephens allan.steph...@windriver.com
Cc: David S. Miller
On 10/31/2012 05:41 AM, Russ Dill wrote:
On Wed, Oct 31, 2012 at 8:55 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
The MFD parent device now uses a regmap, instead of direct
memory access. Use the same method in the sub devices to avoid
nasty surprises.
Also rework the channel
From: Yanchuan Nian ycn...@gmail.com
The new layout pointer in pnfs_find_alloc_layout() may be NULL because of
out of memory. we must do some check work, otherwise pnfs_free_layout_hdr()
will go wrong because it can not deal with a NULL pointer.
Signed-off-by: Yanchuan Nian ycn...@gmail.com
---
On Wed, Oct 31, 2012 at 6:55 AM, Daniel J Blueman
dan...@numascale-asia.com wrote:
As the AMD64 last-level-cache ID is 16-bits and federated systems
eg using Numascale's NumaConnect/NumaChip can have more than 255 memory
controllers, use 16-bits to store the ID.
Signed-off-by: Daniel J
On 31/10/2012 16:18, Torsten Kaiser wrote:
On Wed, Oct 31, 2012 at 6:55 AM, Daniel J Blueman
dan...@numascale-asia.com wrote:
As the AMD64 last-level-cache ID is 16-bits and federated systems
eg using Numascale's NumaConnect/NumaChip can have more than 255 memory
controllers, use 16-bits to
On 10/31/2012 08:52 AM, Andrew Morton wrote:
On Wed, 31 Oct 2012 07:30:33 +0100 Stefani Seibold stef...@seibold.net wrote:
Yes, and I guess the same to give them a 64-element one.
If there's absolutely no prospect that the kfifo code will ever support
100-byte fifos then I guess we should
Commit c003ab1bedf0 ([media] rc-core: add separate defines for
protocol bitmaps and numbers) overlooked hid-picolcd.
This patch (against git.linuxtv.org/media_tree.git, branch
staging/for_v3.8) fixes the compilation breakage.
Signed-off-by: David Härdeman da...@hardeman.nu
---
On Fri, Oct 26, 2012 at 04:06:27PM +0200, Laurent Pinchart wrote:
Hi Thierry,
Thank you for the patch, and sorry for the late reply.
On Monday 15 October 2012 20:03:42 Thierry Reding wrote:
Platform device drivers usually use the driver-private data for their
own purposes. Having it
Hi Thierry,
On Wednesday 31 October 2012 09:26:07 Thierry Reding wrote:
On Fri, Oct 26, 2012 at 04:06:27PM +0200, Laurent Pinchart wrote:
On Monday 15 October 2012 20:03:42 Thierry Reding wrote:
Platform device drivers usually use the driver-private data for their
own purposes. Having it
On Tue, 2012-10-30 at 18:28 +, Olaf Hering wrote:
On Tue, Oct 30, Pasi Kärkkäinen wrote:
On Tue, Oct 30, 2012 at 05:05:05PM +0100, Olaf Hering wrote:
The XenPVHVM extensions have not been tested much on very old
hypervisors. At least Xen 3.4 gets some testing with the pvops kernel.
On Wednesday 31 October 2012 11:05:33 Ming Lei wrote:
On Wed, Oct 31, 2012 at 10:08 AM, Ming Lei ming@canonical.com wrote:
I am afraid it is, because a disk may just have been probed as the
deviceis being reset.
Yes, it is probable, and sounds like similar with 'root_wait' problem,
-Original Message-
From: Arnd Bergmann [mailto:a...@arndb.de]
Sent: Tuesday, October 30, 2012 11:22 PM
To: Michal Simek
Cc: Josh Cartwright; a...@kernel.org; linux-kernel@vger.kernel.org; linux-arm-
ker...@lists.infradead.org; John Linn; Nick Bowler; Russell King - ARM Linux
From: Devendra Naga develkernel412...@gmail.com
following were the errors reported
drivers/thermal/rcar_thermal.c: In function ‘rcar_thermal_probe’:
drivers/thermal/rcar_thermal.c:214:10: warning: passing argument 3 of
‘thermal_zone_device_register’ makes integer from pointer without a cast
Hi Omar,
On 10/31/2012 08:22 AM, Omar Ramirez Luna wrote:
As part of plat-omap code cleanup, I was planning to move omap-mailbox
framework to a newly drivers/mailbox folder, right now this code is
specific to OMAP platforms, but with some clean up it could be the
base for a generic
On Wednesday 31 October 2012 12:08 AM, Mark Brown wrote:
* PGP Signed by an unknown key
On Tue, Oct 30, 2012 at 12:34:05PM +0530, Laxman Dewangan wrote:
Tegra20/Tegra30 supports the spi interface through its SLINK
controller. Add spi driver for SLINK controller.
Applied, thanks.
Thank you
-Original Message-
From: Arnd Bergmann [mailto:a...@arndb.de]
Sent: Tuesday, October 30, 2012 11:37 PM
To: mon...@monstr.eu
Cc: Josh Cartwright; Michal Simek; linux-arm-ker...@lists.infradead.org;
linux-
ker...@vger.kernel.org; a...@kernel.org; Thomas Gleixner
Subject: Re:
As the AMD64 last-level-cache ID is 16-bits and federated systems
eg using Numascale's NumaConnect/NumaChip can have more than 255 memory
controllers, use 16-bits to store the ID.
v2: Avoid change to intlv_en variable
Signed-off-by: Daniel J Blueman dan...@numascale-asia.com
---
Hi,
[A big cut.]
+
+ mutex_lock(data-lock);
+ clk_enable(data-clk);
+
+ reg = readl(data-base + EXYNOS_EMUL_CON);
+ enable = reg EXYNOS_EMUL_ENABLE;
+ if (!enable !temp)
+ goto out;
I think you what you are trying to do here is this:
If the emulation is already
From: Lai Jiangshan la...@cn.fujitsu.com
This patch is part4 of the following patchset:
https://lkml.org/lkml/2012/10/29/319
Part1 is here:
https://lkml.org/lkml/2012/10/31/30
Part2 is here:
http://marc.info/?l=linux-kernelm=135166705909544w=2
Part3 is here:
From: Lai Jiangshan la...@cn.fujitsu.com
All are prepared, we can actually introduce N_MEMORY.
add CONFIG_MOVABLE_NODE make we can use it for movable-dedicated node
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
drivers/base/node.c | 6 ++
include/linux/nodemask.h | 4
1 - 100 of 1594 matches
Mail list logo
