Incomplete vmcore file

2012-10-30 Thread Ritesh Majumdar
Hello, I am using kernel version 2.6.34.4 and trying to enable kernel crash using kexec (kdump). Every time the crash occurs, the size of the dump file (vmcore) is incomplete (around 20 MB).OS is installed with 8 GB of RAM. Due to this gdb/crash fails to analyze the core dump. Does anyone know wh

RE: [PATCH] omap2-clk: Add missing lcdc clock definition

2012-10-30 Thread Paul Walmsley
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 - > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-May/101987.html Ach, shoul

Re: [PATCH] tools: Allow tools to be installed in a user specified location

2012-10-30 Thread Len Brown
Applied. thanks, Len Brown, Intel Open Source Technology Center -- 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.kernel.org/majordomo-info.html Please read the FAQ at http://www.t

Re: [PATCH] ti_tscadc: Match mfd sub devices to regmap interface

2012-10-30 Thread Dmitry Torokhov
On Tue, Oct 30, 2012 at 09:41:00PM -0700, Russ Dill wrote: > On Wed, Oct 31, 2012 at 8:55 AM, Pantelis Antoniou > 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 ch

Re: [Patch v1 07/10] perf tools: add mem access sampling core support

2012-10-30 Thread Namhyung Kim
On Mon, 29 Oct 2012 16:15:49 +0100, Stephane Eranian wrote: > This patch adds the sorting and histogram support > functions to enable profiling of memory accesses. > > The following sorting orders are added: > - symbol_daddr: data address symbol (or raw address) > - dso_daddr: data address shared

Re: [PATCH] Input: select INPUT_MATRIXKMAP for lpc32xx-keys

2012-10-30 Thread Dmitry Torokhov
On Sat, Oct 27, 2012 at 09:40:48AM +0200, Roland Stigge wrote: > This patch adds a "select" dependency of KEYBOARD_LPC32XX on INPUT_MATRIXKMAP, > as the other drivers are doing in this regard. This fixes the following > compile > error if KEYBOARD_LPC32XX is enabled but INPUT_MATRIXKMAP is not: >

[PATCH 1/4, v4] AMD64 EDAC: Add multi-domain support to AMD EDAC

2012-10-30 Thread Daniel J Blueman
Fix the handling of memory controller detection to index the array of detected Northbridges, allowing memory controllers over multiple PCI domains in federated systems eg using Numascale's NumaConnect/ NumaChip. v4: Generate linear Northbridge ID by indexing detected Northbridges Signed-off-by: D

[PATCH 2/4] AMD64 EDAC: Add support for >255 memory controllers

2012-10-30 Thread Daniel J Blueman
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 Blueman --- drivers/edac/amd64_edac.c | 18 +- 1 file changed, 9 insertion

[PATCH 3/4] AMD64 EDAC: Cleanup type usage to be consistent

2012-10-30 Thread Daniel J Blueman
As the Northbridge IDs are at most 16-bits, use the same type consistently. Signed-off-by: Daniel J Blueman --- arch/x86/include/asm/amd_nb.h|2 +- arch/x86/include/asm/processor.h |2 +- arch/x86/kernel/cpu/amd.c|4 ++-- drivers/edac/amd64_edac.c| 26 ++

[PATCH 4/4] AMD64 EDAC: Use appropriate name for NB indexing

2012-10-30 Thread Daniel J Blueman
Use the same 'amd' prefix as related functions for clarity. Signed-off-by: Daniel J Blueman --- arch/x86/include/asm/amd_nb.h |2 +- drivers/edac/amd64_edac.c |6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/x86/include/asm/amd_nb.h b/arch/x86/include/as

Re: [PATCH 1/2] kfifo: round up the fifo size power of 2

2012-10-30 Thread 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 wrote: > > > Say, if we want to allocate a filo with size of 6 bytes, it would be safer > > to allocate 8 bytes instead of 4 bytes. > > > > ... > > > > --- a/kernel/kfifo.c > > +++ b/

