On Wed, Dec 18, 2013 at 3:37 PM, Grygorii Strashko
wrote:
> The system may crash if:
> - there are more then 1 bank
> - unbanked irqs are enabled
> - someone will call gpio_to_irq() for GPIO from bank2 or above
>
> Hence, fix it by not creating irq_domain if unbanked irqs are enabled
> and correct
On Wed, Dec 18, 2013 at 3:37 PM, Grygorii Strashko
wrote:
> The similar GPIO HW block is used by keystone SoCs as
> in Davinci SoCs.
> Hence, reuse Davinci GPIO driver for Keystone taking into
> account that Keystone contains ARM GIC IRQ controller which
> is implemented using IRQ Chip.
>
> Docume
On Wed, Dec 18, 2013 at 03:53:47PM +0900, Joonsoo Kim wrote:
> Currently, to track a reserved and allocated region, we use two different
> ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use
> address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map.
> Now, we are preparing to
On Fri, 2013-12-20 at 16:41 +0100, Sebastian Andrzej Siewior wrote:
> On 07.11.13, Thomas Gleixner wrote:
> > below should address that issue. If that works on mainline we can
> > adapt it for RT (needs a trylock(&base->lock) there).
>
> okay, so this is waht I'm going to take for -RT:
Works, mo
From: Wei Yongjun
Remove including that don't need it.
Signed-off-by: Wei Yongjun
---
drivers/misc/genwqe/card_sysfs.c | 1 -
drivers/misc/genwqe/card_base.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/misc/genwqe/card_sysfs.c b/drivers/misc/genwqe/card_sysfs.c
index a72a992
Hello,
This patch series adds support for clock accuracy retrieval in the common clk
framework.
Best Regards,
Boris
Changes since v3:
- do not export __clk_get_accuracy symbol
Changes since v2:
- fix __clk_recalc_accuracies function comment
- modify __clk_get_accuracy to return the current
The clock accuracy is expressed in ppb (parts per billion) and represents
the possible clock drift.
Say you have a clock (e.g. an oscillator) which provides a fixed clock of
20MHz with an accuracy of +- 20Hz. This accuracy expressed in ppb is
20Hz/20MHz = 1000 ppb (or 1 ppm).
Clock users may need
This patch adds support for accuracy retrieval on fixed clocks.
It also adds a new dt property called 'clock-accuracy' to define the clock
accuracy.
This can be usefull for oscillator (RC, crystal, ...) definitions which are
always given an accuracy characteristic.
Signed-off-by: Boris BREZILLON
Dear All,
When check code , we found below issue in zap_thread function().
>From 57bf616d0e20086d73122373baf799c675f4e3d5 Mon Sep 17 00:00:00 2001
From: Ajeet Yadav
Date: Sat, 21 Dec 2013 14:45:48 +0530
Subject: [PATCH] secure unlock_task_sighand() call
Since the return value was not checked
Update several comments:
1. use f2fs_{un}lock_op install of mutex_{un}lock_op.
2. update comment of get_data_block().
3. update description of node offset.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 14 --
fs/f2fs/dir.c |4 ++--
fs/f2fs/f2fs.h |2 +-
fs/f2fs/node.c |8
In current flow, we will get Null return value of f2fs_find_entry in
recover_dentry when name.len is bigger than F2FS_NAME_LEN, and then we
still add this inode into its dir entry.
To avoid this situation, we must check filename length before we use it.
Another point is that we could remove the co
When we rename a dir to new name which is not exist previous,
we will set pino of parent inode with ino of child inode in f2fs_set_link.
It destroy consistency of pino, it should be fixed.
Thanks for previous work of Shu Tan.
Signed-off-by: Shu Tan
Signed-off-by: Chao Yu
---
fs/f2fs/dir.c |
On Fri, Dec 20, 2013 at 06:29:46PM -0500, Steven Rostedt wrote:
> On Fri, 20 Dec 2013 22:44:13 +0100
> Peter Zijlstra wrote:
>
>
> > @@ -5056,10 +5018,28 @@ static int sched_cpu_inactive(struct not
> > switch (action & ~CPU_TASKS_FROZEN) {
> > case CPU_DOWN_PREPARE:
> > set_c
Mark function smtcfb_setmode() as static in sm7xxfb.c because it is not
used outside this file.
This eliminates the following warning in sm7xxfb.c:
drivers/staging/sm7xxfb/sm7xxfb.c:588:6: warning: no previous prototype for
‘smtcfb_setmode’ [-Wmissing-prototypes]
Signed-off-by: Rashika Kheria
-
Mark functions t3e3_set_loopback(), t3e3_reg_read(), t3e3_reg_write(),
t3e3_port_get(), t3e3_port_set(), t3e3_port_get_stats() and
t3e3_port_del_stats() as static in ctrl.c because they are not used
outside this file.
This eliminates the following warnings in ctrl.c:
drivers/staging/sbe-2t3e3/ctrl
Mark function dwc2_set_param_uframe_sched() as static in core.c because
it is not used outside this file.
This eliminates the following warning in core.c:
drivers/staging/dwc2/core.c:2739:5: warning: no previous prototype for
‘dwc2_set_param_uframe_sched’ [-Wmissing-prototypes]
Signed-off-by: Ra
'max14577_dt_match' is always compiled in. Hence the
helper macro is not needed.
Signed-off-by: Sachin Kamat
---
drivers/mfd/max14577.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/max14577.c b/drivers/mfd/max14577.c
index a5e1c370c609..ac514fb2b877 100644
-
Include appropriate header file dgnc/dgnc_trace.h in dgnc_trace.c
because function dgnc_tracer_free() has its prototype declaration in the
header file.
This eliminates the following warning in dgnc_trace.c:
drivers/staging/dgnc/dgnc_trace.c:180:6: warning: no previous prototype for
‘dgnc_tracer_f
On Sat, Dec 21, 2013 at 03:44:13PM +0530, Rashika Kheria wrote:
> Mark function smtcfb_setmode() as static in sm7xxfb.c because it is not
> used outside this file.
>
> This eliminates the following warning in sm7xxfb.c:
> drivers/staging/sm7xxfb/sm7xxfb.c:588:6: warning: no previous prototype for
Include appropriate header file in dgap/dgap_parse.h in dgap_parse.c
because functions dgap_parsefile(), dgap_config_get_useintr(),
dgap_config_get_altpin(), dgap_find_config(),
dgap_config_get_number_of_ports(), dgap_create_config_string() and
dgap_get_config_letters() have their prototype declara
Include appropriate header file dgap/dgap_trace.h in dgap_trace.c
because function dgap_tracer_free() have its prototype declaration in
the header file.
This eliminates the following warning in dgap_trace.c:
drivers/staging/dgap/dgap_trace.c:181:6: warning: no previous prototype for
‘dgap_tracer_
Mark functions MatchSrcIpAddress(), MatchDestIpAddress() and MatchTos()
as static in Qos.c because they are not used outside this file.
This eliminates the following warnings in Qos.c:
drivers/staging/bcm/Qos.c:27:6: warning: no previous prototype for
‘MatchSrcIpAddress’ [-Wmissing-prototypes]
dr
Remove unused function PropagateCalParamsFromEEPROMToMemory() in nvm.c.
This eliminates the following warning in nvm.c:
drivers/staging/bcm/nvm.c:1369:5: warning: no previous prototype for
‘PropagateCalParamsFromEEPROMToMemory’ [-Wmissing-prototypes]
Signed-off-by: Rashika Kheria
---
drivers/s
Remove unused devm_*_put functions because none of them are
used anywhere in the kernel and devm does automatic cleanup
of resources and requires no manual cleanup.
Signed-off-by: Rashika Kheria
Reviewed-by: Josh Triplett
---
drivers/gpio/devres.c | 25 -
drive
On Sat, Dec 21, 2013 at 03:47:13PM +0530, Rashika Kheria wrote:
> Mark functions t3e3_set_loopback(), t3e3_reg_read(), t3e3_reg_write(),
> t3e3_port_get(), t3e3_port_set(), t3e3_port_get_stats() and
> t3e3_port_del_stats() as static in ctrl.c because they are not used
> outside this file.
>
> This
On Sat, Dec 21, 2013 at 03:50:29PM +0530, Rashika Kheria wrote:
> Mark function dwc2_set_param_uframe_sched() as static in core.c because
> it is not used outside this file.
>
> This eliminates the following warning in core.c:
> drivers/staging/dwc2/core.c:2739:5: warning: no previous prototype fo
On Sat, Dec 21, 2013 at 03:52:38PM +0530, Rashika Kheria wrote:
> Include appropriate header file dgnc/dgnc_trace.h in dgnc_trace.c
> because function dgnc_tracer_free() has its prototype declaration in the
> header file.
>
> This eliminates the following warning in dgnc_trace.c:
> drivers/staging
On Sat, Dec 21, 2013 at 03:58:25PM +0530, Rashika Kheria wrote:
> Include appropriate header file dgap/dgap_trace.h in dgap_trace.c
> because function dgap_tracer_free() have its prototype declaration in
> the header file.
>
> This eliminates the following warning in dgap_trace.c:
> drivers/stagin
On Sat, Dec 21, 2013 at 03:55:50PM +0530, Rashika Kheria wrote:
> Include appropriate header file in dgap/dgap_parse.h in dgap_parse.c
> because functions dgap_parsefile(), dgap_config_get_useintr(),
> dgap_config_get_altpin(), dgap_find_config(),
> dgap_config_get_number_of_ports(), dgap_create_co
On Sat, Dec 21, 2013 at 04:01:16PM +0530, Rashika Kheria wrote:
> Mark functions MatchSrcIpAddress(), MatchDestIpAddress() and MatchTos()
> as static in Qos.c because they are not used outside this file.
>
> This eliminates the following warnings in Qos.c:
> drivers/staging/bcm/Qos.c:27:6: warning
On Sat, Dec 21, 2013 at 04:03:22PM +0530, Rashika Kheria wrote:
> Remove unused function PropagateCalParamsFromEEPROMToMemory() in nvm.c.
>
> This eliminates the following warning in nvm.c:
> drivers/staging/bcm/nvm.c:1369:5: warning: no previous prototype for
> ‘PropagateCalParamsFromEEPROMToMem
On Fri, Dec 20, 2013 at 03:20:16PM -0800, Kees Cook wrote:
>
> If we're doing fd origin verification (not signatures), can't we
> continue to use a regular bzImage?
I imagine the verification function is separated from the new kexec.
It gets passed the proposed new kernel file*, an optional signa
On Fri, Dec 20, 2013 at 07:32:11PM -0800, H. Peter Anvin wrote:
> thing, as currently built there are megabytes of zeroes in it for no
> good reason.
Then remove them ;) AFAICS, that's x86 only? What a waste!
What's the reason? ALIGN_RODATA? Even if so, vmlinux.gz might be
a fair trade-off.
>
>
Dear All,
We found below issue in coredump for uninterruptible task -
>From 1c46f0327d98ad593d8913f9f1dad352f8f44304 Mon Sep 17 00:00:00 2001
From: Ajeet Yadav
Date: Sat, 21 Dec 2013 17:06:05 +0530
Subject: [PATCH] skip increamenting nr for TASK_UNINTERRUPTIBLE
In coredump case, where thread_1
On Fri, 20 Dec, at 11:18:56PM, Rafael J. Wysocki wrote:
>
> I'm not sure 100%, but I *think* we need to do that with interrupts enabled.
> At least after mm_init(), because it relies on things initialized there if I
> remember correctly.
>
> From what I can tell at the moment, it might be possibl
On 12/21/2013 11:14 AM, Rashika Kheria wrote:
> Mark function smtcfb_setmode() as static in sm7xxfb.c because it is not
> used outside this file.
>
> This eliminates the following warning in sm7xxfb.c:
> drivers/staging/sm7xxfb/sm7xxfb.c:588:6: warning: no previous prototype for
> ‘smtcfb_setmode
On Fri, Dec 20, 2013 at 7:43 PM, Colin Cross wrote:
> dma_buf_map_attachment and dma_buf_vmap can return NULL or
> ERR_PTR on a error. This encourages a common buggy pattern in
> callers:
> sgt = dma_buf_map_attachment(attach, DMA_BIDIRECTIONAL);
> if (IS_ERR_OR_NULL(sgt))
>
On Wed, Dec 18, 2013 at 03:53:48PM +0900, Joonsoo Kim wrote:
> To change a protection method for region tracking to find grained one,
> we pass the resv_map, instead of list_head, to region manipulation
> functions. This doesn't introduce any functional change, and it is just
> for preparing a next
Hello Wei,
Am Samstag, den 21.12.2013, 17:23 +0800 schrieb Wei Yongjun:
> From: Wei Yongjun
>
> Remove including that don't need it.
>
> Signed-off-by: Wei Yongjun
> ---
> drivers/misc/genwqe/card_sysfs.c | 1 -
> drivers/misc/genwqe/card_base.h | 1 -
> 2 files changed, 2 deletions(-)
>
>
On Fri, Dec 20, 2013 at 09:23:46PM +0100, Arnaud Ebalard wrote:
> I do not even know to which specific component the irq line of the chip
> is connected. You can take a look at [1] to see what's on the PCB; if
> you have an idea about which one could be a good candidate (TPS65251?),
> I can try an
On Fri, Dec 20, 2013 at 11:43:21AM -0200, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Fix the 'VOLATGE' spell error.
Applied, thanks.
--
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:/
On Fri, Dec 20, 2013 at 12:48:22PM -0200, Fabio Estevam wrote:
> I could not find in the reference manual anywhere that says that the delay
> should de done only when the voltage increases.
The reason this is normally not done is that generally consumers don't
care too much if the supply is too h
On Sat, Dec 21, 2013 at 5:49 AM, Shawn Guo wrote:
> On Fri, Dec 20, 2013 at 11:42:09AM -0200, Fabio Estevam wrote:
>> From: Fabio Estevam
>>
>> At the 'anatop_probe_end' error path, the variable 'ret' is known to be
>> non-zero, so there is no need to check it.
>>
>> Signed-off-by: Fabio Estevam
On Thu, Dec 19, 2013 at 03:54:57PM +, Lee Jones wrote:
> At this moment in time the Ux500 ASoC driver obtains its DMA information
> via AUXDATA platform data passing. To make the driver more independent
> we have to start extracting it from the Device Tree. This patch-set goes
> some way to ens
On Thu, Dec 19, 2013 at 04:03:34PM +0100, Levente Kurusa wrote:
> This is required so that we give up the last reference to the device.
Applied, thanks. Please use subject lines matching the standard for the
subsystem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Fri, Dec 20, 2013 at 12:17:38PM +0800, Xiubo Li wrote:
> There is no need of this function and makes the code slightly shorter
Applied, thanks.
--
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
On Fri, Dec 20, 2013 at 12:35:33PM +0800, Xiubo Li wrote:
> Makes the code slightly shorter
Applied, thanks.
--
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-inf
On Fri, Dec 20, 2013 at 12:30:26PM +0800, Xiubo Li wrote:
> Makes the code slightly shorter
Applied, thanks.
--
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-inf
On Fri, Dec 20, 2013 at 02:39:50PM +0800, Xiubo Li wrote:
> The name of cpu DAI maybe omitted, and then strlen() will lead
> kernel panic.
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordom
On Fri, 20 Dec, at 06:02:19PM, Dave Young wrote:
> Add a new setup_data type SETUP_EFI for kexec use.
> Passing the saved fw_vendor, runtime, config tables and efi runtime mappings.
>
> When entering virtual mode, directly mapping the efi runtime ragions which
> we passed in previously. And skip t
BMP085 EOC (End Of Conversion) irq line is connected to
gpio113 on gta04. Set irq properties to have driver using irq
instead polling for EOC.
Signed-off-by: Marek Belisko
---
arch/arm/boot/dts/omap3-gta04.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-gta04.dt
於 五，2013-12-20 於 17:51 -0800，H. Peter Anvin 提到：
> On 12/20/2013 05:24 PM, joeyli wrote:
> > 於 五，2013-12-20 於 13:04 -0800，H. Peter Anvin 提到：
> >>
> >> Actually, it doesn't have to reprogram the clock ... it just needs to
> >> know if another OS has already done so. All Linux needs to do is to be
>
getmod a application of KGTP (https://kgtp.googlecode.com).
It can get Linux Kernel modules info from sysfs and output them as GDB
command add-symbol-file format. Then you can call "source output_file_name"
inside GDB to let it load all the debug info of Linux Kernel modules.
It will help debug
getmod.py is a application of KGTP (https://kgtp.googlecode.com) too.
After GDB connected to the gdbstub such as KGTP, KGDB, QEMU, call it with
GDB command "source getmod.py". Then GDB will auto load all the debug
info of Linux Kernel modules.
Because GDB need parse the struct the data of modul
We relocate root cache's memcg_params whenever we need to grow the
memcg_caches array to accommodate all kmem-active memory cgroups.
Currently on relocation we free the old version immediately, which can
lead to use-after-free, because the memcg_caches array is accessed
lock-free (see cache_from_me
All caches of the same memory cgroup are linked in the memcg_slab_caches
list via kmem_cache::memcg_params::list. This list is traversed, for
example, when we read memory.kmem.slabinfo. Since the list actually
consists of memcg_cache_params objects, we have to convert an element of
the list to a km
Currently, we have rather a messy function set relating to per-memcg
kmem cache initialization/destruction.
Per-memcg caches are created in memcg_create_kmem_cache(). This function
calls kmem_cache_create_memcg() to allocate and initialize a kmem cache
and then "registers" the new cache in the mem
We obtain a per-memcg cache from a root kmem_cache by dereferencing an
entry of the root cache's memcg_params::memcg_caches array. If we find
no cache for a memcg there on allocation, we initiate the memcg cache
creation (see memcg_kmem_get_cache()). The cache creation proceeds
asynchronously in me
Each root kmem_cache has pointers to per-memcg caches stored in its
memcg_params::memcg_caches array. Whenever we want to allocate a slab
for a memcg, we access this array to get per-memcg cache to allocate
from (see memcg_kmem_get_cache()). The access must be lock-free for
performance reasons, so
On Sat, Dec 21, 2013 at 12:25:50PM -0200, Fabio Estevam wrote:
> I see. Then we can do this instead, so that the successful probe and
> the error path are clearer:
Yes, that's going to cause fewer surprises.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Currently we take both the memcg_create_mutex and the set_limit_mutex
when we enable kmem accounting for a memory cgroup, which makes kmem
activation events serialize with both memcg creations and other memcg
limit updates (memory.limit, memory.memsw.limit). However, there is no
point in such stric
Currently we have two state bits in mem_cgroup::kmem_account_flags
regarding kmem accounting activation, ACTIVATED and ACTIVE. We start
kmem accounting only if both flags are set (memcg_can_account_kmem()),
plus throughout the code there are several places where we check only
the ACTIVE flag, but w
There is no point in flooding logs with warnings or especially crashing
the system if we fail to create a cache for a memcg. In this case we
will be accounting the memcg allocation to the root cgroup until we
succeed to create its own cache, but it isn't that critical.
Signed-off-by: Vladimir Davy
We do not free the cache's memcg_params if __kmem_cache_create fails.
Fix this.
Plus, rename memcg_register_cache() to memcg_alloc_cache_params(),
because it actually does not register the cache anywhere, but simply
initialize kmem_cache::memcg_params.
Signed-off-by: Vladimir Davydov
Cc: Michal
kmem_cache_dup() is only called from memcg_create_kmem_cache(). The
latter, in fact, does nothing besides this, so let's fold
kmem_cache_dup() into memcg_create_kmem_cache().
This patch also makes the memcg_cache_mutex private to
memcg_create_kmem_cache(), because it is not used anywhere else.
Si
This patch-set fixes several bugs here and there in the implementation
of kmem accounting for memory cgroups and makes the code look a bit
clearer.
Vladimir Davydov (11):
slab: cleanup kmem_cache_create_memcg() error handling
memcg, slab: kmem_cache_create_memcg(): fix memleak on fail path
m
Currently kmem_cache_create_memcg() backoffs on failure inside
conditionals, without using gotos. This results in the rollback code
duplication, which makes the function look cumbersome even though on
error we should only free the allocated cache. Since in the next patch I
am going to add yet anoth
Correct spelling typo in memory.txt and
resource_counter.txt
Signed-off-by: Masanari Iida
---
Documentation/cgroups/memory.txt | 4 ++--
Documentation/cgroups/resource_counter.txt | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/cgroups/memory.txt
On 17.12.2013 22:23, Mel Gorman wrote:
On Tue, Dec 17, 2013 at 04:07:35PM +0100, Zlatko Calusic wrote:
On 13.12.2013 15:10, Mel Gorman wrote:
Kicked this another bit today. It's still a bit half-baked but it restores
the historical performance and leaves the door open at the end for playing
nic
On Fri, 20 Dec, at 06:02:19PM, Dave Young wrote:
> @@ -133,6 +133,19 @@ extern void efi_sync_low_kernel_mappings(void);
> extern void efi_setup_page_tables(void);
> extern void __init old_map_region(efi_memory_desc_t *md);
>
> +struct efi_setup_data {
> + u64 fw_vendor;
> + u64 runtime;
Correct spelling typo in Documentations/virtual/kvm
Signed-off-by: Masanari Iida
---
Documentation/virtual/kvm/api.txt | 4 ++--
Documentation/virtual/kvm/hypercalls.txt | 2 +-
Documentation/virtual/kvm/locking.txt | 4 ++--
Documentation/virtual/kvm/ppc-pv.txt | 2 +-
Documen
Hi,
spotted one more typo.
On 12/21/2013 04:57 PM, Masanari Iida wrote:
> diff --git a/Documentation/cgroups/resource_counter.txt
> b/Documentation/cgroups/resource_counter.txt
> index c4d99ed..52e1da1 100644
> --- a/Documentation/cgroups/resource_counter.txt
> +++ b/Documentation/cgroups/resour
On Sun, Dec 22, 2013 at 1:22 AM, Levente Kurusa wrote:
> Hi,
>
> spotted one more typo.
>
> On 12/21/2013 04:57 PM, Masanari Iida wrote:
>> diff --git a/Documentation/cgroups/resource_counter.txt
>> b/Documentation/cgroups/resource_counter.txt
>> index c4d99ed..52e1da1 100644
>> --- a/Documentati
On Sat, Dec 21 2013, Matias Bjorling wrote:
> Hi,
>
> These three patches cover:
>
> * Incorporated the feedback from Randy Dunlap into documentation.
> Can be merged with the previous documentation commit (6824518).
> * Set use_per_node_hctx to false per default to save resources.
> * Allow su
On Fri, Dec 20, 2013 at 02:28:05PM -0800, Olof Johansson wrote:
> Commit 597d795a2a78 ('mm: do not allocate page->ptl dynamically, if
> spinlock_t fits to long') restructures some allocators that are compiled
> even if USE_SPLIT_PTLOCKS arn't used. It results in compilation failure:
>
> mm/memory.
Sarah Sharp linux.intel.com> writes:
Good Afternoon,
> Also, do you have an HP system, or is this a different vendor?
for what its worth. I do have an Ivybridge laptop and I do see
immediate wake-ups from suspend to ram from time to time. When
this happens I do modprobe -r xhci_hcd and the mac
> > At this moment in time the Ux500 ASoC driver obtains its DMA information
> > via AUXDATA platform data passing. To make the driver more independent
> > we have to start extracting it from the Device Tree. This patch-set goes
> > some way to ensure the ux500 Audio driver is ready for the switch
On 21/12/2013 11:11, Mike Galbraith wrote:
Works, modulo noisy workqueues.
rtbox:~ # sleep 35 && killall pert& cgexec -g cpuset:rtcpus taskset -c 3 pert 5
[1] 5660
2400.05 MHZ CPU
perturbation threshold 0.018 usecs.
pert/s: 33 >15.75us:2 min: 0.04 max: 24.14 avg: 2.51 sum/s:
Like this then? :-)
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5056,10 +5019,25 @@ static int sched_cpu_inactive(struct not
switch (action & ~CPU_TASKS_FROZEN) {
case CPU_DOWN_PREPARE:
set_cpu_active((long)hcpu, false);
+
+ /* explicitly
Hi Guenter, hi Anthony,
On Thu, 19 Dec 2013 10:10:49 -0800, Guenter Roeck wrote:
> On Thu, Dec 19, 2013 at 03:54:54PM +0100, Jean Delvare wrote:
> > BTW, you (and we) probably shouldn't waste too much energy on this.
> > ADCs are only accurate to some degree anyway. If you take the
> > components
On Fri, 20 Dec, at 06:02:10PM, Dave Young wrote:
> Here is the V7 patchset for supporting kexec kernel efi runtime.
> Per pervious discussion I pass the 1st kernel efi runtime mapping
> via setup_data to 2nd kernel. Besides of the runtime mapping
> info I also pass the fw_vendor, runtime, config ta
Did you actually *see* the problem, or was this just from looking at the code?
I don't hate the patch, and it might be the right thing to do in any
case (just to avoid depending on subtle things), but this really *is*
subtle, and I'm adding Oleg to the participants since it is his code
(going back
Again, adding Oleg to the cc. And I don't think this is correct, since
SIGKILL can actually kill uninterruptible processes too
(TASK_WAKEKILL) so the basic premise of the patch is incorrect. And
again, we do have that whole issue with exit_mm() serialization.
Linus
On Sat, Dec
On 12/21/2013 09:30 AM, Jean Delvare wrote:
Hi Guenter, hi Anthony,
On Thu, 19 Dec 2013 10:10:49 -0800, Guenter Roeck wrote:
On Thu, Dec 19, 2013 at 03:54:54PM +0100, Jean Delvare wrote:
BTW, you (and we) probably shouldn't waste too much energy on this.
ADCs are only accurate to some degree a
On 12/18/2013 10:36 PM, Apelete Seketeli wrote:
> Add defconfig for the Ben NanoNote handheld computer which is built
> around QI_LB60 board and Ingenic JZ4740 MIPS SoC.
>
> Signed-off-by: Apelete Seketeli
Acked-by: Lars-Peter Clausen
> ---
> arch/mips/configs/qi_lb60_defconfig | 188
>
On 12/21/13 08:21, Masanari Iida wrote:
> Correct spelling typo in Documentations/virtual/kvm
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> Documentation/virtual/kvm/api.txt | 4 ++--
> Documentation/virtual/kvm/hypercalls.txt | 2 +-
> Documentation/virtua
> Cc: sta...@vger.kernel.org # 3.9+
> Signed-off-by: Naoya Horiguchi
Looks good.
Reviewed-by: Andi Kleen
-Andi
--
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/majordo
On 12/21, Linus Torvalds wrote:
>
> We have coredump serialization in exit_mm() that I think *should* make
> this all ok - if we still see p->mm matching our mm,
Yes. And the comment says:
lock_task_sighand(p)
must be used. Since p->mm != NULL and we hold ->mmap_sem
it can
On 12/21, Linus Torvalds wrote:
>
> Again, adding Oleg to the cc. And I don't think this is correct,
me too, but I can't reply right now, will do tomorrow,
> > In coredump case, where thread_1 faults while thread_2 is in
> > TASK_UNINTERRUPTIBLE state, it cannot handle the SIGKILL.
Yes, and we
[+cc Daniel]
On Fri, Dec 20, 2013 at 05:19:38PM -0800, Yinghai Lu wrote:
> On Fri, Dec 20, 2013 at 4:27 PM, Bjorn Helgaas wrote:
>
> > Why are we reading these BARs directly anyway? These look like
> > standard PCI BARs (I810_GMADDR == 0x10 and I915_GMADDR == 0x18), so
> > the PCI core should a
On Saturday 21 December 2013, Ravi Patel wrote:
> create mode 100644 Documentation/devicetree/bindings/misc/apm-xgene-qmtm.txt
>
> diff --git a/Documentation/devicetree/bindings/misc/apm-xgene-qmtm.txt
> b/Documentation/devicetree/bindings/misc/apm-xgene-qmtm.txt
> new file mode 100644
> index 0
New version of the PCU firmware supports two new commands:
- IMS_PCU_CMD_OFN_SET_CONFIG which allows to write data to the
registers of one finger navigation(OFN) chip present on the device
- IMS_PCU_CMD_OFN_GET_CONFIG which allows to read data form the
registers of said chip.
This commit a
From: Fabio Estevam
There is no need to create a local variable for accessing sreg->name.
Access it directly instead.
Signed-off-by: Fabio Estevam
---
Changes since v1:
- None
drivers/regulator/anatop-regulator.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/r
From: Fabio Estevam
Currently 'anatop_probe_end' path is executed on both succesfull and error paths
of anatop_regulator_probe().
To let the code a bit clearer, make 'anatop_probe_end' to be executed only when
an error happens.
Signed-off-by: Fabio Estevam
---
drivers/regulator/anatop-regulat
From: "Paul E. McKenney"
Running RCU out of softirq is a problem for some workloads that would
like to manage RCU core processing independently of other softirq work,
for example, setting kthread priority. This commit therefore moves the
RCU core work from softirq to a per-CPU/per-flavor SCHED_O
Hi Roger,
> It seems the controller the original driver was written for does not report
> touch ID and just reports 2 touch co-ordinates. I'm not sure how this fits
> into
> Type B reporting model.
Look in drivers/input/mouse/cypress_ps2.c for an example of how to deal with
anonymous touch coord
On Saturday 21 December 2013, Ravi Patel wrote:
> +/* CSR Address Macros */
> +#define CSR_QM_CONFIG_ADDR 0x0004
> +#define QM_ENABLE_WR(src) (((u32)(src)<<31) & 0x8000)
> +
> +#define CSR_PBM_ADDR 0x0008
> +#define OVERWRITE_WR(src) (((u32)(src)<<31) & 0x8000)
> +#d
On Saturday 21 December 2013, Ravi Patel wrote:
> This patch adds support for APM X-Gene SoC Queue Manager/Traffic Manager.
> QMTM is required by APM X-Gene SoC Ethernet, PktDMA (XOR Engine) and
> Security Engine subsystems. All subsystems communicate with QMTM using
> messages which include inf
Hi Benjamin,
> The ANTEC Touch Pad is a device which can switch from a multitouch
> touchpad to a mouse. It thus presents several generic collections which
> are currently ignored by hid-multitouch. Enable them by using the generic
> protocol. Adding also a suffix for them depending on their appli
Here's both x86 people and filesystem people involved, because this
hacky RFC patch touches both.
NOTE NOTE NOTE! I've modified "cp_new_stat()" in place, in a way that
is x86-64 specific. So the attached patch *only* works on x86-64, and
will very actively break on anything else. That's intentiona
1 - 100 of 154 matches
Mail list logo
