On 16 October 2012 09:59, Russell King - ARM Linux
wrote:
> On Tue, Oct 16, 2012 at 09:04:34AM +0300, Hiroshi Doyu wrote:
>> In addition to those contiguous/discontiguous page allocation, is
>> there any way to _import_ anonymous pages allocated by a process to be
>> used in dma-mapping API
Sukadev,
On 15.10.12 17:55:34, Robert Richter wrote:
> On 11.10.12 18:28:39, Sukadev Bhattiprolu wrote:
> > + { .type = PERF_TYPE_HARDWARE, .config =
> > PERF_COUNT_HW_STALLED_CYCLES_FIXED_POINT },
> > + { .type = PERF_TYPE_HARDWARE, .config =
> > PERF_COUNT_HW_STALLED_CYCLES_LOAD_STORE },
>
From: Sivaram Nair
This undoes commit 20f4665831cec65d6e5d33587bba28ffa536b91d by bringing
back the tegra_timer clock. tegra_timer is indeed a clock (hidden by
the PERIPH_CLK macro) which should be added to the tegra_list_clks.
The above commit caused tegra_init_timer() failing to get the clk
This patchset fixes a bug introduced by commit
20f4665831cec65d6e5d33587bba28ffa536b91d by bringing back the
tegra_timer clock. The above commit caused tegra_init_timer() failing
to get the clk reference.
The first patch renames the existing tegra_timer object to
tegra_sys_timer and the second
From: Sivaram Nair
The timer variable is renamed to avoid confusion and symbol name clash
with the tegra_timer clock.
Signed-off-by: Sivaram Nair
---
arch/arm/mach-tegra/board-dt-tegra20.c |2 +-
arch/arm/mach-tegra/board-dt-tegra30.c |2 +-
arch/arm/mach-tegra/board.h|
From: Sha Zhengju
Sysctl oom_kill_allocating_task enables or disables killing the OOM-triggering
task in out-of-memory situations, but it only works on overall system-wide oom.
But it's also a useful indication in memcg so we take it into consideration
while oom happening in memcg. Other sysctl
Hi Hiroshi,
2012/10/16 Hiroshi Doyu :
> Hi Inki/Marek,
>
> On Tue, 16 Oct 2012 02:50:16 +0200
> Inki Dae wrote:
>
>> 2012/10/15 Marek Szyprowski :
>> > Hello,
>> >
>> > Some devices, which have IOMMU, for some use cases might require to
>> > allocate a buffers for DMA which is contiguous in
Hi,
There are many situations where we want to correlate events happening at
the user level with samples recorded in the perf_event kernel sampling buffer.
For instance, we might want to correlate the call to a function or creation of
a file with samples. Similarly, when we want to monitor a JVM
Namjae Jeon writes:
>> What is real usage pattern of persistent across remounts on FAT?
> Yes, like a TORRENT FILE -> it reserves space in advance
> even though the system can be rebooted/disk unmounted and remount
> but the space still remains there - as long as the torrent exists
> Or if
On Tue, Oct 16, 2012 at 12:52 PM, Viresh Kumar wrote:
>>> Also, the proposed solution might hide some other important errors. We may
>>> need
>>> to terminate transfers when we found that an error is there in last
>>> transfers:
>> I think it could be better than first solution, but what do
From: Suleiman Souhlal
We currently have a percpu stock cache scheme that charges one page at a
time from memcg->res, the user counter. When the kernel memory
controller comes into play, we'll need to charge more than that.
This is because kernel memory allocations will also draw from the user
This is just a cleanup patch for clarity of expression. In earlier
submissions, people asked it to be in a separate patch, so here it is.
[ v2: use named enum as type throughout the file as well ]
Signed-off-by: Glauber Costa
Acked-by: Kamezawa Hiroyuki
Acked-by: Michal Hocko
Acked-by:
From: Suleiman Souhlal
mem_cgroup_do_charge() was written before kmem accounting, and expects
three cases: being called for 1 page, being called for a stock of 32
pages, or being called for a hugepage. If we call for 2 or 3 pages (and
both the stack and several slabs used in process creation
Signed-off-by: Glauber Costa
CC: Frederic Weisbecker
CC: Kamezawa Hiroyuki
CC: Michal Hocko
CC: Christoph Lameter
CC: Pekka Enberg
CC: Johannes Weiner
CC: Suleiman Souhlal
CC: Tejun Heo
---
Documentation/cgroups/memory.txt | 58 +++-
1 file changed, 57
Because the ultimate goal of the kmem tracking in memcg is to track slab
pages as well, we can't guarantee that we'll always be able to point a
page to a particular process, and migrate the charges along with it -
since in the common case, a page will contain data belonging to multiple
processes.
We can use static branches to patch the code in or out when not used.
Because the _ACTIVE bit on kmem_accounted is only set after the
increment is done, we guarantee that the root memcg will always be
selected for kmem charges until all call sites are patched (see
memcg_kmem_enabled). This
Because kmem charges can outlive the cgroup, we need to make sure that
we won't free the memcg structure while charges are still in flight.
For reviewing simplicity, the charge functions will issue
mem_cgroup_get() at every charge, and mem_cgroup_put() at every
uncharge.
This can get expensive,
Because those architectures will draw their stacks directly from the
page allocator, rather than the slab cache, we can directly pass
__GFP_KMEMCG flag, and issue the corresponding free_pages.
This code path is taken when the architecture doesn't define
CONFIG_ARCH_THREAD_INFO_ALLOCATOR (only
A lot of the initialization we do in mem_cgroup_create() is done with
softirqs enabled. This include grabbing a css id, which holds
>id_lock->rlock, and the per-zone trees, which holds
rtpz->lock->rlock. All of those signal to the lockdep mechanism that
those locks can be used in SOFTIRQ-ON-W
This patch introduces infrastructure for tracking kernel memory pages to
a given memcg. This will happen whenever the caller includes the flag
__GFP_KMEMCG flag, and the task belong to a memcg other than the root.
In memcontrol.h those functions are wrapped in inline acessors. The
idea is to
It is useful to know how many charges are still left after a call to
res_counter_uncharge. While it is possible to issue a res_counter_read
after uncharge, this can be racy.
If we need, for instance, to take some action when the counters drop
down to 0, only one of the callers should see it. This
When a process tries to allocate a page with the __GFP_KMEMCG flag, the
page allocator will call the corresponding memcg functions to validate
the allocation. Tasks in the root memcg can always proceed.
To avoid adding markers to the page - and a kmem flag that would
necessarily follow, as much
This flag is used to indicate to the callees that this allocation is a
kernel allocation in process context, and should be accounted to
current's memcg. It takes numerical place of the of the recently removed
__GFP_NO_KSWAPD.
[ v4: make flag unconditional, also declare it in trace code ]
Hi,
This is the first part of the kernel memory controller for memcg. It has been
discussed many times, and I consider this stable enough to be on tree. A follow
up to this series are the patches to also track slab memory. They are not
included here because I believe we could benefit from merging
This patch adds the basic infrastructure for the accounting of kernel
memory. To control that, the following files are created:
* memory.kmem.usage_in_bytes
* memory.kmem.limit_in_bytes
* memory.kmem.failcnt
* memory.kmem.max_usage_in_bytes
They have the same meaning of their user memory
On 10/16/2012 06:12 PM, Sha Zhengju wrote:
From: Sha Zhengju
Sysctl oom_kill_allocating_task enables or disables killing the OOM-triggering
task in out-of-memory situations, but it only works on overall system-wide oom.
But it's also a useful indication in memcg so we take it into
From: Alan Cox
If elf_core_dump is called and fill_note_info fails in the kmalloc then
it returns 0 but has not yet initialised all the needed fields. As a result
we do a kfree(randomness) after correctly skipping the thread data.
Signed-off-by: Alan Cox
---
fs/binfmt_elf.c |4 +++-
1
On Tue, Oct 16, 2012 at 01:27:13AM +0V400, Frederic Weisbecker wrote:
> 2012/9/18 Andrew Vagin :
> > You may want to know where and how long a task is sleeping. A callchain
> > may be found in sched_switch and a time slice in stat_iowait, so I add
> > handler in perf inject for merging this
From: Alan Cox
This happens to do the right thing in all cases on fibre channel but not on
other media types
Signed-off-by: Alan Cox
---
drivers/message/fusion/mptscsih.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/message/fusion/mptscsih.c
Hi Russell,
Russell King - ARM Linux wrote @ Tue, 16 Oct 2012
10:59:28 +0200:
> On Tue, Oct 16, 2012 at 09:04:34AM +0300, Hiroshi Doyu wrote:
> > In addition to those contiguous/discontiguous page allocation, is
> > there any way to _import_ anonymous pages allocated by a process to be
> >
On 10/16/2012 5:17 PM, Hans-Christian Egtvedt wrote:
Around Tue 16 Oct 2012 15:19:27 +0800 or thereabout, Josh Wu wrote:
fixed the following compile error when use avr32 atstk1006_defconfig:
drivers/mtd/nand/atmel_nand.c: In function 'pmecc_err_location':
On Tue, Oct 16, 2012 at 07:12:49PM +0900, Inki Dae wrote:
> Hi Hiroshi,
>
> I'm not sure I understand what you mean but we had already tried this
> way and for this, you can refer to below link,
>
> http://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg22555.html
>
> but
On Tue, 16 Oct 2012 12:13:38 +0800
Chen Gang wrote:
> 于 2012年10月16日 10:51, Myklebust, Trond 写道:
>
> >>
> >> 1) is it means: nfs_inode_attrs_need_update need not consider async
> >> read_done situation ?
> >
> > I don't understand what you mean. This is mainly about the asynchronous
> > write
On Tue, Oct 16, 2012 at 12:27:55PM +0200, Hiroshi Doyu wrote:
> Hi Russell,
>
> Russell King - ARM Linux wrote @ Tue, 16 Oct 2012
> 10:59:28 +0200:
>
> > On Tue, Oct 16, 2012 at 09:04:34AM +0300, Hiroshi Doyu wrote:
> > > In addition to those contiguous/discontiguous page allocation, is
> > >
On 10/16/2012 06:20 PM, Ni zhan Chen wrote:
On 10/16/2012 06:12 PM, Sha Zhengju wrote:
From: Sha Zhengju
Sysctl oom_kill_allocating_task enables or disables killing the
OOM-triggering
task in out-of-memory situations, but it only works on overall
system-wide oom.
But it's also a useful
On 16 October 2012 14:13, James Hogan wrote:
> Commit 800d78bfccb3d38116abfda2a5b9c8afdbd5ea21 ("mmc: dw_mmc: add
> support for implementation specific callbacks") merged in v3.7-rc1.
>
> The above commit introduced multiple NULL pointer dereferences when
> the default dw_mci_pltfm_probe() is
On Tue, Oct 16, 2012 at 05:53:07PM +0800, Ni zhan Chen wrote:
> >By hpa request I've tried alternative approach for hzp implementation (see
> >Virtual huge zero page patchset): pmd table with all entries set to zero
> >page. This way should be more cache friendly, but it increases TLB
> >pressure.
On Tuesday, October 16, James Hogan
> Commit 800d78bfccb3d38116abfda2a5b9c8afdbd5ea21 ("mmc: dw_mmc: add
> support for implementation specific callbacks") merged in v3.7-rc1.
>
> The above commit introduced multiple NULL pointer dereferences when
> the default dw_mci_pltfm_probe() is used, as it
On 10/16/2012 11:43 AM, Lars Poeschel wrote:
> On Tuesday 16 October 2012 at 10:40:26, Lars-Peter Clausen wrote:
>> On 10/12/2012 04:34 PM, Lars Poeschel wrote:
>>> [...]
>>> +static void vprbrd_dev_release(struct device *dev)
>>> +{
>>> + return;
>>
>> A empty release callback is usually a good
Hi Russell,
2012/10/16 Russell King - ARM Linux :
> On Tue, Oct 16, 2012 at 07:12:49PM +0900, Inki Dae wrote:
>> Hi Hiroshi,
>>
>> I'm not sure I understand what you mean but we had already tried this
>> way and for this, you can refer to below link,
>>
>>
On 10/16/2012 06:54 PM, Kirill A. Shutemov wrote:
On Tue, Oct 16, 2012 at 05:53:07PM +0800, Ni zhan Chen wrote:
By hpa request I've tried alternative approach for hzp implementation (see
Virtual huge zero page patchset): pmd table with all entries set to zero
page. This way should be more cache
From: Matthieu CASTET
on cortexA8 (omap3) ralign is 64 and __alignof__(unsigned long long) is 8.
So we always disable debug.
This patch is based on 5c5e3b33b7cb959a401f823707bee006caadd76e, but fix
case were align < sizeof(unsigned long long).
Signed-off-by: Matthieu Castet
CC: Russell King
This function is used by sparc, powerpc tile and arm64 for compat
support. The patch adds a generic implementation with a wrapper for
PowerPC to do the u32->int sign extension.
The reason for a single patch covering powerpc, tile, sparc and arm64 is
to keep it bisectable, otherwise kernel
On Tue, Oct 16, 2012 at 07:13:07PM +0800, Ni zhan Chen wrote:
> On 10/16/2012 06:54 PM, Kirill A. Shutemov wrote:
> >On Tue, Oct 16, 2012 at 05:53:07PM +0800, Ni zhan Chen wrote:
> >>>By hpa request I've tried alternative approach for hzp implementation (see
> >>>Virtual huge zero page patchset):
On 16.10.2012 11:17, Hans-Christian Egtvedt wrote:
> Around Tue 16 Oct 2012 15:19:27 +0800 or thereabout, Josh Wu wrote:
>> fixed the following compile error when use avr32 atstk1006_defconfig:
>> drivers/mtd/nand/atmel_nand.c: In function 'pmecc_err_location':
>>
On 13 October 2012 16:33, Jassi Brar wrote:
> On Fri, Oct 5, 2012 at 3:47 PM, Inderpal Singh
> wrote:
>> The first 2 patches of this series fix memory leaks because the memory
>> allocated for peripheral channels and DMA descriptors were not getting
>> freed.
>>
>> The last 2 patches balance the
On 10/16/2012 07:28 PM, Kirill A. Shutemov wrote:
On Tue, Oct 16, 2012 at 07:13:07PM +0800, Ni zhan Chen wrote:
On 10/16/2012 06:54 PM, Kirill A. Shutemov wrote:
On Tue, Oct 16, 2012 at 05:53:07PM +0800, Ni zhan Chen wrote:
By hpa request I've tried alternative approach for hzp implementation
On Tuesday 16 October 2012, Jaegeuk Kim wrote:
> On Monday 15 October 2012, Dave Chinner wrote:
> > On Sun, Oct 14, 2012 at 03:19:37PM +, Arnd Bergmann wrote:
> > > On Sunday 14 October 2012, Vyacheslav Dubeyko wrote:
> > > > On Oct 14, 2012, at 11:09 AM, Jaegeuk Kim wrote:
> > > > >
于 2012年10月16日 18:33, Jeff Layton 写道:
> In any situation where we get back attributes, we have to decide
> whether they are valid or stale. It's always possible for replies or
> their handling to be reordered such that an older set of attributes
> is processed after a newer set.
>
>
From: "hongbo.zhang"
Hi all,
This patch set is to upstream ST-Ericsson thermal driver and fix some bugs
of thermal layer at the same time.
All of these patches are based on v3.7-rc1.
[PATCH 1/5] Thermal: do bind operation after thermal zone or cooling
device register returns.
In the previous
From: "hongbo.zhang"
In the previous bind function, cdev->get_max_state(cdev, _state) is called
before the registration function finishes, but at this moment, the parameter
cdev at thermal driver layer isn't ready--it will get ready only after its
registration, so the the get_max_state callback
From: "hongbo.zhang"
Signed-off-by: hongbo.zhang
---
drivers/thermal/cpu_cooling.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
index cc1c930..b6b4c2a 100644
--- a/drivers/thermal/cpu_cooling.c
+++
From: "hongbo.zhang"
Is is not reliable to check the list entry pointer after
list_for_each_entry loop, list_empty should be used instead.
Signed-off-by: hongbo.zhang
---
drivers/thermal/cpu_cooling.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
From: "hongbo.zhang"
The cpufreq works as a cooling device, so the cooling layer should
check and wait until the cpufreq driver is initialized.
Signed-off-by: hongbo.zhang
---
drivers/thermal/cpu_cooling.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git
From: "hongbo.zhang"
This diver is based on the thermal management framework in thermal_sys.c.
A thermal zone device is created with the trip points to which cooling
devices can be bound, the current cooling device is cpufreq, e.g. CPU
frequency is clipped down to cool the CPU, and other cooling
There are several places in the kernel that use functionality like basename(3)
with an exception: in case of '/foo/bar/' we expect to get an empty string.
Let's do it common helper for them.
Signed-off-by: Andy Shevchenko
Cc: Jason Baron
Cc: YAMANE Toshiaki
Cc: Greg Kroah-Hartman
Cc:
Signed-off-by: Andy Shevchenko
---
fs/proc/proc_devtree.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index df7dd08..3d9fd66 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -13,6 +13,7 @@
There are several places in the kernel that use functionality like basename(3)
with the exception: in case of '/foo/bar/' we expect to get an empty string.
Let's do it common helper for them.
Signed-off-by: Andy Shevchenko
---
include/linux/string.h | 11 +++
1 file changed, 11
Signed-off-by: Andy Shevchenko
Cc: Steven Rostedt
Cc: Frederic Weisbecker
---
kernel/trace/trace_uprobe.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
index 03003cd..c7ba4f6 100644
---
The custom filename function mostly repeats the kernel's kbasename. This patch
simplifies it. The updated filename() will not check for the '\' in the
filenames. It seems redundant in Linux. The __FILE__ macro always defined if
we compile an existing file. Thus, NULL check is not needed there as
Remove the custom implementation of the functionality similar to kbasename().
Signed-off-by: Andy Shevchenko
Cc: Jason Baron
---
lib/dynamic_debug.c |9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index e7f7d99..1db1fc6
There are several places in kernel that duplicate code to get last part of the
pathname. This patchset introduces a helper and few fixes.
Since v2:
- fixed Cc list in the patch 6/6 ("trace: ...")
- update patch 3/6 ("rts_pstor: ...") to not hide const qualifier
- send patch 1/1 to all people
Signed-off-by: Andy Shevchenko
Cc: linux...@kvack.org
---
mm/memory.c |8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/mm/memory.c b/mm/memory.c
index 5823f29..06158b7 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -58,6 +58,7 @@
#include
#include
#include
(2012/10/16 2:17), Khalid Aziz wrote:
> On Mon, 2012-10-15 at 16:00 +0900, Takao Indoh wrote:
>> This patch resets PCIe devices at boot time by hot reset when
>> "reset_devices" is specified.
>>
>> Signed-off-by: Takao Indoh
>> ---
>> arch/x86/include/asm/pci-direct.h |1
>>
Appear to be a copy-paste bug: the code was checking board_data->dsi_enable_pads
while calling board_data->dsi_disable_pads.
Signed-off-by: Peter Ujfalusi
---
Hi Tomi,
not sure if this need to be included to 3.7
Regards,
Peter
drivers/video/omap2/dss/core.c | 2 +-
1 file changed, 1
(2012/10/16 18:02), Hyeoncheol Lee wrote:
> Event arguments except @SYM are supported. They are @ADDR,
> $stack, $stackN, $retval, and offs(arguments).
>
> Cc: Masami Hiramatsu
> Cc: Srikar Dronamraju
> Signed-off-by: Hyeoncheol Lee
> ---
[...]
> #define DEFINE_FETCH_stack(type)
This patch adds basic support to take care of opmode(if any) which can be set by
set_suspend_[disable/mode] callbacks.
Signed-off-by: Yadwinder Singh Brar
---
drivers/regulator/max77686.c | 16 ++--
1 files changed, 14 insertions(+), 2 deletions(-)
diff --git
This patch implements set_suspend_disable callback for BUCKs which
support only switch ON/OFF modes during system suspend state, and
set_suspend_mode callbacks for LDOs which also suport Low power mode and
switch ON/OFF modes.
Signed-off-by: Yadwinder Singh Brar
---
drivers/regulator/max77686.c
We can not directly call kvm_release_pfn_clean to release the pfn
since we can meet noslot pfn which is used to cache mmio info into
spte
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c |3 +--
virt/kvm/kvm_main.c |4 +---
2 files changed, 2 insertions(+), 5 deletions(-)
diff
Remove mmu_is_invalid and use is_invalid_pfn instead
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c |5 -
arch/x86/kvm/paging_tmpl.h |4 ++--
2 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 6f85fe0..b8d13d7
Let it return emulate state instead of spte like __direct_map
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/paging_tmpl.h | 32 +---
1 files changed, 13 insertions(+), 19 deletions(-)
diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
index
The function does not depend on guest mmu mode, move it out from
paging_tmpl.h
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c | 36
arch/x86/kvm/paging_tmpl.h | 26 +++---
2 files changed, 31 insertions(+), 31
The only difference between FNAME(update_pte) and FNAME(pte_prefetch)
is that the former is allowed to prefetch gfn from dirty logged slot,
so introduce a common function to prefetch spte
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/paging_tmpl.h | 55
This patch filters noslot pfn out from error pfns based on Marcelo comment:
noslot pfn is not a error pfn
After this patch,
- is_noslot_pfn indicates that the gfn is not in slot
- is_error_pfn indicates that the gfn is in slot but the error is occurred
when translate the gfn to pfn
-
Alex Russell writes:
> Signed-off-by: Alex Russell
> ---
> drivers/lguest/core.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/lguest/core.c b/drivers/lguest/core.c
> index b5fdcb7..a5ebc00 100644
> --- a/drivers/lguest/core.c
> +++ b/drivers/lguest/core.c
On Tue, 16 Oct 2012 19:44:38 +0800
Chen Gang wrote:
>
> 于 2012年10月16日 18:33, Jeff Layton 写道:
> > In any situation where we get back attributes, we have to decide
> > whether they are valid or stale. It's always possible for replies or
> > their handling to be reordered such that an older set of
On Tue 16-10-12 14:16:41, Glauber Costa wrote:
> This patch adds the basic infrastructure for the accounting of kernel
> memory. To control that, the following files are created:
>
> * memory.kmem.usage_in_bytes
> * memory.kmem.limit_in_bytes
> * memory.kmem.failcnt
> *
On Tue 16-10-12 14:16:42, Glauber Costa wrote:
> This flag is used to indicate to the callees that this allocation is a
> kernel allocation in process context, and should be accounted to
> current's memcg. It takes numerical place of the of the recently removed
> __GFP_NO_KSWAPD.
>
> [ v4: make
On Tue, Oct 16, 2012 at 12:08 PM, Robert Richter wrote:
> Sukadev,
>
> On 15.10.12 17:55:34, Robert Richter wrote:
>> On 11.10.12 18:28:39, Sukadev Bhattiprolu wrote:
>> > + { .type = PERF_TYPE_HARDWARE, .config =
>> > PERF_COUNT_HW_STALLED_CYCLES_FIXED_POINT },
>> > + { .type =
On Tue 16-10-12 14:16:51, Glauber Costa wrote:
> Signed-off-by: Glauber Costa
> CC: Frederic Weisbecker
> CC: Kamezawa Hiroyuki
> CC: Michal Hocko
> CC: Christoph Lameter
> CC: Pekka Enberg
> CC: Johannes Weiner
> CC: Suleiman Souhlal
> CC: Tejun Heo
Acked-by: Michal Hocko ---
>
Hi Luis,
On Saturday 13 October 2012 10:00:42 Luis R. Rodriguez wrote:
> On Sat, Oct 13, 2012 at 3:33 AM, Laurent Pinchart wrote:
> > On Friday 12 October 2012 16:49:31 Luis R. Rodriguez wrote:
> >> From: "Luis R. Rodriguez"
> >>
> >> The UAPI changes split kernel API and userspace API
> >>
Hi Stephen,
On Mon, Oct 15, 2012 at 11:42:44AM -0600, Stephen Warren wrote:
> Joerg, given 3.7-rc1 is now out, I'd like to take this through the Tegra
> tree due to other patches depending on it.
>
> Given the patch is so trivial, I'll probably just apply it anyway soon -
> this is more of a
David,
On Mon, Oct 15, 2012 at 9:46 PM, David Rientjes wrote:
> On Sat, 13 Oct 2012, Ezequiel Garcia wrote:
>
>> But SLAB suffers from a lot more internal fragmentation than SLUB,
>> which I guess is a known fact. So memory-constrained devices
>> would waste more memory by using SLAB.
>
> Even
On Tue, Oct 16, 2012 at 09:32:29AM +0200, Gabor Z. Papp wrote:
> lo lo,
>
> I'm trying to compile 2.6.32.60 with gcc 4.7.2, and getting the
> following error:
>
> CC arch/x86/kernel/ptrace.o
> arch/x86/kernel/ptrace.c:1472:17: error: conflicting types for
> 'syscall_trace_enter'
> In
I have this lockdep warning on wireless-testing tree based
on 3.7-rc1 (no other patches except wireless bits).
=
Restarting tasks ... done.
[ INFO: possible recursive locking detected ]
3.7.0-rc1-wl+ #2 Not tainted
On Tue, Oct 16, 2012 at 11:26:01AM +0200, Laurent CARON wrote:
> On Tue, Oct 16, 2012 at 11:03:53AM +0200, Borislav Petkov wrote:
> > That's:
> >
> > BUG_ON(async_tx_test_ack(depend_tx) || txd_next(depend_tx)
> > ||
> > txd_parent(tx));
> >
> > but probably
On Mon, Oct 15, 2012 at 11:42:44AM -0600, Stephen Warren wrote:
> Joerg, given 3.7-rc1 is now out, I'd like to take this through the Tegra
> tree due to other patches depending on it.
>
> Given the patch is so trivial, I'll probably just apply it anyway soon -
> this is more of a heads-up to
On Mon, Oct 15, 2012 at 11:33:08PM +0800, Fei Yang wrote:
> 2012/10/15 Mikael Pettersson :
> > Yangfei (Felix) writes:
> > > Hi all,
> > >
> > > I found that hardcoded instruction in inline asm can cause certains
> > certain features fail to work on ARM platform due to endianness.
> > >
Posting this patch to fix an issue concerning sparse irq's that I raised
a while back. There was discussion about adding refcounting to sparse
irqs (to fix other potential race conditions), but that does not appear to
have been addressed yet. This covers the only issue of this type that I've
On 10/16/2012 04:39 AM, Mel Gorman wrote:
Thierry reported that the "iron out" patch for isolate_freepages_block()
had problems due to the strict check being too strict with "mm: compaction:
Iron out isolate_freepages_block() and isolate_freepages_range() -fix1".
It's possible that more pages
On Tue, Oct 16, 2012 at 02:48:25PM +0200, Borislav Petkov wrote:
> On Tue, Oct 16, 2012 at 11:26:01AM +0200, Laurent CARON wrote:
> > On Tue, Oct 16, 2012 at 11:03:53AM +0200, Borislav Petkov wrote:
> > > That's:
> > >
> > > BUG_ON(async_tx_test_ack(depend_tx) ||
> > >
On 10/16/2012 01:57 AM, Greg KH wrote:
> On Tue, Oct 16, 2012 at 01:31:18AM +0200, Roland Stigge wrote:
>> +int gpio_block_export(struct gpio_block *block)
>> +{
>> +int status;
>> +struct device *dev;
>> +
>> +/* can't export until sysfs is available ... */
>> +if
David Sharp wrote:
> > Please use the Kbuild infrastructure ("generic-y += ..." in
> > arch/*/include/asm/Kbuild)
> > instead of adding wrappers around the asm-generic version.
>
> mips apparently recencly got rid of arch/mips/include/asm/Kbuild.
It didn't. However, if you use patch to create
On Tue, 2012-10-16 at 09:35 -0300, Ezequiel Garcia wrote:
> Now, returning to the fragmentation. The problem with SLAB is that
> its smaller cache available for kmalloced objects is 32 bytes;
> while SLUB allows 8, 16, 24 ...
>
> Perhaps adding smaller caches to SLAB might make sense?
> Is there
The prediction for future is difficult and when the cpuidle governor prediction
fails and govenor possibly choose the shallower C-state than it should. How to
quickly notice and find the failure becomes important for power saving.
cpuidle menu governor has a method to predict the repeat
The prediction for future is difficult and when the cpuidle governor prediction
fails and govenor possibly choose the shallower C-state than it should. How to
quickly notice and find the failure becomes important for power saving.
cpuidle menu governor has a method to predict the repeat
In general case, the expected residency is much larger than deepest C-state
target residency, but prediction logic still predicts the small predicted
residency, so the prediction history is totally broken. In this situation,
reset the correction factor is the only choice.
Signed-off-by: Youquan
When cpuidle governor choose a C-state to enter for idle CPU, but it notice that
there is tasks request to be executed. So the idle CPU will not really enter
the target C-state and go to run task.
In this situation, it will use the residency of previous really entered target
C-states. Obviously,
The function detect_repeating_patterns was not very useful for
workloads with alternating long and short pauses, for example
virtual machines handling network requests for each other (say
a web and database server).
Instead, try to find a recent sleep interval that is somewhere
between the median
The prediction for future is difficult and when the cpuidle governor prediction
fails and govenor possibly choose the shallower C-state than it should. How to
quickly notice and find the failure becomes important for power saving.
The patch extends to general case that prediction logic get
701 - 800 of 1166 matches
Mail list logo
