Tomasz / Olof,
On Thu, May 9, 2013 at 2:45 AM, Tomasz Figa wrote:
>> Nothing stops you from doing that on your own. I tend to push back
>> onto the maintainers to get them engaged in their own housekeeping,
>> but anyone is free to :)
I will probably leave this to the maintainers at this
On Thu, May 9, 2013 at 6:08 PM, Linus Torvalds
wrote:
> On Wed, May 8, 2013 at 6:48 AM, Grant Likely wrote:
>>
>> * "git grep '\bGENERIC_GPIO\b'" should return 1 hit in the Chinese
>> documentation.
>
> That's the oddest command line I've seen in some time.
>
> You do realize that "git grep"
Jassi,
On 05/09/2013 12:48 PM, Jassi Brar wrote:
> On Thu, May 9, 2013 at 10:10 PM, Suman Anna wrote:
>> On 05/09/2013 11:41 AM, Jassi Brar wrote:
>>> On 9 May 2013 22:01, Suman Anna wrote:
Hi Jassi,
On 05/06/2013 02:24 AM, Jassi Brar wrote:
> +++
On Thu, May 9, 2013 at 5:52 PM, Saravana Kannan wrote:
> On 05/09/2013 04:50 AM, Grant Likely wrote:
>>
>> On Thu, May 9, 2013 at 11:07 AM, Ming Lei wrote:
>>>
>>> On Thu, May 9, 2013 at 1:18 PM, Saravana Kannan
>>> wrote:
The most obvious fallback of using late_initcall_sync()
Tony
On 05/08/2013 06:47 PM, Tony Lindgren wrote:
> * Dan Murphy [130418 11:35]:
>> On 04/18/2013 04:30 AM, Vincent Stehlé wrote:
>>> On 04/17/2013 10:16 PM, Dan Murphy wrote:
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
>>> (..)
diff --git
On Thu, 9 May 2013, Mel Gorman wrote:
> > I would be useful if the allocator would hand out pages from the
> > same physical area first. This would reduce fragmentation as well and
> > since it is likely that numerous pages are allocated for some purpose
> > (given that that the page sizes of 4k
On Tue, 7 May 2013 10:00:48 -0400 Jean-Francois Dagenais
wrote:
> V2: use the new bus_mutex
>
> extract from http://datasheets.maximintegrated.com/en/ds/DS2408.pdf:
>
> Power-up timing
> The DS2408 is sensitive to the power-on slew rate and can inadvertently
> power up with a test mode
On 5/9/2013 6:36 AM, Denis Efremov wrote:
> EXPORT_SYMBOL and inline directives are contradictory to each other.
> The patch fixes this inconsistency.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Denis Efremov
> ---
> arch/tile/lib/spinlock_32.c | 2 +-
>
On 5/9/2013 2:08 AM, Libo Chen wrote:
> When usb_create_hcd fail, we should call gxio_usb_host_destroy
>
> Signed-off-by: Libo Chen
> ---
> drivers/usb/host/ohci-tilegx.c |7 +--
> 1 files changed, 5 insertions(+), 2 deletions(-)
Thanks; taken into the tile tree. I also made the same
On Thu, May 9, 2013 at 10:10 PM, Suman Anna wrote:
> On 05/09/2013 11:41 AM, Jassi Brar wrote:
>> On 9 May 2013 22:01, Suman Anna wrote:
>>> Hi Jassi,
>>>
>>> On 05/06/2013 02:24 AM, Jassi Brar wrote:
+++ b/include/linux/mailbox_client.h
@@ -0,0 +1,85 @@
+/*
+ * This program
On Thu, May 09, 2013 at 01:38:36PM -0400, Alan Stern wrote:
> On Thu, 9 May 2013, Guenter Roeck wrote:
>
> > The following patch series introduces a marker for power management
> > functions
> > and data. This this marker, #ifdef CONFIG_PM and #ifdef CONFIG_PM_SLEEP
> > can be removed from most
On Thu, 9 May 2013, Guenter Roeck wrote:
> The following patch series introduces a marker for power management functions
> and data. This this marker, #ifdef CONFIG_PM and #ifdef CONFIG_PM_SLEEP
> can be removed from most of the code. This ensures that the conditional code
> still compiles but is
On Thu, May 09, 2013 at 08:41:49AM -0700, Dave Hansen wrote:
> On 05/08/2013 09:02 AM, Mel Gorman wrote:
> > So preliminary testing indicates the results are mixed bag. As long as
> > locks are not contended, it performs fine but parallel fault testing
> > hits into spinlock contention on the
On Tue, May 07, 2013 at 01:46:42PM -0700, Dave Hansen wrote:
> Michal, I figure you're the most logical person for these to go
> through.
>
> There is a fair amount of churn in the areas around these patches
> so I've resolved conflicts a couple of times. For the patches that
> are almost purely
On Thu, May 09, 2013 at 04:21:09PM +, Christoph Lameter wrote:
> On Thu, 9 May 2013, Mel Gorman wrote:
>
> > >
> > > The per cpu structure access also would not need to disable irq if the
> > > fast path would be using this_cpu ops.
> > >
> >
> > How does this_cpu protect against preemption
On Thu, 2013-05-09 at 14:44 +0900, Masami Hiramatsu wrote:
> Cleanup regex_lock and ftrace_lock locking points around
> ftrace_ops hash update code.
>
> The new rule is that regex_lock protects ops->*_hash
> read-update-write code for each ftrace_ops. Usually,
> hash update is done by following
On Thu, 2013-05-09 at 15:08 +0800, Li Zefan wrote:
> Cc: Naoya Horiguchi
>
> On 2013/5/9 12:35, Dave Jones wrote:
> > Just saw this on v3.9-11789-ge0fd9af while fuzz-testing.
> >
> > [ 163.917836] BUG: unable to handle kernel NULL pointer dereference at
> > 0008
> > [ 163.918984]
The following patch series introduces a marker for power management functions
and data. This this marker, #ifdef CONFIG_PM and #ifdef CONFIG_PM_SLEEP
can be removed from most of the code. This ensures that the conditional code
still compiles but is not included in the object file.
As a side
By marking power management functions and data with __pm, #ifdef CONFIG_PM
and #ifdef CONFIG_PM_SLEEP is no longer necessary in most cases.
This ensures that the power management code still compiles even if power
management is disabled, but does not consume space in the object file.
As a side
Drops #ifdef from code, and ensures that conditional code still compiles
if power management is disabled. Resulting code is dropped from object file.
Signed-off-by: Guenter Roeck
---
drivers/hwmon/max6639.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git
On 05/09/13 09:50, David Teigland wrote:
> On Thu, May 09, 2013 at 09:47:45AM +1000, Stephen Rothwell wrote:
>> [Just forwarding to David ...]
>>
>> On Wed, 08 May 2013 11:04:45 -0700 Randy Dunlap
>> wrote:
>>>
>>> on x86_64:
>>>
>>> when CONFIG_GFS2_FS_LOCKING_DLM=y and CONFIG_DLM=m:
>>>
>>>
With this change, code only needed is power management is active still
compiles if it is disabled, but does not consume space in the object file.
Signed-off-by: Guenter Roeck
---
drivers/hwmon/tmp102.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git
The following patch series introduces a marker for power management functions
and data. This this marker, #ifdef CONFIG_PM and #ifdef CONFIG_PM_SLEEP
can be removed from most of the code. This ensures that the conditional code
still compiles but is not included in the object file.
As a side
On Thu, 2013-05-09 at 12:34 -0400, Steven Rostedt wrote:
> On Thu, 2013-05-09 at 12:27 -0400, Steven Rostedt wrote:
>
> > We probably should have a better way to initialize this. As there are 26
> > ftrace_ops currently in the kernel (and this patch doesn't cover all of
> > them). Maybe have the
On Wed, May 8, 2013 at 6:48 AM, Grant Likely wrote:
>
> * "git grep '\bGENERIC_GPIO\b'" should return 1 hit in the Chinese
> documentation.
That's the oddest command line I've seen in some time.
You do realize that "git grep" is perfectly happy to just take the
"-w" flag exactly like normal
At Thu, 9 May 2013 16:43:28 +0800,
Ming Lei wrote:
>
> On Thu, May 9, 2013 at 3:31 PM, Takashi Iwai wrote:
> > At Thu, 9 May 2013 09:25:35 +0800,
> > Ming Lei wrote:
> >>
> >> On Thu, May 9, 2013 at 1:51 AM, Takashi Iwai wrote:
> >> >> In other words, the first patch is no essential part of the
Hello.
On 09-05-2013 6:35, Jongsung Kim wrote:
Removal of unused #define's is a matter of a separate cleanup patch...
Sorry. I won't touch them.
+static int rtl8201f_ack_interrupt(struct phy_device *phydev) {
+ int err;
+
+ err = phy_read(phydev, RTL8201F_ISR);
On 05/09/2013 04:50 AM, Grant Likely wrote:
On Thu, May 9, 2013 at 11:07 AM, Ming Lei wrote:
On Thu, May 9, 2013 at 1:18 PM, Saravana Kannan wrote:
The most obvious fallback of using late_initcall_sync() also doesn't work
since the deferred probing work initated during late_initcall() is
On Thu, May 09, 2013 at 09:47:45AM +1000, Stephen Rothwell wrote:
> [Just forwarding to David ...]
>
> On Wed, 08 May 2013 11:04:45 -0700 Randy Dunlap wrote:
> >
> > on x86_64:
> >
> > when CONFIG_GFS2_FS_LOCKING_DLM=y and CONFIG_DLM=m:
> >
> > fs/built-in.o: In function `gfs2_lock':
> >
On 05/09/2013 11:41 AM, Jassi Brar wrote:
> On 9 May 2013 22:01, Suman Anna wrote:
>> Hi Jassi,
>>
>> On 05/06/2013 02:24 AM, Jassi Brar wrote:
>>> +++ b/include/linux/mailbox_client.h
>>> @@ -0,0 +1,85 @@
>>> +/*
>>> + * This program is free software; you can redistribute it and/or modify
>>> +
Hi Linus,
Here are some fixes for v3.10. They're fairly minor but do fix
user-visible issues.
Bjorn
The following changes since commit ab86e974f04b1cd827a9c7c35273834ebcd9ab38:
Merge branch 'timers-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2013-04-30
Chao Xie writes:
> This patch have something wrong.
> 1.The pxa_sync_time API is not needed. The RTC sync can be done
> by user space applications, so in kernel this API is not needed.
> 2.The pxa_rtc_open can not be deleted. This change has been
> declined during review at the mail list
>
On 9 May 2013 22:01, Suman Anna wrote:
> Hi Jassi,
>
> On 05/06/2013 02:24 AM, Jassi Brar wrote:
>> +++ b/include/linux/mailbox_client.h
>> @@ -0,0 +1,85 @@
>> +/*
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public
The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git
tags/please-pull-pstore
for you to fetch changes up to
On Thu, May 9, 2013 at 3:14 PM, Russell King - ARM Linux
wrote:
> On Thu, May 09, 2013 at 02:50:17PM +0100, Mark Brown wrote:
>> On Thu, May 09, 2013 at 12:50:46PM +0100, Grant Likely wrote:
>>
>> > However, if a device that shuts down resources after init has
>> > completed and then cannot turn
Hi Jassi,
On 05/06/2013 02:24 AM, Jassi Brar wrote:
> +++ b/include/linux/mailbox_client.h
> @@ -0,0 +1,85 @@
> +/*
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free
Hi Suman,
On 9 May 2013 06:55, Suman Anna wrote:
>> so it can't be driven by the controller. We could make it a Kconfig option.
>> What do you suggest?
>
> I am saying controller/link because they are the ones that knows how the
> physical transport is, and it may vary from one to another. I
On Thu, 2013-05-09 at 12:27 -0400, Steven Rostedt wrote:
> We probably should have a better way to initialize this. As there are 26
> ftrace_ops currently in the kernel (and this patch doesn't cover all of
> them). Maybe have the first time its registered to initialize it.
Crap, but it can be
On Thu, 9 May 2013, Dave Hansen wrote:
> BTW, I really like the 'magazine' name. It's not frequently used in
> this kind of context and it conjures up a nice mental image whether it
> be of stacks of periodicals or firearm ammunition clips.
The term "magazine" was prominently used in the
On Thu, 2013-05-09 at 14:44 +0900, Masami Hiramatsu wrote:
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index 8a5c017..3f29b3d 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -64,9 +64,17 @@
>
> #define FL_GLOBAL_CONTROL_MASK (FTRACE_OPS_FL_GLOBAL |
It is a few instructions more efficent to and slightly more readable to use
this_rq()-> instead of cpu_rq(smp_processor_id()->
Cc: Ingo Molnar
Cc: Peter Zijlstra
Signed-off-by: Nathan Zimmer
---
kernel/sched/fair.c | 6 ++
kernel/sched/rt.c | 2 +-
2 files changed, 3 insertions(+), 5
On Thu, 9 May 2013, Mel Gorman wrote:
> >
> > The per cpu structure access also would not need to disable irq if the
> > fast path would be using this_cpu ops.
> >
>
> How does this_cpu protect against preemption due to interrupt? this_read()
> itself only disables preemption and it's explicitly
Linus, please pull from
git://git.infradead.org/~dwmw2/random-2.6.git for-linus-20130509
- Artem's removal of dead code continues (RPX, MBX860)
- Two krealloc() abuse fixes
This is some miscellaneous cleanups that don't really belong anywhere
else (or were ignored), that have been
Wang, All,
On Thu, May 09, 2013 at 11:27:31PM +0800, Wang YanQing wrote:
> On Mon, May 06, 2013 at 11:15:31PM +0200, Yann E. MORIN wrote:
> > From: "Yann E. MORIN"
> >
> > When searching for symbols, return the symbols sorted by relevance.
> >
> > Sorting is done as thus:
> > - first,
EUNBONG SONG reported a bug on MIPS64 platforms
caused by free_initmem() as below:
[ 132.134719] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW3.9.0+ #29
[ 132.141678] Stack : 0004 003f 80fa
802924a8
80fa
Lockdep is an awesome piece of code which detects locking issues
which are relevant both to userspace and kernelspace. We can
easily make lockdep work in userspace since there is really no
kernel spacific magic going on in the code.
All we need is to wrap two functions which are used by lockdep
kernel/lockdep.c deals with validating locking scenarios for
various architectures supported by the kernel. There isn't
anything kernel specific going on in lockdep, and when we
compare userspace to other architectures that don't have to deal
with irqs such as s390, they become all too similar.
This is a rather simple and basic test suite to test common
locking issues.
Beyond tests, it also shows how to use the library.
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/run_tests.sh | 27 +++
tools/lib/lockdep/tests/AA.c | 13 +
This is a simple wrapper to make using liblockdep on existing
applications much easier.
After running 'make && make install', it becomes quite simple to
test things with liblockdep. For example, to try it on perf:
lockdep perf
No other integration required.
Signed-off-by: Sasha Levin
A simple test to make sure we handle rwlocks correctly.
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/tests/WW.c | 13 +
1 file changed, 13 insertions(+)
create mode 100644 tools/lib/lockdep/tests/WW.c
diff --git a/tools/lib/lockdep/tests/WW.c b/tools/lib/lockdep/tests/WW.c
new
On Thu, May 09, 2013 at 02:36:43PM +0100, Russell King - ARM Linux wrote:
> On Thu, May 09, 2013 at 08:01:20AM -0500, Robin Holt wrote:
> > diff --git a/include/linux/reboot.h b/include/linux/reboot.h
> > index 26cf11b..bc77231 100644
> > --- a/include/linux/reboot.h
> > +++
Signed-off-by: Sasha Levin
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5f5c895..0c822ef 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4856,6 +4856,11 @@ F: drivers/lguest/
F: include/linux/lguest*.h
F: tools/lguest/
Both pthreads and lockdep support dealing with rwlocks, so
here's the liblockdep implementation for those.
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/include/liblockdep/rwlock.h | 91 +++
1 file changed, 91 insertions(+)
create mode 100644
This allows lockdep to be used without being compiled in the
original program.
Usage is quite simple:
LD_PRELOAD=/path/to/liblockdep.so /path/to/my/program
And magically, you'll have lockdep checking in your program!
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/preload.c | 384
These headers provide the same API as their pthread mutex
counterparts.
The design here is to allow to easily switch to liblockdep lock
validation just by adding a "liblockdep_" to pthread_mutex_*()
calls, which means that it's easy to integrate liblockdep into
existing codebases.
Signed-off-by:
liblockdep is a tiny wrapper built around kernel/lockdep.c. The aim is to
provide the same functionality the kernel gets from lockdep to userspace.
The bulk of the code here is the LD_PRELOAD support which provides users
an easy way to test their code without having to integrate liblockdep into
From: Zhang Yanfei
For some reason, comments below are lost:
- comments for init_range_memory_mapping()
- comments in init_mem_mapping that is helpful for reminding people
that the pagetable is setup top-down
The comments were written by Yinghai in his patch in
Change signature of free_reserved_area() according to Russell King's
suggestion to fix following build warnings:
arch/arm/mm/init.c: In function 'mem_init':
arch/arm/mm/init.c:603:2: warning: passing argument 1 of 'free_reserved_area'
makes integer from pointer without a cast [enabled by
On Thu, May 09, 2013 at 04:07:50PM +0100, Russell King - ARM Linux wrote:
> On Thu, May 09, 2013 at 03:37:02PM +0100, Mark Brown wrote:
> > That's clearly a "don't do that then" sort of thing; while we don't want
> > to be unhelpful there's no guarantees with this approach.
> That's not a "don't
On 05/08/2013 09:02 AM, Mel Gorman wrote:
> So preliminary testing indicates the results are mixed bag. As long as
> locks are not contended, it performs fine but parallel fault testing
> hits into spinlock contention on the magazine locks. A greater problem
> is that because CPUs share magazines
On Thu, 2013-05-09 at 10:47 -0400, Steven Rostedt wrote:
> > sh-2.05b# echo p vfs_symlink > kprobe_events
> > sh-2.05b# echo vfs_symlink:enable_event:kprobes:p_vfs_symlink_0 >
> > set_ftrace_filter
> >
> Ouch! I'm surprised I didn't trigger this in my tests. I have lockdep
> enabled, and I did
On 05/09/2013 06:56 AM, Norbert Preining wrote:
in the current state, that is release 3.9.0, but the same happened
in earlier kernels, this driver and/or NM is completely useless
at times. At times it just works, at times it does nothing.
In this case, now the 5th day in series ...
Nice long
On Thu, May 09, 2013 at 07:59:30AM +, EUNBONG SONG wrote:
>
> I got a message as below every time i ran iozone test.
>
>
> [ 4876.293124] [] show_stack+0x68/0x80
> [ 4876.309411] [] notifier_call_chain+0x5c/0xa8
> [ 4876.315245] [] __atomic_notifier_call_chain+0x3c/0x58
> [ 4876.321860] []
On 05/09/2013 11:05 AM, David Ahern wrote:
On 5/9/13 8:46 AM, Waiman Long wrote:
I am sorry that I forgot to rerun checkpatch.pl again after changing the
argument type from int to bool.
You can edit/create .git/hooks/pre-commit and have it run
checkpatch.pl so you don't forget:
#!/bin/bash
On Mon, May 06, 2013 at 11:15:31PM +0200, Yann E. MORIN wrote:
> From: "Yann E. MORIN"
>
> When searching for symbols, return the symbols sorted by relevance.
>
> Sorting is done as thus:
> - first, symbols with a prompt, [1]
> - then, smallest offset, [2]
> - then, shortest
On Thu, May 09, 2013 at 05:07:44PM +0200, Peter Zijlstra wrote:
> On Thu, May 09, 2013 at 03:32:15PM +0200, Jiri Olsa wrote:
> > hi,
> > adding sysfs attribute to specify the maximum allowed value
> > for perf_event_attr::precise_ip field.
> >
> > Adding functionality for simple 'p' modifier and
On Wed, May 08, 2013 at 06:41:58PM +, Christoph Lameter wrote:
> On Wed, 8 May 2013, Mel Gorman wrote:
>
> > 1. IRQs do not have to be disabled to access the lists reducing IRQs
> >disabled times.
>
> The per cpu structure access also would not need to disable irq if the
> fast path
On Thu, May 09, 2013 at 01:55:04PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (arm defconfig)
> produced this warning:
>
> ipc/shm.c: In function 'newseg':
> ipc/shm.c:494:18: warning: unused variable 'hs' [-Wunused-variable]
>
>
On 05/08/2013 09:03 AM, Mel Gorman wrote:
> @@ -368,10 +375,9 @@ struct zone {
>
> /*
>* Keep some order-0 pages on a separate free list
> - * protected by an irq-unsafe lock
> + * protected by an irq-unsafe lock.
>*/
> - spinlock_t
On Thu, 2013-05-09 at 14:44 +0900, Masami Hiramatsu wrote:
> Return 0 instead of the number of activated ftrace if
> event_enable_func succeeded and return an error code if failed,
> beacuse 0 is success code at caller (ftrace_regex_write).
>
> Without this fix, writing enable_event trigger on
Disabling the interrupt line could miss an IRQ and leave the line into a
low state hence locking the driver.
Signed-off-by: David Hauweele
---
drivers/net/ieee802154/mrf24j40.c |7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/net/ieee802154/mrf24j40.c
The transceiver may fail under heavy traffic when a frame is transmitted
while receiving another frame.
This patch uses a mutex to separate the transmission and reception of
frames along with a secondary working queue to avoid a deadlock while
waiting for the transmission interrupt.
On Thu, May 09, 2013 at 07:31:18AM -0400, Peter Hurley wrote:
> On 05/08/2013 04:45 PM, Greg KH wrote:
> >On Wed, May 08, 2013 at 04:37:14PM -0400, Peter Hurley wrote:
> >>On 05/08/2013 04:14 PM, Greg KH wrote:
> >>>On Wed, May 08, 2013 at 03:56:49PM -0400, Peter Hurley wrote:
> On 05/08/2013
Add the IMG Debug Adapter File System (DAFS) for metag, which uses
SWITCH operations to communicate with a file server on a host computer
via a JTAG debug adapter.
Signed-off-by: James Hogan
Cc: Alexander Viro
---
v8:
* enabled building as a module (commit e605ff8 merged during v3.10
On Thu, 2013-05-09 at 10:31 -0400, Steven Rostedt wrote:
> > diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> > index 53582e9..44ac836 100644
> > --- a/kernel/trace/trace_events.c
> > +++ b/kernel/trace/trace_events.c
> > @@ -2061,8 +2061,11 @@ event_enable_func(struct
On Thu, May 09, 2013 at 09:52:47AM -0400, Richard Guy Briggs wrote:
> On Thu, May 09, 2013 at 09:29:18AM -0400, Steve Grubb wrote:
> > On Tuesday, April 16, 2013 03:38:23 PM Richard Guy Briggs wrote:
> > > On Tue, Apr 09, 2013 at 02:39:32AM -0700, Eric W. Biederman wrote:
> > > > Andrew Morton
On Thu, May 09, 2013 at 03:32:15PM +0200, Jiri Olsa wrote:
> hi,
> adding sysfs attribute to specify the maximum allowed value
> for perf_event_attr::precise_ip field.
>
> Adding functionality for simple 'p' modifier and 'precise' term
> to get the maximum allowed value for
On Thu, May 09, 2013 at 03:37:02PM +0100, Mark Brown wrote:
> On Thu, May 09, 2013 at 03:14:45PM +0100, Russell King - ARM Linux wrote:
> > On Thu, May 09, 2013 at 02:50:17PM +0100, Mark Brown wrote:
>
> > > Even if the driver copes fine it can still be desirable to avoid the
> > > power down/up
On 5/9/13 8:46 AM, Waiman Long wrote:
I am sorry that I forgot to rerun checkpatch.pl again after changing the
argument type from int to bool.
You can edit/create .git/hooks/pre-commit and have it run checkpatch.pl
so you don't forget:
#!/bin/bash
exec git diff --cached |
Ceph's encode_caps_cb() worked hard to not call __page_cache_alloc while
holding a lock, but it's spoiled because ceph_pagelist_addpage() always
calls kmap(), which might sleep. Here's the result:
[13439.295457] ceph: mds0 reconnect start
[13439.300572] BUG: sleeping function called from invalid
On 09/05/13 15:51, Arnd Bergmann wrote:
> It won't.
>
>> > Looking at the code in clocksource_of_init it just goes through the
>> > of_device_id table, which is not used in case of non-DT.
> All new platforms are DT-only, and none of the old platforms use this
> driver, so it does not matter.
>
This commit moves the balloon_lock mutex out of the fill_balloon()
and leak_balloon() functions to their callers.
The reason for this change is that the next commit will introduce
a shrinker callback for the balloon driver, which will also call
leak_balloon() but will require different locking
Automatic ballooning consists of dynamically adjusting the guest's
balloon according to memory pressure in the host and in the guest.
This commit implements the guest side of automatic balloning, which
basically consists of registering a shrinker callback with the kernel,
which will try to
Hi,
This series is a respin of automatic ballooning support I started
working on last year. Patch 2/2 contains all relevant technical
details and performance measurements results.
This is in RFC state because it's a work in progress.
Here's some information if you want to try automatic
On Thu, May 09, 2013 at 06:29:51PM +0800, Dave Young wrote:
> On Tue, May 07, 2013 at 03:25:58AM -0400, CAI Qian wrote:
> > Never saw any of those messages were floating in any of the RC testing, but
> > now happened in 3.9 GA on Power 7 systems.
> >
> > [0.329753] EEH: devices created
> > [
On 07-05-2013 09:01, Amit Daniel Kachhap wrote:
> This patch adds support to handle multiple instances of the TMU controllers.
> This is done by removing the static structure to register with the core
> thermal
> and creating it dynamically for each instance of the TMU controller. The
> interrupt
On 09/05/13 15:40, Mark Brown wrote:
> So what exactly is the driver doing then? If the register maps look
> nothing like each other then what's the common functionality the driver
> is providing?
What I meant here is that, sysconf registers are reassigned per SOC, so
the sysconf register
On Thursday 09 May 2013, Srinivas KANDAGATLA wrote:
> >> diff --git a/arch/arm/include/asm/global_timer.h
> >> b/arch/arm/include/asm/global_timer.h
> >> new file mode 100644
> >> index 000..46f9188
> >> --- /dev/null
> >> +++ b/arch/arm/include/asm/global_timer.h
> >> @@ -0,0 +1,12 @@
> >>
On Thu, 9 May 2013, Anthony Olech wrote:
> Hi Guennadi,
>
> without trying to step on our marketing department's toes, I can only
> suggest that you slurp the online archives of the LKML and ALSA mailing
> list.
> The Linux Kernel Mailing List archive that I use is:
>
Hey Amit,
On 07-05-2013 09:01, Amit Daniel Kachhap wrote:
> This patch modifies TMU controller to add changes needed to work with
> exynos5440 platform. Also register definitions and required configuration data
> are added. This sensor registers 3 instance of the tmu controller with the
> thermal
On Thu, 2013-05-09 at 14:44 +0900, Masami Hiramatsu wrote:
> Fix a deadlock on ftrace_regex_lock which happens when setting
> an enable_event trigger on dynamic kprobe event as below.
>
>
> sh-2.05b# echo p vfs_symlink > kprobe_events
> sh-2.05b# echo
On 05/09/2013 06:19 AM, Jiri Olsa wrote:
On Wed, May 08, 2013 at 11:44:35AM -0400, Waiman Long wrote:
On 05/07/2013 05:30 AM, Jiri Olsa wrote:
On Mon, May 06, 2013 at 09:43:53AM -0400, Waiman Long wrote:
When "perf record" was used on a large machine with a lot of CPUs,
the perf
On 05/09/2013 03:08 AM, Li Zefan wrote:
Cc: Naoya Horiguchi
On 2013/5/9 12:35, Dave Jones wrote:
Just saw this on v3.9-11789-ge0fd9af while fuzz-testing.
[ 163.917836] BUG: unable to handle kernel NULL pointer dereference at
0008
[ 163.918984] IP: [] newseg+0x10d/0x390
The
On 07-05-2013 09:01, Amit Daniel Kachhap wrote:
> TMU probe function now checks for a device tree defined regulator.
> For compatibility reasons it is allowed to probe driver even without
> this regulator defined.
>
> Signed-off-by: Lukasz Majewski
> Signed-off-by: Kyungmin Park
>
When "perf record" was used on a large machine with a lot of CPUs,
the perf post-processing time (the time after the workload was done
until the perf command itself exited) could take a lot of minutes
and even hours depending on how large the resulting perf.data file was.
While running AIM7
On Thu, May 09, 2013 at 03:08:15PM +0800, Li Zefan wrote:
> Cc: Naoya Horiguchi
>
> On 2013/5/9 12:35, Dave Jones wrote:
> > Just saw this on v3.9-11789-ge0fd9af while fuzz-testing.
> >
> > [ 163.917836] BUG: unable to handle kernel NULL pointer dereference at
> > 0008
> > [
Hi Guennadi,
without trying to step on our marketing department's toes, I can only suggest
that you slurp the online archives of the LKML and ALSA mailing list.
The Linux Kernel Mailing List archive that I use is:
http://lkml.indiana.edu/hypermail/linux/kernel
The ALSA mailing list archive that
On Thu, May 09, 2013 at 03:00:16PM +0100, Srinivas KANDAGATLA wrote:
> Some of layouts of the sysconf registers are totally changed for each SOC.
> Looking at driver by driver maybe some drivers can take advantage of the
> patterns, but Am not sure if this will be a sustainable solution for all
On 05/08/2013 08:18 PM, Leonid Yegoshin wrote:
Page 'new' during MIGRATION can't be flushed by flush_cache_page().
Using flush_cache_page(vma, addr, pfn) is justified only if
page is already placed in process page table, and that is done right
after flush_cache_page(). But without it the arch
On Thu, May 09, 2013 at 03:14:45PM +0100, Russell King - ARM Linux wrote:
> On Thu, May 09, 2013 at 02:50:17PM +0100, Mark Brown wrote:
> > Even if the driver copes fine it can still be desirable to avoid the
> > power down/up cycle if it involves some user visible effect - things
> > like
401 - 500 of 1402 matches
Mail list logo
