* H. Peter Anvin h...@zytor.com wrote:
Keep in mind we already tried CF9 in the default flow and it broke
things. I'm willing to wait for reports about production machines,
though, but I fully expect them.
Typically there's nothing particularly weird about preproduction Intel
hardware
Kirill A. Shutemov with faultaround patchset introduced
vm_ops-map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
This patch creates infrastructure to move the FAULT_AROUND_ORDER
to arch/ using Kconfig. This will enable architecture
Performance data for different FAULT_AROUND_ORDER values from 4 socket
Power7 system (128 Threads and 128GB memory) is below. perf stat with
repeat of 5 is used to get the stddev values. This patch create
FAULT_AROUND_ORDER Kconfig parameter and defaults it to 3 based on the
performance data.
On Thu, Apr 3, 2014 at 6:21 PM, Jovi Zhangwei jovi.zhang...@gmail.com wrote:
Hi Alexei,
We talked a lot on ktap and ebpf integration in these days,
Now I think we can put into deeply to thinking out some
technical issues in there.
Firstly, I want to make sure you are support this ktap and
Kirill A. Shutemov with faultaround patchset introduced
vm_ops-map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
This patchset creates infrastructure to move the FAULT_AROUND_ORDER
to arch/ using Kconfig. This will enable
Hi Daniel,
Interesting idea.
The benefit of this patch is to reduce power.
Have you been able to measure a power reduction, via power meter, or
via built-in RAPL power meter?
(turbostat will show RAPL watts, or if you have constant quantity of
work, use turbostat -J)
thanks,
-Len
--
To
On Thursday 03 April 2014 12:51 PM, Dan Carpenter wrote:
We are allocating the size of a pointer and not the size of the data.
This will lead to memory corruption.
There isn't actually a cb_device struct, btw. The code is only able
to compile because GCC knows that all pointers are the same
Hi Thomas,
I know you are not going to look at these before end of this merge window and
you wanted to have a look at V1 before me posting these. But I am reposting them
now due to these reasons:
- Need to resend my cpu isolation (cpuset.quiesce) patches which are based of
these
- Few patches
Caller of hrtimer_switch_to_hres(), i.e. hrtimer_run_pending(), has already
verified this by calling hrtimer_hres_active() and so we don't need to do it
again in hrtimer_switch_to_hres().
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 3 ---
1 file changed, 3
In switch_hrtimer_base() we are calling hrtimer_check_target() which guarantees
this:
/*
* With HIGHRES=y we do not migrate the timer when it is expiring
* before the next event on the target cpu because we cannot reprogram
* the target cpu hardware and we would cause it to fire late.
*
*
We need to call hrtimer_get_softirq_time() only once for a cpu_base from
hrtimer_run_queues(). And it shouldn't be called if there are no timers queued
for that cpu_base.
Currently we are managing this with help of a variable: gettime. This part of
code can be simplified by using
Complete bottom part of remove_hrtimer() is part of a 'if' block and so all code
present in that block has extra indentation level before it. Rewrite it to
remove this extra indentation level.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 46
Timers are removed from the red-black trees from __remove_hrtimer() and after
removing timer from the tree, it calls hrtimer_force_reprogram() which might use
value of cpu_base-active_bases. If the timer being removed is the last one on
that clock base, then cpu_base-active_bases wouldn't give the
We had this code at two places to find if a clock base belongs to current CPU:
base-cpu_base == __get_cpu_var(hrtimer_bases)
Better to get a inlined routine for that.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 9 ++---
1 file changed, 6 insertions(+),
The topology_##name() macro does not use its argument when CONFIG_SMP is not
set, as it ultimately calls the cpu_data() macro.
So we avoid maintaining a possibly unused `cpu' variable, to avoid the
following compilation warning:
drivers/base/topology.c: In function ‘show_physical_package_id’:
Currently we are returning notifier_from_errno() from CPU_UP_PREPARE notifier
when we detect there is an error while calling init_timers_cpu().
notifier_from_errno() already has enough checks within to do something similar.
And so we can call it directly without checking if there was an error or
clock 'base' can be obtained easily by doing timer-base and hrtimer_reprogram()
hrtimer_enqueue_reprogram() never gets anything else than timer-base as its
parameter. And so these routines doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
lock_hrtimer_base() always returns after taking lock and so timer-base can't
change further. So, callers of this routine can simply do timer-base to get the
base and so we can make this routine return void.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 17
clock 'base' can be obtained easily by doing timer-base and enqueue_hrtimer()
never gets anything else than timer-base as its parameter. And so this routines
doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 14 +++---
1
In init_timers() we need to call init_timers_cpu() for boot cpu. For this,
currently we are emulating a call to hotplug notifier. Probably this was done
initially to get rid of code redundancy. But this sequence always called a
single routine, i.e. init_timers_cpu(), and so calling that routine
switch_hrtimer_base() always sets timer-base to the right base and so the
caller can obtain it easily. So, this routine doesn't need to return anything.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
enqueue_hrtimer() routine is called from three places and only one of them
effectively uses its return value. Also, by its name enqueue_hrtimer() isn't
supposed to return if the queued timer is the leftmost. So it makes more sense
to separate this routine into two parts, first one enqueues a timer
clock 'base' can be obtained easily by doing timer-base and
switch_hrtimer_base() never gets anything else than timer-base as its
parameter. And so this routines doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 9 -
1
clock 'base' can be obtained easily by doing timer-base and remove_timer()/
__remove_timer() never gets anything else than timer-base as its parameter.
Which means, these routines doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c
We are taking cpu_base-lock for every clock-base in hrtimer_run_queues() and
there is nothing in there which prevents us to take this lock only once. Modify
code to take lock only once for a cpu_base.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 4 ++--
1 file
There are various places where we are currently running a loop of
HRTIMER_MAX_CLOCK_BASES iterations. We just run 'continue;' if there are no
timers added to a clock base. Instead we can use the new for_each_active_base()
routine to iterate over only the bases which are currently active.
There are many places where we need to iterate over all the currently active
clock bases for a particular cpu_base. Create for_each_active_base() to simplify
code at those places.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 13 +
1 file changed, 13
This code was added long back by following commit:
commit 06027bdd278a32a84b273e41db68a5db8ffd2bb6
Author: Ingo Molnar mi...@elte.hu
Date: Tue Feb 14 13:53:15 2006 -0800
[PATCH] hrtimer: round up relative start time on low-res arches
Don't know if it was a
Following code is repeated at many places:
ktime_sub(hrtimer_get_expires(timer), base-offset);
and so it makes sense to create a separate inlined routine for this.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
include/linux/hrtimer.h | 6 ++
kernel/hrtimer.c| 11
__remove_hrtimer() is called from three locations: remove_hrtimer(),
__run_hrtimer() and migrate_hrtimer_list(). And all these guarantee that timer
was queued earlier. And so there is no need to check if the timer is queued or
not in __remove_hrtimer().
Signed-off-by: Viresh Kumar
This patch reorders code within __remove_hrtimer() routine to achieve this:
- no need to check if timer is the next timer to expire when high resolution
mode isn't configured in kernel. So, move this check within the #ifdef/endif
block.
- Validate 'reprogram' and hrtimer_hres_active() first as
* Steven Rostedt rost...@goodmis.org wrote:
On Thu, 03 Apr 2014 07:10:47 -0700
H. Peter Anvin h...@zytor.com wrote:
Could you tell which of these modes work on your box:
Basically my thinking is that the patch should be reverted, if my fix
below does not work.
I distilled your test
Complete bottom part of switch_hrtimer_base() is part of a 'if' block and so all
code present in that block has extra indentation level before it. Rewrite it to
remove this extra indentation level.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 51
unlock_hrtimer_base() was handled specially at a separate place earlier as
lock_hrtimer_base() had separate definitions for SMP and non-SMP cases, but
unlock_hrtimer_base() had only a single definition. And so probably it was kept
at the end of this #ifdef/endif CONFIG_SMP. But this #ifdef ends
In hrtimers_init() we need to call init_hrtimers_cpu() for boot cpu. For this,
currently we are emulating a call to hotplug notifier. Probably this was done
initially to get rid of code redundancy. But this sequence always called a
single routine, i.e. init_hrtimers_cpu(), and so calling that
hrtimer_set_expires_range() and hrtimer_set_expires_range_ns() have almost same
implementations and so we can actually call hrtimer_set_expires_range() from
hrtimer_set_expires_range_ns() internally instead of duplicating code.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Linux coding guidelines says:
The preferred form for passing a size of a struct is the following:
p = kmalloc(sizeof(*p), ...);
But __hrtimer_init() wasn't following that. Fix it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 2 +-
1 file changed, 1
Breaking format fragments into multiple lines hits readability of code. Even if
it goes over 80 column width, its better to keep them together.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
'for' loop in migrate_hrtimers() has only one line in its body and so doesn't
require {} as per coding guidelines. Remove it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/hrtimer.c
retrigger_next_event() is defined within #ifdef CONFIG_HIGH_RES_TIMERS as we
already have pointer to base available. So it makes more sense to simple use
base-hres_active instead of doing this by calling hrtimer_hres_active():
__this_cpu_read(hrtimer_bases.hres_active)
Also the same
As majority of this code came from existing kernel/timer.c, few comments still
had name of routines from timers framework. Fix them.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/hrtimer.c
High Resolution feature can be enabled/disabled from bootargs if we have a
string 'highres=' followed by 'on' or 'off'. The default value of this variable
is '1'. When 'on' is passed as bootarg, we don't have to overwrite this
variable by '1'.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
The comment was probably added when there were only two clock bases available
for hrtimers, now there are four.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index
In switch_hrtimer_base() we have created a local variable basenum which is set
to base-index initially. This variable is used at only one place. It makes code
more readable if we remove this variable and use base-index directly.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Currently we have a 'tab' here instead of 'space' after 'comma'. Replace it with
space.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index d55092c..a1120a0 100644
On 04/03/2014 04:49 PM, Nishanth Menon wrote:
On 04/03/2014 05:52 AM, Peter Ujfalusi wrote:
[...]
.../devicetree/bindings/clock/clk-palmas.txt | 35 +++
drivers/clk/Kconfig| 7 +
drivers/clk/Makefile | 1 +
Hi,
I'm using TP-LINK PCIe NIC card on my PCIe Root Complex.
Probing looks fine by setting:
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
PCI: enabling device :00:00.0 (0140 - 0143)
PCI: enabling device :01:00.0 (0140 - 0143)
r8169 :01:00.0 eth0: RTL8168e/8111e at 0xf006a000,
Guys, I don't really see why you get so worked up about this. There is
lots and lots of precedent of Linux allowing non-Posix (or non-standard
in general) arguments to system calls. Even ones that don't have
symbolic names defined for them (the magic 3 open argument for device
files).
Given
hrtimer_force_reprogram() is only called from parts of kernel which are defined
between #ifdef CONFIG_HIGH_RES_TIMERS and so its empty definition is never used.
Remove it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
kernel/hrtimer.c | 2 --
1 file changed, 2 deletions(-)
diff --git
* Madhavan Srinivasan ma...@linux.vnet.ibm.com wrote:
Performance data for different FAULT_AROUND_ORDER values from 4 socket
Power7 system (128 Threads and 128GB memory) is below. perf stat with
repeat of 5 is used to get the stddev values. This patch create
FAULT_AROUND_ORDER Kconfig
Hello,
Probably this question belongs to kernelnewbies
list but I think i will get accurate answer from here.
I am doing some optimization in kernel video driver
code to reduce the latency from the time buffer
is given to the time it is displayed.
Userspace:
t1 = gettimeofday()
Kernelspace:
t2
The BCP bit in TCR4/RCR4 register rules as followings:
0 Bit clock is active high with drive outputs on rising edge
and sample inputs on falling edge.
1 Bit clock is active low with drive outputs on falling edge
and sample inputs on rising edge.
For all formats currently supported in
Hi Greg,
On 04/03/2014 02:57 PM, Greg Troxel wrote:
Michael Kerrisk (man-pages) mtk.manpa...@gmail.com writes:
I think the only reasonable solution is to better document existing
behavior and what the programmer should do. With that in mind, I've
drafted the following text for the
* Ingo Molnar mi...@kernel.org wrote:
* Madhavan Srinivasan ma...@linux.vnet.ibm.com wrote:
Performance data for different FAULT_AROUND_ORDER values from 4
socket Power7 system (128 Threads and 128GB memory) is below. perf
stat with repeat of 5 is used to get the stddev values. This
[Resending this message from yesterday, since, as Richard Hansen
pointed out, I failed to CC bug-readline@]
[CC += Peter Zijlstra]
[CC += bug-readl...@gnu.org -- maintainers, it _may_ be desirable to
fix your msync() call]
Richard,
On Thu, Apr 3, 2014 at 1:44 AM, Richard Hansen rhan...@bbn.com
On Fri, Apr 4, 2014 at 2:26 PM, Alexei Starovoitov a...@plumgrid.com wrote:
On Thu, Apr 3, 2014 at 6:21 PM, Jovi Zhangwei jovi.zhang...@gmail.com wrote:
Hi Alexei,
We talked a lot on ktap and ebpf integration in these days,
Now I think we can put into deeply to thinking out some
technical
* Alexei Starovoitov a...@plumgrid.com wrote:
On Thu, Apr 3, 2014 at 6:21 PM, Jovi Zhangwei jovi.zhang...@gmail.com wrote:
Hi Alexei,
We talked a lot on ktap and ebpf integration in these days,
Now I think we can put into deeply to thinking out some
technical issues in there.
On 04/03/2014 10:11 PM, Arun Shamanna Lakshmi wrote:
[...]
Here as well, default for bit_pos should be 0.
This means when 'None' of the options are selected, by default, it
enumerates to 0. Since we are using __ffs, BIT(0) of Register-0 also
enumerates to 0. That's the reason why I used just
-Original Message-
From: Lars-Peter Clausen [mailto:l...@metafoo.de]
Sent: Friday, April 04, 2014 12:32 AM
To: Arun Shamanna Lakshmi
Cc: lgirdw...@gmail.com; broo...@kernel.org;
swar...@wwwdotorg.org; pe...@perex.cz; ti...@suse.de; alsa-
de...@alsa-project.org;
The current kernel code assumes big endian and parses RTAS events all
wrong. The most visible effect is that we cannot honor EPOW events,
meaning, for example, we cannot shut down a guest properly from the
hypervisor.
This new patch is largely inspired by Nathan's work: we get rid of all
the bit
Hi,
I'm running into an inconsistent lock state warning on the final v3.14
kernel (-rc8 is good) on Freescale i.MX6 platform with fec driver
(drivers/net/ethernet/freescale/fec_main.c). The git bisect points
the finger to commit c15b1cc (ipv6: move DAD and addrconf_verify
processing to
On 04/03/2014 10:52 PM, Jan Kara wrote:
On Thu 03-04-14 08:34:44, Michael Kerrisk (man-pages) wrote:
Limitations and caveats
The inotify API provides no information about the user or process
that triggered the inotify event. In particular, there is no
easy way
Hi Tom,
On Wed, 02 Apr 2014 09:51:54 -0500, Tom Zanussi wrote:
Hi Namhyung,
On Wed, 2014-04-02 at 08:31 +, Namhyung Kim wrote:
One thing I noticed in the main logic is that it seems there's no
limit checking when adding/creating new entry. In
hash_trigger_entry_create(), there's a
* Jovi Zhangwei jovi.zhang...@gmail.com wrote:
On Wed, Apr 2, 2014 at 3:43 PM, Ingo Molnar mi...@kernel.org wrote:
* Jovi Zhangwei jovi.zhang...@gmail.com wrote:
So based on all these input, I suggest:
Put all these community efforts together, figure out the proper
design
Subject: [PATCH] ASoC: fsl_sai: Fix Bit Clock Polarity configurations
The BCP bit in TCR4/RCR4 register rules as followings:
0 Bit clock is active high with drive outputs on rising edge
and sample inputs on falling edge.
1 Bit clock is active low with drive outputs on falling edge
Signed-off-by: Alexey Brodkin abrod...@synopsys.com
Reviewed-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Cc: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Cc: Vineet Gupta vgu...@synopsys.com
cc: Brian Norris computersforpe...@gmail.com
Cc: Grant Likely grant.lik...@linaro.org
On 04/04/2014 09:34 AM, Arun Shamanna Lakshmi wrote:
-Original Message-
From: Lars-Peter Clausen [mailto:l...@metafoo.de]
Sent: Friday, April 04, 2014 12:32 AM
To: Arun Shamanna Lakshmi
Cc: lgirdw...@gmail.com; broo...@kernel.org;
swar...@wwwdotorg.org; pe...@perex.cz; ti...@suse.de;
On 3 April 2014 23:51, Ramkumar Ramachandra artag...@gmail.com wrote:
Ramkumar Ramachandra wrote:
tools/perf/config/Makefile | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Jiri, any comments?
Note: this patch is equivalent to '[PATCH] perf tools: Fix feature
check for libdw dwarf
Hi Viresh,
I changed your print message as you suggested.
diff --git a/kernel/timer.c b/kernel/timer.c
index 6c3a371..193101d 100644
--- a/kernel/timer.c
+++ b/kernel/timer.c
@@ -1617,8 +1617,8 @@ static void migrate_timer_list(struct tvec_base
*new_base, struct list_head *hea
* Jovi Zhangwei jovi.zhang...@gmail.com wrote:
On Fri, Apr 4, 2014 at 2:26 PM, Alexei Starovoitov a...@plumgrid.com wrote:
On Thu, Apr 3, 2014 at 6:21 PM, Jovi Zhangwei jovi.zhang...@gmail.com
wrote:
Hi Alexei,
We talked a lot on ktap and ebpf integration in these days,
Now I think
Add missing of_node_put to decremente the reference count.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/rtc/rtc-88pm860x.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rtc/rtc-88pm860x.c b/drivers/rtc/rtc-88pm860x.c
index fb9e3c63b4ac..0c6add1a38dc
Use of_get_child_by_name to obtain reference to charger node instead of
of_find_node_by_name which can walk outside of the parent node.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/rtc/rtc-88pm860x.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Use of_get_child_by_name to obtain reference to charger node instead of
of_find_node_by_name which can walk outside of the parent node.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/power/max8925_power.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
The driver obtained the reference to parent-of_node but immediately it
was overwritten by reference to child node 'leds'. The of_node_put at
the end of DT parsing function decremented only the child 'leds' so
effectively the reference to parent of_node leaked.
Getting reference to parent-of_node
Use of_get_child_by_name to obtain reference to charger node instead of
of_find_node_by_name which can walk outside of the parent node.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/leds/leds-88pm860x.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Check the return value of devm_kzalloc() to fix possible NULL pointer
dereference and properly exit the probe() on memory allocation failure.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/power/max8925_power.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
On 4 April 2014 13:16, Jet Chen jet.c...@intel.com wrote:
Hi Viresh,
I changed your print message as you suggested.
diff --git a/kernel/timer.c b/kernel/timer.c
index 6c3a371..193101d 100644
--- a/kernel/timer.c
+++ b/kernel/timer.c
@@ -1617,8 +1617,8 @@ static void
Hi Mark,
ping on this series, see comment below.
On 25 March 2014 16:23, Jean Pihet jean.pi...@linaro.org wrote:
Hi Mark,
On 21 March 2014 16:11, Mark Rutland mark.rutl...@arm.com wrote:
Hi Jean,
On Wed, Mar 19, 2014 at 09:42:33AM +, Jean Pihet wrote:
Introducing perf_regs_load
* Ingo Molnar mi...@kernel.org wrote:
Alternatively we could just use the following reboot order:
* 1) If the FADT has the ACPI reboot register flag set, try it
* 2) If still alive, write to the keyboard controller
* 3) If still alive, write to the ACPI reboot register again
* 4) If
Commit-ID: d122ab8d224a59aa0c3e4ba3540c6ab99556c3e3
Gitweb: http://git.kernel.org/tip/d122ab8d224a59aa0c3e4ba3540c6ab99556c3e3
Author: Ingo Molnar mi...@kernel.org
AuthorDate: Fri, 4 Apr 2014 08:41:26 +0200
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Fri, 4 Apr 2014 08:48:03
Hi Rob,
On Fri, Apr 4, 2014 at 12:16 AM, Rob Herring robherri...@gmail.com wrote:
--- a/arch/c6x/kernel/setup.c
+++ b/arch/c6x/kernel/setup.c
@@ -265,8 +265,8 @@ int __init c6x_add_memory(phys_addr_t start, unsigned
long size)
*/
notrace void __init machine_init(unsigned long dt_ptr)
Hi Xiubo,
On Fri, Apr 04, 2014 at 03:37:00PM +0800, Xiubo Li-B47053 wrote:
Subject: [PATCH] ASoC: fsl_sai: Fix Bit Clock Polarity configurations
The BCP bit in TCR4/RCR4 register rules as followings:
0 Bit clock is active high with drive outputs on rising edge
and sample inputs
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested.
These two typos were introduced in commit 1425052097b5 (gpio: add IRQ
chip helpers in gpiolib), which has just been merged.
include/linux/gpio/driver.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
[CC += Al Viro Linux, since they also discussed the point about
remote filesystems and /proc and /sys here:
http://thread.gmane.org/gmane.linux.file-systems/83641/focus=83713 .]
On 04/03/2014 05:38 PM, Eric W. Biederman wrote:
Michael Kerrisk (man-pages) mtk.manpa...@gmail.com writes:
(To:
* tip-bot for Ingo Molnar tip...@zytor.com wrote:
Commit-ID: d122ab8d224a59aa0c3e4ba3540c6ab99556c3e3
Gitweb: http://git.kernel.org/tip/d122ab8d224a59aa0c3e4ba3540c6ab99556c3e3
Author: Ingo Molnar mi...@kernel.org
AuthorDate: Fri, 4 Apr 2014 08:41:26 +0200
Committer: Ingo Molnar
On Thu, Apr 03, 2014 at 04:48:56PM +0200, Richard Genoud wrote:
I've met an endless (or at least very long) loop if I power down the usb
port on witch a usb wifi key is plugged.
(Ok, it's not very smart to power down a usb port when a usb key is in
used... but still, I think that should not
Hi Harini,
On Fri, Apr 4, 2014 at 5:00 AM, Harini Katakam
harinikatakamli...@gmail.com wrote:
+ num-cs = /bits/ 16 4;
What's going on with the /bits/ - is this something that's required for
the property?
The master-num-chipselect property is 16 bit but writing 4 here directly
Greg,
This pertains to commit 8ceee72808d1 (crypto: ghash-clmulni-intel -
use C implementation for setkey()) that has been pulled by Linus
during the current merge window.
It is missing two things:
- a cc to stable annotation
- a fix for the sparse warning below (change cast from __be64 to
On 04/04/2014 08:29 AM, Len Brown wrote:
Hi Daniel,
Interesting idea.
The benefit of this patch is to reduce power.
Have you been able to measure a power reduction, via power meter, or
via built-in RAPL power meter?
(turbostat will show RAPL watts, or if you have constant quantity of
work, use
On 03/04/2014 10:16, Daniel Lezcano wrote:
On 03/28/2014 12:13 PM, Gregory CLEMENT wrote:
Add the wfi, cpu idle and cpu deep idle power states support for the
Armada XP SoCs.
All the latencies and the power consumption values used at the
armada_370_xp_idle_driver structure are preliminary
On Thu, Apr 03, 2014 at 05:37:01PM +0200, Jakub Kiciński wrote:
On Thu, 3 Apr 2014 16:12:07 +0200, Richard Genoud wrote:
rt2x00usb_register_read_lock() calls rt2x00usb_vendor_req_buff_lock()
that calls rt2x00usb_vendor_request() which is already looping up to
REGISTER_BUSY_COUNT times.
Here is no difference between MAP_SHARED and MAP_PRIVATE.
do_mmap_pgoff()
switch (flags MAP_TYPE) {
case MAP_SHARED:
...
/* fall through */
case MAP_PRIVATE:
if (!(file-f_mode FMODE_READ))
return -EACCES;
get_user_pages(write=1, force=1) has always had odd behaviour on write-
protected shared mappings: although it demands FMODE_WRITE-access to the
underlying object (do_mmap_pgoff sets neither VM_SHARED nor VM_MAYWRITE
without that), it ends up with do_wp_page substituting private anonymous
On Fri, Apr 04, 2014 at 01:13:12AM +0100, Ben Hutchings wrote:
On Mon, 2014-03-31 at 14:23 +0100, Luis Henriques wrote:
3.5.7.33 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Hutchings b...@decadent.org.uk
[...]
Should be
On Thu, Apr 03, 2014 at 10:50:27PM +0100, Mark Brown wrote:
On Thu, Apr 03, 2014 at 03:32:15PM +0100, Charles Keepax wrote:
Currently, of_regulator_match does not increment the reference count of
the of_nodes it takes new references to. This could cause the node
pointer held to be invalid,
On 03.04.2014 15:50, Eric Dumazet wrote:
If bug is in tun.c you have this list of changes you could bisect
from :
# git log --oneline v3.13..v3.14 drivers/net/tun.c
6671b2240c54 tun: remove bogus hardware vlan acceleration flags from
vlan_features
99932d4fc03a netdevice: add queue
migrate_timer() is called when a CPU goes down and its timers are required to be
migrated to some other CPU. Its the responsibility of the users of the timer to
remove it before control reaches to migrate_timers().
As these were the pinned timers, the best we can do is: don't migrate these and
In order to quiesce a CPU on which Isolation might be required, we need to move
away all the timers queued on that CPU. There are two types of timers queued on
any CPU: ones that are pinned to that CPU and others can run on any CPU but are
queued on CPU in question. And we need to migrate only the
To isolate CPUs (isolate from hrtimers) from sysfs using cpusets, we need some
support from the hrtimer core. i.e. A routine hrtimer_quiesce_cpu() which would
migrate away all the unpinned hrtimers, but shouldn't touch the pinned ones.
This patch creates this routine.
Signed-off-by: Viresh Kumar
For networking applications, platforms need to provide one CPU per each user
space data plane thread. These CPUs shouldn't be interrupted by kernel at all
unless userspace has requested for some functionality. Currently, there are
background kernel activities that are running on almost every CPU,
1 - 100 of 1160 matches
Mail list logo