Re: [Patch v1 08/10] perf report: add support for mem access profiling

2012-10-30 Thread Namhyung Kim
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 > --- [snip] > + cost = mi->cost; > + if (!cost) > +

Re: [PATCH V2 RFC 3/3] kvm: Check system load and handle different commit cases accordingly

2012-10-30 Thread Raghavendra K T
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 asymmet

RE: [PATCH 2/2] therma: exynos: Supports thermal tripping

2012-10-30 Thread Jonghwan Choi
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: Sup

RE: [PATCH] thermal: solve compilation errors in rcar_thermal

2012-10-30 Thread Zhang, Rui
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,

linux-next: Tree for Oct 31

2012-10-30 Thread Stephen Rothwell
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

[PATCH] perf: x86 filter_events() - use hw event id ?

2012-10-30 Thread Sukadev Bhattiprolu
>From c3b53a5733fdea35807f4513255bca05e3aee5c5 Mon Sep 17 00:00:00 2001 From: Sukadev Bhattiprolu 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 id_. But filter_events()

Re: [PATCH 1/2] kfifo: round up the fifo size power of 2

2012-10-30 Thread Stefani Seibold
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 wrote: > > > > > Say, if we want to allocate a filo with size of 6 bytes, it would be safer > > > to allocate 8 byt

Re: [PATCH v3] epoll: Support for disabling items, and a self-test app.

2012-10-30 Thread Michael Wang
On 10/26/2012 08:08 AM, Paton J. Lewis wrote: > From: "Paton J. Lewis" > > 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 related to an >

[PATCH] userns: Support fuse interacting with multiple user namespaces

2012-10-30 Thread Eric W. Biederman
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 communi

RE: [PATCH] omap2-clk: Add missing lcdc clock definition

2012-10-30 Thread Hiremath, Vaibhav
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 - > > http://lists.infrad

Re: [RFC][PATCH] perf: Add a few generic stalled-cycles events

2012-10-30 Thread Sukadev Bhattiprolu
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 su

Re: [PATCH V2 RFC 0/3] kvm: Improving undercommit,overcommit scenarios

2012-10-30 Thread Raghavendra K T
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

RE: [PATCH v2] Thermal: exynos: Add sysfs node supporting exynos's emulation mode.

2012-10-30 Thread R, Durgadoss
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.. >

[PATCH v2 2/2] therma: exynos: Supports thermal tripping

2012-10-30 Thread Jonghwan Choi
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 --- drivers/thermal/exynos_thermal.c |

[PATCH v2 1/2] thermal: exynos: Fix wrong bit to control tmu core

2012-10-30 Thread Jonghwan Choi
[0]bit is used to enable/disable tmu core. [1] bit is a reserved bit. Signed-off-by: Jonghwan Choi --- drivers/thermal/exynos_thermal.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/thermal/exynos_thermal.c b/drivers/thermal/exynos_thermal.c index fd03e85..6

Re: [PATCH 1/2] kfifo: round up the fifo size power of 2

2012-10-30 Thread Yuanhan Liu
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 wrote: > > > > > > > Say, if we want to al

Re: [PATCH 1/2] kfifo: round up the fifo size power of 2

2012-10-30 Thread Andrew Morton
On Wed, 31 Oct 2012 07:30:33 +0100 Stefani Seibold 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 > > > has

Re: [PATCH v3 0/3] zram/zsmalloc promotion

2012-10-30 Thread Minchan Kim
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 t

Re: [PATCH 2/2] mm/slob: Use free_page instead of put_page for page-size kmalloc allocations

2012-10-30 Thread Pekka Enberg
> 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 >> b

Re: [PATCH 1/3] mm/slob: Drop usage of page->private for storing page-sized allocations

2012-10-30 Thread Pekka Enberg
On Fri, Oct 19, 2012 at 1:41 AM, Ezequiel Garcia 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 store the allocated

Re: [Patch v1 10/10] perf tools: add new mem command for memory access profiling

2012-10-30 Thread Namhyung Kim
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

<    4   5   6   7   8   9