On 02/18/2013 10:01 PM, Steven Rostedt wrote:
> On Mon, 2013-02-18 at 21:51 +0530, Srivatsa S. Bhat wrote:
>> Hi Michel,
>
>> Yes.. I don't think we can avoid that. Moreover, since we _want_ unfair
>> reader/writer semantics to allow flexible locking rules and guarantee
>> deadlock-safety, having
Hi Boris, Hi Rui,
@Rui, would be great, if you could review the patch and verify, whether
everything I'm telling is the truth, thanks.
Borislav Petkov writes:
On Sun, Feb 17, 2013 at 04:41:57PM +0100, Peter Feuerer wrote:
Don't think so, I think this was already in since 2.6. and
I assume
On 02/18/2013 09:53 PM, Michel Lespinasse wrote:
> On Mon, Feb 18, 2013 at 8:39 PM, Srivatsa S. Bhat
> wrote:
>> Some important design requirements and considerations:
>> -
[...]
>> +/*
>> + * Invoked by atomic hotplug reader (a task which wants
2013/2/5 Michael Wolf :
> In the case of where you have a system that is running in a
> capped or overcommitted environment the user may see steal time
> being reported in accounting tools such as top or vmstat. This can
> cause confusion for the end user.
Sorry, I'm no expert in this area. But
Steven Rostedt wrote:
> On Mon, 2013-02-18 at 12:39 +1100, Amnon Shiloh wrote:
> > Hello,
> >
> > The code in "kernel/sys.c" provides the "prctl(PR_SET_MM)" function,
> > which is the only way a process can set or modify the following 11
> > per-process fields:
> >
> > start_code, end_code,
On 02/18/2013 09:21 PM, Michel Lespinasse wrote:
> On Mon, Feb 18, 2013 at 8:39 PM, Srivatsa S. Bhat
> wrote:
>> @@ -200,6 +217,16 @@ void percpu_write_lock_irqsave(struct percpu_rwlock
>> *pcpu_rwlock,
>>
>> smp_mb(); /* Complete the wait-for-readers, before taking the lock */
>>
On Fri 15-02-13 14:22:19, Andrew Morton wrote:
> On Fri, 15 Feb 2013 17:57:10 +0100
> Jan Kara wrote:
>
> > A CPU can be caught in console_unlock() for a long time (tens of seconds are
> > reported by our customers) when other CPUs are using printk heavily and
> > serial
> > console makes
On Mon, 2013-02-18 at 21:51 +0530, Srivatsa S. Bhat wrote:
> Hi Michel,
> Yes.. I don't think we can avoid that. Moreover, since we _want_ unfair
> reader/writer semantics to allow flexible locking rules and guarantee
> deadlock-safety, having a recursive reader side is not even an issue, IMHO.
On 19/02/13 00:12, Lai Jiangshan wrote:
Core patches are patch 1, patch 9, patch 13
Patch 1: enhance locking
Patch 9: recorde worker id to work->data instead of pool id
lookup worker via worker ID if offq
Patch 13:also lookup worker via worker ID if running&,
remove lookup via
On 02/10/2013 06:58 AM, Len Brown wrote:
> From: Len Brown
>
> pm_idle is dead code on blackfin.
>
> Signed-off-by: Len Brown
> Cc: uclinux-dist-de...@blackfin.uclinux.org
> ---
> arch/blackfin/kernel/process.c | 7 ---
> 1 file changed, 7 deletions(-)
>
> diff --git
Commit-ID: 5dae63c442131f1b0a66abd43fdc861031f13ca6
Gitweb: http://git.kernel.org/tip/5dae63c442131f1b0a66abd43fdc861031f13ca6
Author: Yuanhan Liu
AuthorDate: Fri, 1 Feb 2013 18:59:16 +0800
Committer: Ingo Molnar
CommitDate: Mon, 18 Feb 2013 10:10:21 +0100
rwsem-spinlock: Implement
Commit-ID: 20bf062c6575e162ede00308ca3a5714ca112009
Gitweb: http://git.kernel.org/tip/20bf062c6575e162ede00308ca3a5714ca112009
Author: Alexander Holler
AuthorDate: Sat, 16 Feb 2013 16:38:17 +0100
Committer: Ingo Molnar
CommitDate: Mon, 18 Feb 2013 09:28:42 +0100
x86/memtest: Shorten
Hi Michel,
On 02/18/2013 09:15 PM, Michel Lespinasse wrote:
> Hi Srivasta,
>
> I admit not having followed in detail the threads about the previous
> iteration, so some of my comments may have been discussed already
> before - apologies if that is the case.
>
> On Mon, Feb 18, 2013 at 8:38 PM,
On Mon, Feb 18, 2013 at 8:39 PM, Srivatsa S. Bhat
wrote:
> Some important design requirements and considerations:
> -
>
> 1. Scalable synchronization at the reader-side, especially in the fast-path
>
>Any synchronization at the atomic
I might be able to get my hands on a T43 later this week and see if I can
reproduce this. This patch seems more plausible, at least... but still
puzzling.
Jonas Heinrich wrote:
>On 02-17 21:40, Rafael J. Wysocki wrote:
>> Does the commit immediately preceding this one behave correctly?
From: Hugh Dickins
On architectures where a pgd entry may be shared between user and kernel
(ARM+LPAE), freeing page tables needs a ceiling other than 0. This patch
introduces a generic USER_PGTABLES_CEILING that arch code can override.
Signed-off-by: Hugh Dickins
[catalin.mari...@arm.com:
Following feedback on the previous patch to limit the free_pgtables()
ceiling, this series introduces a USER_PGTABLES_CEILING macro defaulting
to 0 and an ARM-specific definition to TASK_SIZE.
Catalin Marinas (1):
arm: Set the page table freeing ceiling to TASK_SIZE
Hugh Dickins (1):
mm:
ARM processors with LPAE enabled use 3 levels of page tables, with an
entry in the top level (pgd) covering 1GB of virtual space. Because of
the branch relocation limitations on ARM, the loadable modules are
mapped 16MB below PAGE_OFFSET, making the corresponding 1GB pgd shared
between kernel
Every time, when we need to find the executing worker from work,
we need 2 steps:
find the pool from the idr by pool id.
find the worker from the hash table of the pool.
Now we merge them as one step: find the worker directly from the idr by worker
ID.
(lock_work_pool(). If the
When a work is dequeued via try_to_grab_pending(), its pool id is recored
in work->data. but this recording is useless when the work is not running.
In this patch, we only record pool id when the work is running.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 11 +--
1 files
Add new worker->id which is allocated from worker_idr. This
will be used to record the last running worker in work->data.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 28
kernel/workqueue_internal.h |1 +
2 files changed, 29 insertions(+), 0
Allow we use delayed_flags only in different path in later patches.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 7ac6824..cdd5523 100644
--- a/kernel/workqueue.c
We plan to only set rescuer->pool in the C.S. of pool->lock,
so when worker_maybe_bind_and_lock() is called, the worker(rescuer)->pool
may NULL. Thus we need to change the worker_maybe_bind_and_lock() API,
we need to add a @pool argument to it or use @pool argument instead of
@worker argument. we
We ensure these semantics:
worker->pool is set to pool if the worker is associated to the pool.
(normal worker is associated to its pool when created,
rescuer is associated to a pool dynamically.)
worker->pool is set to NULL if the worker is
Use already-known "cwq" instead of get_work_cwq(work) in try_to_grab_pending()
and cwq_activate_first_delayed().
It avoid unneeded calls to get_work_cwq() which becomes not so light-way
in later patches.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 11 +--
1 files changed, 5
Since we don't use the hashtable, thus we can use list to implement
the for_each_busy_worker().
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 27 ++-
kernel/workqueue_internal.h |9 +++--
2 files changed, 13 insertions(+), 23 deletions(-)
diff
pool->busy_list is touched when the worker processes every work.
if this code is moved out, we reduce this touch.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index
Current, we always record cwq in work->data if the work is queued.
Even the work is running at the same time. It requires us to use hash table
to lookup the worker.
If we record the worker ID is work->data even the work is queued, we can
remove this hash table lookup:
in lock_work_pool(),
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index cdd5523..ab5c61a 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -544,9 +544,11 @@ static inline unsigned
worker_maybe_bind_and_lock() uses both @task and @current and the same time,
they are the same(worker_maybe_bind_and_lock() can only be called by current
worker task)
We make it uses @current only.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c |7 +++
1 files changed, 3
We will use worker->id for global worker id.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 20 +++-
kernel/workqueue_internal.h |2 +-
2 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index
color bits is not used when offq, so we reuse them for pool IDs.
thus we will have more pool IDs.
Signed-off-by: Lai Jiangshan
---
include/linux/workqueue.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/workqueue.h b/include/linux/workqueue.h
index
get_work_pool() is too weak, the caller *always* has to lock and check.
We merge all the code and name it lock_work_pool() and remove get_work_pool().
This patch has a little overhead for __queue_work() and try_to_grab_pending():
Even worker_pool_by_id(pool_id) == get_cwq(cpu, wq)->pool,
Core patches are patch 1, patch 9, patch 13
Patch 1: enhance locking
Patch 9: recorde worker id to work->data instead of pool id
lookup worker via worker ID if offq
Patch 13:also lookup worker via worker ID if running&,
remove lookup via hashtable
Patch 6-8: ensure modification
From: Vivek Goyal
Subject: Re: [PATCH 05/13] vmcore: modify ELF32 code according to new type
Date: Fri, 15 Feb 2013 10:30:48 -0500
> On Thu, Feb 14, 2013 at 07:12:10PM +0900, HATAYAMA Daisuke wrote:
>> On elf32 mmap() is not supported. All vmcore objects are in old
>> memory.
>
> This is odd.
Remove hypervisor-only socket option.
Reported-by: Gerd Hoffmann
Acked-by: Dmitry Torokhov
Signed-off-by: Andy King
---
include/uapi/linux/vm_sockets.h |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/include/uapi/linux/vm_sockets.h
> -Original Message-
> From: geert.uytterhoe...@gmail.com
> [mailto:geert.uytterhoe...@gmail.com] On Behalf Of Geert Uytterhoeven
> Sent: Monday, February 18, 2013 5:29 AM
> To: Haiyang Zhang
> Cc: florianschandi...@gmx.de; linux-fb...@vger.kernel.org; KY Srinivasan;
> o...@aepfle.de;
Allow our own family as the protocol value for socket creation.
Reported-by: Gerd Hoffmann
Signed-off-by: Andy King
---
net/vmw_vsock/af_vsock.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index c1b9e55..ca511c4
From: Dmitry Torokhov
This is the default behavior for a looong time.
Acked-by: Andy King
Signed-off-by: Dmitry Torokhov
---
net/vmw_vsock/af_vsock.c |2 --
net/vmw_vsock/vmci_transport.c |2 --
2 files changed, 0 insertions(+), 4 deletions(-)
diff --git
From: Dmitry Torokhov
There isn't really a need to have a separate file for it.
Acked-by: Andy King
Signed-off-by: Dmitry Torokhov
---
net/vmw_vsock/af_vsock.c |3 +--
net/vmw_vsock/vsock_version.h | 22 --
2 files changed, 1 insertions(+), 24 deletions(-)
Minor vSockets fixes, two of which were reported on LKML.
Andy King (2):
VSOCK: Remove hypervisor-only socket option
VSOCK: Don't reject PF_VSOCK protocol
Dmitry Torokhov (2):
VSOCK: get rid of EXPORT_SYMTAB
VSOCK: get rid of vsock_version.h
include/uapi/linux/vm_sockets.h |8
From: Vivek Goyal
Subject: Re: [PATCH 04/13] vmcore: introduce types for objects copied in 2nd
kernel
Date: Fri, 15 Feb 2013 10:28:28 -0500
> On Thu, Feb 14, 2013 at 07:12:05PM +0900, HATAYAMA Daisuke wrote:
>> Some parts of old memory need to be copied in buffers on 2nd kernel to
>> be
On Monday 18 February 2013, Alexander Shiyan wrote:
> diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
> index 4a7ed5a..3c0abcb 100644
> --- a/drivers/mfd/syscon.c
> +++ b/drivers/mfd/syscon.c
Hi Alexander,
> struct regmap *syscon_regmap_lookup_by_compatible(const char *s)
> {
>
From: Vivek Goyal
Subject: Re: [PATCH 02/13] vmcore: round up buffer size of ELF headers by
PAGE_SIZE
Date: Fri, 15 Feb 2013 10:18:21 -0500
> On Thu, Feb 14, 2013 at 07:11:54PM +0900, HATAYAMA Daisuke wrote:
>> To satisfy mmap() page-size boundary requirement, reound up buffer
>> size of ELF
On 02/18/13 01:39, Jiri Kosina wrote:
> On Thu, 14 Feb 2013, Paul Gortmaker wrote:
>
>> It seems there are about 80 new, but undocumented addtions at
>> the top level Documentation directory. This fixes up the top
>> level 00-INDEX by adding new entries and deleting a couple orphans.
>> Some
On Sun, Feb 17, 2013 at 10:02:11PM +0100, Frederic Weisbecker wrote:
> 2013/2/17 Frederic Weisbecker :
> > 2013/2/17 Linus Torvalds :
> >> On Sun, Feb 17, 2013 at 7:11 AM, Frederic Weisbecker
> >> wrote:
> >>>
> >>> preempt_value_in_interrupt() looks buggy in your patch: it makes
> >>>
Hi,
On Mon, Feb 18, 2013 at 07:50:12AM -0800, Greg KH wrote:
> > If it helps in any way, I have printed below only the filenames
> > (without path) so I could pipe it through uniq:
> >
> > act_mask
> > audit
> > autosuspend_delay_ms
> > bind
>
> This one the driver core creates, I'll fix that
On Mon, Feb 18, 2013 at 8:39 PM, Srivatsa S. Bhat
wrote:
> @@ -200,6 +217,16 @@ void percpu_write_lock_irqsave(struct percpu_rwlock
> *pcpu_rwlock,
>
> smp_mb(); /* Complete the wait-for-readers, before taking the lock */
> write_lock_irqsave(_rwlock->global_rwlock, *flags);
> +
Hugh,
On Thu, Feb 14, 2013 at 09:24:09PM +, Hugh Dickins wrote:
> On Wed, 13 Feb 2013, Andrew Morton wrote:
> > On Wed, 13 Feb 2013 11:39:29 +
> > Catalin Marinas wrote:
> >
> > > ARM processors with LPAE enabled use 3 levels of page tables, with an
> > > entry in the top level (pgd)
On Mon, Feb 18, 2013 at 05:33:16PM +0200, Felipe Balbi wrote:
> Hi folks,
>
> there are today a number of SYSFS files with read permission set but
> can't really be read (tried with normal user and root). To make things
> simpler, I wrote a simple ruby script (see below) to check if the file
> is
Hi Srivasta,
I admit not having followed in detail the threads about the previous
iteration, so some of my comments may have been discussed already
before - apologies if that is the case.
On Mon, Feb 18, 2013 at 8:38 PM, Srivatsa S. Bhat
wrote:
> Reader-writer locks and per-cpu counters are
On Fri, Feb 15, 2013 at 01:36:30PM +0100, Peter De Schrijver wrote:
> This is the seventh version of the Tegra114 clockframework. It is based on the
> for-next branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git and
>
2013/2/18 Vincent Guittot :
> On 18 February 2013 15:38, Frederic Weisbecker wrote:
>> I pasted the original at: http://pastebin.com/DMm5U8J8
>
> We can clear the idle flag only in the nohz_kick_needed which will not
> be called if the sched_domain is NULL so the sequence will be
>
> = CPU 0 =
Hi folks,
there are today a number of SYSFS files with read permission set but
can't really be read (tried with normal user and root). To make things
simpler, I wrote a simple ruby script (see below) to check if the file
is world writeable or if it has Read permission but throws an exception
when
On Mon, 2013-02-18 at 12:16 +0100, Thomas Gleixner wrote:
> On Mon, 18 Feb 2013, Tim Sander wrote:
> > Here is a transtribed backtrace for easier reading:
> > c0010fac t dump_backtrace
> > c022c188 T dump_stack
> > c022c71c t __schedule_bug
> > c022fb28 t __schedule
> > c0230644 t
On Mon, 2013-02-18 at 11:58 +0100, Vincent Guittot wrote:
> My tests have been done without cpuidle because i have some issues
> with function tracer and cpuidle
>
> But the cpu hotplug and cpuidle work well when I run the tests without
> enabling the function tracer
>
I know suspend and
On Mon, 2013-02-18 at 13:43 +0530, Srikar Dronamraju wrote:
> > The cache misses dropped by ~23% and migrations dropped by ~28%. I
> > really believe that the idle_balance() hurts performance, and not just
> > for something like hackbench, but the aggressive nature for migration
> > that
Em Mon, 18 Feb 2013 14:52:51 +0100
Borislav Petkov escreveu:
> On Sun, Feb 17, 2013 at 07:44:04AM -0300, Mauro Carvalho Chehab wrote:
> > We could do it for the location. The space for label, however, depends on
> > how many DIMMs are in the system, as multiple dimm's may be present, and
> > the
On Mon, 2013-02-18 at 04:42 +0100, Mike Galbraith wrote:
> On Sun, 2013-02-17 at 16:54 -0500, Steven Rostedt wrote:
> > On Sun, 2013-02-17 at 08:14 +0100, Mike Galbraith wrote:
> >
> > > (And puts a dent in x264 ultrafast)
>
> > What about my last patch? The one that avoids idle_balance() if
On Mon, 2013-02-18 at 12:39 +1100, Amnon Shiloh wrote:
> Hello,
>
> The code in "kernel/sys.c" provides the "prctl(PR_SET_MM)" function,
> which is the only way a process can set or modify the following 11
> per-process fields:
>
> start_code, end_code, start_data, end_data, start_brk,
On Mon, Feb 18, 2013 at 06:34:44PM +0800, Lin Feng wrote:
> >>> + if (!migrate_pre_flag) {
> >>> + if (migrate_prep())
> >>> + goto put_page;
> >
> > CONFIG_MEMORY_HOTREMOVE depends on CONFIG_MIGRATION so this will never
> >
Hi,
I think the advantage of the ioctl() is that is reuses existing infrastructure.
The downside is that to get the timestamp you need at a minimum:
uint64_t get_perf_timestamp(void)
{
struct perf_event_attr attr;
uint64_t ts = 0;
int fd;
memset(, 0, sizeof(attr));
/* pick a
2013/2/18 OGAWA Hirofumi :
> Namjae Jeon writes:
>
>>> Hm. My concerns are compatibility and reliability. Although We can
>>> change on-disk format if need, but I don't think it can be compatible
>>> and reliable. If so, who wants to use it? I feel there is no reason to
>>> use FAT if there is no
On Wed, Feb 13, 2013 at 07:40:05PM +0100, Daniel Vetter wrote:
> On Tue, Jan 22, 2013 at 7:55 PM, David Woodhouse wrote:
> > On Mon, 2013-01-21 at 19:48 +0100, Daniel Vetter wrote:
> >> We already have the quirk entry for the mobile platform, but also
> >> reports on some desktop versions. So be
On 18 February 2013 15:38, Frederic Weisbecker wrote:
> 2013/2/18 Frederic Weisbecker :
>> 2013/2/8 Vincent Guittot :
>>> On 8 February 2013 16:35, Frederic Weisbecker wrote:
What if the following happen (inventing function names but you get the
idea):
CPU 0
On 18/02/2013 19:42, Hillf Danton wrote:
On Mon, Feb 18, 2013 at 2:18 PM, Daniel J Blueman
wrote:
On Monday, 18 February 2013 06:10:02 UTC+8, Jiri Slaby wrote:
Hi,
You still feel the sour taste of the "kswapd craziness in v3.7" thread,
right? Welcome to the hell, part two :{.
I believe
Em Fri, Feb 15, 2013 at 05:28:49PM -0500, Frederik Deweerdt escreveu:
> Hi,
>
> The following patch causes 'perf stat --repeat 0' to be interpreted as
> 'forever', displaying the stats for every run.
>
> We act as if a single run was asked, and reset the stats in each
> iteration. In this mode
On Sat, 2013-02-16 at 12:59 -0800, Paul E. McKenney wrote:
>
> > diff --git a/kernel/rcutiny_plugin.h b/kernel/rcutiny_plugin.h
> > index 2b0484a..bac1906 100644
> > --- a/kernel/rcutiny_plugin.h
> > +++ b/kernel/rcutiny_plugin.h
> > @@ -552,7 +552,7 @@ static void rcu_read_unlock_special(struct
Namjae Jeon writes:
>> Hm. My concerns are compatibility and reliability. Although We can
>> change on-disk format if need, but I don't think it can be compatible
>> and reliable. If so, who wants to use it? I feel there is no reason to
>> use FAT if there is no compatible.
>>
>> Well, anyway,
t; > Afaict if memory offline fails now, the device is ejected (_EJ0) anyways
> > causing a panic. Tested in a VM with linux-next-20130207 and
> > linux-next-20130218 by doing an SCI-eject request on a hot-plugged dimm.
> >
> > Are there more patches in development for safe
2013/2/18 OGAWA Hirofumi :
> Namjae Jeon writes:
>
+ if (parent && (len < FAT_FID_SIZE_WITH_PARENT)) {
+ *lenp = FAT_FID_SIZE_WITH_PARENT;
+ return 255;
+ } else if (len < FAT_FID_SIZE_WITHOUT_PARENT) {
+ *lenp =
On Sat, Feb 16, 2013 at 10:26:30AM -0800, Linus Torvalds wrote:
> On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar wrote:
> >>
> >> c060f943d092 may be related as you config does not have
> >> CONFIG_SPARSEMEM defined.
> >
> > Right, that's the commit causing the x86 regression:
> >
> >
This patch allow using syscon driver from the platform data, i.e.
possibility using driver on systems without oftree support.
Signed-off-by: Alexander Shiyan
---
drivers/mfd/Kconfig | 1 -
drivers/mfd/syscon.c | 76 +++-
2 files changed, 57
Hello.
...
> >> >> Thanks for the patch adding non-dt support. :-)
> >> >>
> >> >> On Mon, Feb 04, 2013 at 07:00:40PM +0400, Alexander Shiyan wrote:
> >> >> > This patch adds support usage platform driver resources, i.e.
> >> >> > possibility works without oftree support. Additionally patch
> >>
2013/2/18 Frederic Weisbecker :
> 2013/2/8 Vincent Guittot :
>> On 8 February 2013 16:35, Frederic Weisbecker wrote:
>>> What if the following happen (inventing function names but you get the
>>> idea):
>>>
>>> CPU 0 CPU 1
>>>
>>> dom = new_domain(...) {
Namjae Jeon writes:
>>> + if (parent && (len < FAT_FID_SIZE_WITH_PARENT)) {
>>> + *lenp = FAT_FID_SIZE_WITH_PARENT;
>>> + return 255;
>>> + } else if (len < FAT_FID_SIZE_WITHOUT_PARENT) {
>>> + *lenp = FAT_FID_SIZE_WITHOUT_PARENT;
>>> +
(2013/02/16 10:20), Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 15 Feb 2013 08:52:12 -0800, Eric Dumazet wrote:
>
>> Driver is buggy, as TX completion can happen both from ndo_start_xmit()
>> and a timer, and there is no spinlock or appropriate synchro.
>
> Yes, it is a known issue. I did post
2013/2/8 Vincent Guittot :
> On 8 February 2013 16:35, Frederic Weisbecker wrote:
>> What if the following happen (inventing function names but you get the idea):
>>
>> CPU 0 CPU 1
>>
>> dom = new_domain(...) {
>>nr_cpus_busy = 0;
>>
Hi Andy,
On Sun, Feb 17, 2013 at 4:17 PM, Andi Shyti wrote:
>> >> + char name[30];
>> >> + char buf[50];
>> >> +
>> >> + if (size >= sizeof(buf))
>> >> + size = sizeof(buf);
>> >
>> > what's the point of this?
>>
>> This is a way to limit copied from userspace data by
Hi Tomi,
On Thu, Feb 14, 2013 at 11:24 AM, Tomi Valkeinen wrote:
> On 2013-02-14 02:07, Ruslan Bilovol wrote:
>
>> This patch is exactly a part of mainlining of the BlazeTablet board support
>> :)
>> The goal is to have as much as possible support of this board in the
>> 'vanilla' kernel.
>>
2013/2/18 OGAWA Hirofumi :
> Andrew Bartlett writes:
>
>>> >> First, Thanks for your interest !
>>> >> A mismatch between inode size and reserved blocks can be either due to
>>> >> pre-allocation (after our changes) or due to corruption (sudden unplug
>>> >> of media etc).
>>> >> We don’t think
From: Magnus Damm
This patch adds a driver for external IRQ pins connected
to the INTC block on recent SoCs from Renesas.
The INTC hardware block usually contains a rather wide
range of features ranging from external IRQ pin handling
to legacy interrupt controller support. On older SoCs
the
Commit-ID: dbda92d16f8655044e082930e4e9d244b87fde77
Gitweb: http://git.kernel.org/tip/dbda92d16f8655044e082930e4e9d244b87fde77
Author: Bu, Yitian
AuthorDate: Mon, 18 Feb 2013 12:53:37 +
Committer: Thomas Gleixner
CommitDate: Mon, 18 Feb 2013 15:05:57 +0100
printk: Fix rq->lock vs
2013/2/18 OGAWA Hirofumi :
> OGAWA Hirofumi writes:
>
>>> +if (parent && (len < FAT_FID_SIZE_WITH_PARENT)) {
>>> +*lenp = FAT_FID_SIZE_WITH_PARENT;
>>> +return 255;
>>> +} else if (len < FAT_FID_SIZE_WITHOUT_PARENT) {
>>> +*lenp =
2013/2/18 OGAWA Hirofumi :
> Namjae Jeon writes:
>
>> + if (MSDOS_SB(inode->i_sb)->options.nfs == FAT_NFS_NOSTALE_RO) {
>> + if (inode->i_ino == MSDOS_ROOT_INO)
>> + stat->ino = MSDOS_ROOT_INO;
>
> Can we simply set i_pos = MSDOS_ROOT_INO in fat_read_root()? If
2013/2/18 OGAWA Hirofumi :
> Namjae Jeon writes:
>
>> -nfs -- This option maintains an index (cache) of directory
>> - inodes by i_logstart which is used by the nfs-related code to
>> - improve look-ups.
>> +nfs= stale_rw|nostale_ro
>
> Strange space after
On Sun, Feb 17, 2013 at 07:44:04AM -0300, Mauro Carvalho Chehab wrote:
> We could do it for the location. The space for label, however, depends on
> how many DIMMs are in the system, as multiple dimm's may be present, and
> the core will point to all possible affected DIMMs.
>
> Ok, perhaps we
On Sun, Feb 17, 2013 at 04:41:57PM +0100, Peter Feuerer wrote:
> Don't think so, I think this was already in since 2.6. and
> I assume with this patch applied, acerhdf works from at least this
> 2.6. up to new 3.8 and will still work in the future.
Well, it can't be because there wouldn't be
On 02/18/2013 12:30 AM, Afzal Mohammed wrote:
> Register percpu local timer for scheduler tick in the case of one core
> SMP configuration. In other cases - secondary cpu's as well as boot
> cpu's having more than one core, this is being registered as per
> existing boot flow, with a difference
Am Montag, 18. Februar 2013, 12:16:41 schrieb Thomas Gleixner:
> On Mon, 18 Feb 2013, Tim Sander wrote:
> > Here is a transtribed backtrace for easier reading:
> > c0010fac t dump_backtrace
> > c022c188 T dump_stack
> > c022c71c t __schedule_bug
> > c022fb28 t __schedule
> > c0230644 t
On Mon, 11 Feb 2013, Len Brown wrote:
> From: Len Brown
>
> Update APM to register its local idle routine with cpuidle.
>
> This allows us to stop exporting pm_idle to modules on x86.
>
> The Kconfig sub-option, APM_CPU_IDLE, now depends on on CPU_IDLE.
>
> Compile-tested only.
I will test
On 15.2.2013 17:25, Stephen Warren wrote:
> On 02/15/2013 01:52 AM, Hiroshi Doyu wrote:
>> This patch allows kernel source to include those DT
>> headers. For example:
>>
>> + #include
>>
>> Signed-off-by: Hiroshi Doyu
>> ---
>> Makefile |2 +-
>> 1 file changed, 1 insertion(+), 1
On Mon, Feb 18, 2013 at 01:51:45PM +0100, Christian Ruppert wrote:
> This patch makes the SDA hold time configurable through device tree.
> It was tested on a hybrid of i2c/next and arc-3.8-baseline (see
> https://github.com/foss-for-synopsys-dwc-arc-processors/linux/commits/arc-3.8-baseline)
>
This patch enables BMP085 pressure sensor that can be
found on OMAP4 Blaze Tablet development platform
Signed-off-by: Ruslan Bilovol
---
arch/arm/configs/omap2plus_defconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/omap2plus_defconfig
On Mon, 2013-02-18 at 20:36 +0900, OGAWA Hirofumi wrote:
> Andrew Bartlett writes:
> > Or, if we cannot make any changes to the on-disk format, what about
> > keeping such a database in memory, allocating some of the existing free
> > list to files that have had fallocate() called on them?
y hot-remove operations?
I doesn't by itself. Nor it really can, because the .remove() callbacks of
device drivers are not allowed to fail.
> Afaict if memory offline fails now, the device is ejected (_EJ0) anyways
> causing a panic. Tested in a VM with linux-next-20130207 and
> linux-next-
On Mon, Feb 18, 2013 at 06:12:54PM +0530, Srivatsa S. Bhat wrote:
> Once stop_machine() is gone from the CPU offline path, we won't be able to
> depend on preempt_disable() or local_irq_disable() to prevent CPUs from
> going offline from under us.
>
> Use the get/put_online_cpus_atomic() APIs to
pick_next_entity() prefers next, then last. However code checks if the
left entity can be skipped even if next / last is set.
Check if left entity should be skipped only if next/last is not set.
Signed-off-by: Srikar Dronamraju
---
kernel/sched/fair.c | 31 +++
1
The pci controller structure has a provision to store the device strcuture
pointer of the corresponding platform device. Currently this information is
not stored during fsl pci controller initialization. This information is
required while dealing with iommu groups for pci devices connected to the
Macros for checking FSL PCI controller version.
Signed-off-by: Varun Sethi
---
arch/powerpc/include/asm/pci-bridge.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/include/asm/pci-bridge.h
b/arch/powerpc/include/asm/pci-bridge.h
index 025a130..c12ed78
301 - 400 of 1098 matches
Mail list logo
