On 03/18/2015 08:26 PM, Andy Lutomirski wrote:
> Hi Linus-
>
> You seem to enjoy debugging these things. Want to give this a shot?
> My guess is a vmalloc fault accessing either old_rsp or kernel_stack
> right after swapgs in syscall entry.
The code is:
ENTRY(system_call)
Hi Andy,
Am 18.03.2015 um 20:26 schrieb Andy Lutomirski:
> Hi Linus-
>
> You seem to enjoy debugging these things. Want to give this a shot?
> My guess is a vmalloc fault accessing either old_rsp or kernel_stack
> right after swapgs in syscall entry.
>
> On Wed, Mar 18, 2015 at 12:03 PM,
On Wed, Mar 18, 2015 at 12:46 PM, Prarit Bhargava wrote:
> This patch splits rtc.txt into two separate files, one for the
> documentation itself, and the other for the rtctest.c file. The rtctest
> file is moved into the kernel tools/testing/selftests/timers directory.
> This will make automated
On 03/18, Andrey Wagin wrote:
>
> This patch fixes the problem. Oleg, could you send this path in the
> criu maillist?
Sure, will do.
Oleg.
--
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 3/18/15 1:43 PM, David Miller wrote:
From: David Ahern
Date: Wed, 18 Mar 2015 10:56:22 -0600
I am trying to understand why the perf tool on sparc fails to convert
kernel symbols when /proc/kcore is used. I have instrumented perf to
the point I can see that it drops symbols from kallsyms
On 2015/03/18, 1:07 PM, "Maxime Lorrillere"
wrote:
>From: Laure Millet
>
>This patch fixes lines over 80 characters
I think the newer rule is that strings shouldn't be split across lines.
That makes
the first hunk invalid, though the second one is OK.
Cheers, Andreas
>Signed-off-by: Laure
Em Wed, Mar 18, 2015 at 07:59:16PM +0100, Jiri Olsa escreveu:
> On Wed, Mar 18, 2015 at 03:50:48PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Mar 11, 2015 at 09:58:49AM +0100, Jiri Olsa escreveu:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> > > perf/build
> >
2015-03-18 21:50 GMT+03:00 Cyrill Gorcunov :
> On Wed, Mar 18, 2015 at 07:31:33PM +0100, Oleg Nesterov wrote:
>> On 03/18, Cyrill Gorcunov wrote:
>> >
>> > On Wed, Mar 18, 2015 at 06:48:43PM +0100, Oleg Nesterov wrote:
>> > >
>> > > Shot in a dark afer a quick grep: restore_gpregs() should
Hello,
On Wed, Mar 18, 2015 at 12:36:22PM -0700, Dmitry Torokhov wrote:
> Because they are not inherently problematic. I mean from the kernel POV
> they work fine, the question is if your userspace can deal with them or
> not. For example ChromeOS userspace is fine.
async already provides
rtctest.c checks to see if PIE is functioning by testing if 20 interrupts occur
at rates from 2HZ to 64HZ. While this check is good, it does not check to
see if the correct amount of time has actually passed. This misses
situations where the RTC may be operating at a higher or lower frequency
Fix your email client From header to use your full name.
The subject is very vague.
On Wed, Mar 18, 2015 at 08:08:48PM +0100, p...@amd48-systeme.lip6.fr wrote:
> Several warnings and errors of coding style rules corrected.
Which?
> Compile tested.
Put this under the --- cut off.
regards,
dan
On Wed, 18 Mar 2015, Roger Quadros wrote:
> To support OTG we want a mechanism to start and stop
> the HCD from the OTG state machine. Add usb_start_hcd()
> and usb_stop_hcd().
>
> Signed-off-by: Roger Quadros
There are a few problems in this proposed patch.
> +int usb_start_hcd(struct
Perhaps this is just a formatting error in my email client, but
shouldn't NULL be one more space over to line up with the '(' above?
On 03/18/2015 02:08 PM, p...@amd48-systeme.lip6.fr wrote:
+ rc = ll_intent_file_open(file->f_path.dentry,
+
We need this earlier in the boot process to allow various subsystems
to use configfs (e.g Industrial IIO).
Also, debugfs is at core_initcall level and configfs should be on
the same level from infrastructure point of view.
Suggested-by: Lars-Peter Clausen
Signed-off-by: Daniel Baluta
---
First
PER_CPU_VAR(kernel_stack) was set up in a way where it points
five stack slots below the top of stack.
Presumably, it was done to avoid one "sub $5*8,%rsp"
in syscall/sysenter code paths, where iret frame needs to be
created by hand.
Ironically, none of them benefits from this optimization,
FIXUP_TOP_OF_STACK is only necessary because we don't save %r11
to pt_regs->r11 on SYSCALL64 fast path, but we want ptrace to see
it populated.
Bite the bullet, add a single additional PUSH insn, and remove
FIXUP_TOP_OF_STACK.
RESTORE_TOP_OF_STACK is already a nop. Remove it too.
On SandyBridge
Confirmed - your fix solves TX problem in kernel.
- Leonid.
On 03/18/2015 10:34 AM, Leonid Yegoshin wrote:
Thank you, Markos!
It seems like one Samurai problem may be solved by your work -
right now I experience TX problem while I use NFS root.
Will test today.
- Leonid.
Markos Chandras
Documentation/rtc.txt is a combination of two files, a real documentation
file and a test program. Splitting these up into two files is a good idea
for automated testing. While testing on an AMD based system it was noticed
that the RTC was not behaving properly which lead to a possible bug in
On Tue, Mar 17, 2015 at 4:24 AM, Peter Zijlstra wrote:
> On Fri, Feb 20, 2015 at 11:49:49AM -0800, John Stultz wrote:
>> On Fri, Feb 20, 2015 at 6:29 AM, Peter Zijlstra wrote:
>> > @@ -489,7 +512,12 @@ static void timekeeping_update(struct ti
>> > memcpy(_timekeeper,
This patch splits rtc.txt into two separate files, one for the
documentation itself, and the other for the rtctest.c file. The rtctest
file is moved into the kernel tools/testing/selftests/timers directory.
This will make automated testing easier. Note that the only difference in
the rtc.txt
We lose a number of large insns there:
textdata bss dec hex filename
9863 0 098632687 entry_64_before.o
9671 0 0967125c7 entry_64.o
What's more important, we convert two "MOVQ $imm,off(%rsp)" to "PUSH $imm"
(the ones which fill
On 03/18/2015 04:27 AM, James Hogan wrote:
+ .align 4
doesn't this mean the first one & label might not be suitably aligned.
Would it be better to put this before the ld_d (no need for it after
$w31 case) and putting another .align 4 before the Lmsa_to and Lmsa_from
labels (so the label
Uck, my reply made the formatting even worse. I'm trying to say it
should look like this:
+rc = ll_intent_file_open(file->f_path.dentry,
+NULL, 0, it);
Not like this:
+rc = ll_intent_file_open(file->f_path.dentry,
+
We need this earlier in the boot process to allow various subsystems
to use configfs (e.g Industrial IIO).
Also, debugfs is at core_initcall level and configfs should be on
the same level from infrastructure point of view.
Suggested-by: Lars-Peter Clausen
Signed-off-by: Daniel Baluta
---
From: David Ahern
Date: Wed, 18 Mar 2015 10:56:22 -0600
> I am trying to understand why the perf tool on sparc fails to convert
> kernel symbols when /proc/kcore is used. I have instrumented perf to
> the point I can see that it drops symbols from kallsyms because it
> cannot find a
On 03/18/2015 01:24 PM, Scott Branden wrote:
This patchset attempts to standarize the naming of dt-bindings
documents based on the Broadcom vendor prefix of brcm.
Although there are no guidelines currently present for how to name
the dt-bindings document the "vendor,binding.txt" style is in use
On Wed, Mar 18 2015 at 10:12 -0600, Bjorn Andersson wrote:
On Thu 12 Mar 15:29 PDT 2015, Lina Iyer wrote:
On Fri, Feb 27 2015 at 15:30 -0700, Bjorn Andersson wrote:
>Add driver for Qualcomm Hardware Mutex block found in many Qualcomm
>SoCs.
>
>Based on initial effort by Kumar Gala
>
On 15-03-18 08:28 AM, Greg Kroah-Hartman wrote:
On Wed, Mar 18, 2015 at 12:16:22PM +0100, Nicolas Ferre wrote:
Le 17/03/2015 20:01, Alan Stern a écrit :
On Tue, 17 Mar 2015, Boris Brezillon wrote:
The EHCI IP only needs the UTMI/UPLL (uclk) and the peripheral (iclk)
clocks to work properly.
Hi All,
On 02/24/2015 06:12 PM, grygorii.stras...@linaro.org wrote:
On 02/05/2015 04:37 PM, grygorii.stras...@linaro.org wrote:
From: Grygorii Strashko
Setting a dev_pm_ops suspend/resume pair of callbacks but not a set of
hibernation callbacks means those pm functions will not be
called
Radim Krčmář writes:
> kvm_ioapic_update_eoi() wasn't called if directed EOI was enabled.
> We need to do that for irq notifiers. (Like with edge interrupts.)
Wow! It's interesting that this path is only hit with Xen as guest.
I always thought of directed EOI as a "security feature" since
On Wed, Mar 18, 2015 at 02:45:50PM -0400, Tejun Heo wrote:
> On Wed, Mar 18, 2015 at 11:37:31AM -0700, Dmitry Torokhov wrote:
> > I do not believe that we will be able to activate asynchronous probing
> > by default in the next 2, 3, 4 merge windows: distributions will have to
> > try and use it
As described in previous e-mail, we need to get informed when
the task, whose mm is monitored with uffd, calls fork().
The fork notification is the new uffd with the same regions
and flags as those on parent. When read()-ing from uffd the
monitor task would receive the new uffd's descriptor
The new API will report more than just the page-faults. The
reason for this is -- when the task whose mm we monitor with
uffd and the monitor task itself cannot cooperate with each
other, the former one can screw things up. Like this.
If task fork()-s the child process is detached from uffd and
Hi,
On the recent LSF Andrea presented his userfault-fd patches and
I had shown some issues that appear in usage scenarios when the
monitor task and mm task do not cooperate to each other on VM
changes (and fork()-s).
Here's the implementation of the extended uffd API that would help
us to
Reformat the existing code a bit to make it easier for
further patching.
Signed-off-by: Pavel Emelyanov
---
fs/userfaultfd.c | 37 -
1 file changed, 28 insertions(+), 9 deletions(-)
diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
index b4c7f25..6c9a2d6
Hi Thomas,
On Mon, Mar 16, 2015 at 06:11:52PM +0100, Thomas Niederprüm wrote:
> The 130X controllers are very similar from the configuration point of view.
> The configuration registers for the SSD1305/6/7 are bit identical (except the
> the VHCOM register and the the default values for clock
Hi Linus-
You seem to enjoy debugging these things. Want to give this a shot?
My guess is a vmalloc fault accessing either old_rsp or kernel_stack
right after swapgs in syscall entry.
On Wed, Mar 18, 2015 at 12:03 PM, Stefan Seyfried
wrote:
> Hi all,
>
> first, I'm kind of happy that I'm not
This patchset attempts to standarize the naming of dt-bindings
documents based on the Broadcom vendor prefix of brcm.
Although there are no guidelines currently present for how to name
the dt-bindings document the "vendor,binding.txt" style is in use by
some of the other vendors.
---
MIPS R5, MIPS R6 and MSA HW specs allow a broad range of address exception
on unaligned MSA load/store operations - from none unaligned up to
full support in HW. In practice, it is expected that HW can occasionally
triggers AdE for non-aligned data access (misalignment). It is usually
expected on
On Mon, Mar 16, 2015 at 06:11:50PM +0100, Thomas Niederprüm wrote:
> Currently the videomemory is allocated by kmalloc, making it a memory
> region that is not necessarily page aligend. This leads to problems
> upon mmap call, where the video memory's address gets aligned to the
> next page
On Sat, Mar 14, 2015 at 11:57:17AM +0800, Chen-Yu Tsai wrote:
> Since the phy core already supports specifying a regulator to handle
> during power up/down, it was decided to drop the regulator support
> in the sun9i usb phy driver.
>
> This patch switches the DT to the core bindings. This and
On 03/18/15 06:32, Georgi Djakov wrote:
> This patchset introduces the parent_map index tables, which solve the
> issue discussed here [1].
> While doing this, fix also some of the code around (patches 1 and 2)
>
> [1] https://lkml.org/lkml/2015/3/5/682
>
> Patchset based on clk-next.
The concept
> > The answer is no: it solves a different problem. Group read
> > is just fine granuality counting. It cannot be used
> > to sample for multiple events in parallel.
>
> But group read disables sampling for non-leader events so the number
> of total samples should be small, no?
Yes it's
This patch fixes these sparse warnings:
drivers/staging/fbtft/fbtft-sysfs.c:23:5: warning: symbol
'fbtft_gamma_parse_str' was not declared. Should it be static?
drivers/staging/fbtft/fbtft-sysfs.c:153:6: warning: symbol
'fbtft_expand_debug_value' was not declared. Should it be static?
On Wed, Mar 18, 2015 at 06:49:55PM +0100, Daniel Borkmann wrote:
> On 03/18/2015 06:14 PM, mancha wrote:
> ...
> >Patch 0001 fixes the dead store issue in memzero_explicit().
>
> Thanks! I have issued the fix for the memzero bug to Herbert in
> your authorship as discussed, also giving some more
On 03/16/2015 01:10 PM, Jonathan Corbet wrote:
> On Mon, 16 Mar 2015 11:58:53 -0400
> Prarit Bhargava wrote:
>
>> Documentation/rtc.txt is a combination of two files, a real documentation
>> file and a test program. Splitting these up into two files is a good idea
>> for automated testing.
>
This patch cleans the toshiba_bluetooth_add function by using the
recently introduced function toshiba_bluetooth_present, simplifying
its code and returning appropriate error values.
Also, disables the BT device at the removal of the driver, by using
the function toshiba_bluetooth_disable.
This patch cleans the toshiba_bluetooth_enable function, removing
some unneeded code and returning appropriate error values.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_bluetooth.c | 32
1 file changed, 12 insertions(+), 20 deletions(-)
diff
Bug 93911 reported a broken handling of the BT device, causing the
driver to get stuck in a loop enabling/disabling the device whenever
the device is deactivated by the kill switch as follows:
1. The user activated the kill switch, causing the system to generate
a 0x90 (status change) event
This patch introduces three new functions, which are going to be used
by the next patches.
The functions introduced are toshiba_bluetooth_present,
toshiba_bluetooth_status and toshiba_bluetooth_disable, which queries
the presence of the device, queries the status and disables the
device
This patch cleans the toshiba_bluetooth_enable function, removing
some unneeded code and returning appropriate error values.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_bluetooth.c | 32
1 file changed, 12 insertions(+), 20 deletions(-)
diff
On Wed, Mar 18, 2015 at 07:25:22PM +0100, Oleg Nesterov wrote:
> On 03/18, Cyrill Gorcunov wrote:
> >
> > On Wed, Mar 18, 2015 at 11:06:00AM -0700, Andy Lutomirski wrote:
> > > > --- a/arch/x86/crtools.c
> > > > +++ b/arch/x86/crtools.c
> > > > @@ -475,6 +475,7 @@ int restore_gpregs(struct
These patches introduce three new functions, cleaning up the driver
code, checking for errors and returning accordingly, and also fixes
bug 93911.
Azael Avalos (4):
toshiba_bluetooth: Add three new functions to the driver
toshiba_bluetooth: Clean up *_add function and disable BT device at
On 18 March 2015 at 11:25, Dan Carpenter wrote:
> Could you read your patches again and find other similar white space
> issues.
Done.
Best,
--
Lorenzo Stoakes
https:/ljs.io
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 18 March 2015 at 10:59, Dan Carpenter wrote:
> Call it a v2 patch. Put a note under the --- cut off line:
> v2: updated to apply to latest linux-next
>
> http://kernelnewbies.org/PatchTipsAndTricks
Since each changed patch in the resend already incorporates changes to
update to apply to the
On Wed, Mar 18, 2015 at 07:05:09PM +, Will Deacon wrote:
> (2) I believe Sudeep and Lorenzo have concerns about patch 13 (SMP init),
> so I'm assuming there will be additional patches from them that are
> required.
Bah, getting ahead of myself. This is in fact patch *12* of the
From: Laure Millet
This patch fixes lines over 80 characters
Signed-off-by: Laure Millet
Signed-off-by: Maxime Lorrillere
---
drivers/staging/lustre/lustre/llite/namei.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lustre/llite/namei.c
This patch annotates pointers as referring to I/O mapped memory where they ought
to be, removes now unnecessary ugly casts, eliminates an incorrect deref on I/O
mapped memory by using iowrite16 instead, and updates the pointer arithmetic
accordingly to take into account that the pointers are now
Hanjun,
On Wed, Mar 11, 2015 at 12:39:26PM +, Hanjun Guo wrote:
> This patch set already tested on multi platforms:
> - AMD Seattle board;
> - Cavium Thunder board;
> - Huawei D02 board;
> - Qualcomm ARM64 platform
>
> This version 10 patch set address some minor comments and collect
This patch takes into account that cursor->vstart, crtc->vScreen and
share->pvMem are pointers to memory-mapped I/O and thus we should use memset_io
to make this explicit. In addition, some architectures require special treatment
of memory-mapped I/O so the previous code could actually break
Hi all,
first, I'm kind of happy that I'm not the only one seeing this, and
thus my beloved Thinkpad can stay for a bit longer... :-)
Then, I'm mostly an amateur when it comes to kernel debugging, so bear
with me when I'm stumbling through the code...
Am 18.03.2015 um 19:03 schrieb Andy
From: Laure Millet
This patch fixes a quoted string split across lines.
Signed-off-by: Laure Millet
Signed-off-by: Maxime Lorrillere
---
drivers/staging/lustre/lustre/llite/namei.c |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git
On Wed, Mar 18, 2015 at 03:50:48PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 11, 2015 at 09:58:49AM +0100, Jiri Olsa escreveu:
> > hi,
> > moving features detection framework from perf to 'tools/build'
> > plus other minor fixes.
> >
> > v2 changes:
> > - omitted patch 1 from
Several warnings and errors of coding style rules corrected.
Compile tested.
Signed-off-by: Pierre-Yves Péneau
---
drivers/staging/lustre/lustre/llite/file.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/lustre/lustre/llite/file.c
From: Laure Millet
This patch fixes a coding style error in a pointer declaration.
Signed-off-by: Laure Millet
Signed-off-by: Maxime Lorrillere
---
drivers/staging/lustre/lustre/llite/namei.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Laure Millet
This fixes a missing blank line after declarations.
Signed-off-by: Laure Millet
Signed-off-by: Maxime Lorrillere
---
drivers/staging/lustre/lustre/llite/namei.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/lustre/lustre/llite/namei.c
Link the external IRQ controller irqc0 to the IRQC module clock, so it
can be power managed using that clock.
Signed-off-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a7791.dtsi| 9 +
include/dt-bindings/clock/r8a7791-clock.h | 3 +++
2 files changed, 12 insertions(+)
diff
Link the external IRQ controllers irqc0 and irqc1 to the IRQC module
clock, so they can be power managed using that clock.
Signed-off-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a73a4.dtsi| 11 +++
include/dt-bindings/clock/r8a73a4-clock.h | 1 +
2 files changed, 8
From: Laure Millet
This patch fixes a trailing whitespace in namei.c
Signed-off-by: Laure Millet
Signed-off-by: Maxime Lorrillere
---
drivers/staging/lustre/lustre/llite/namei.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/namei.c
Hi,
This patch series adds the IRQC clock to the device tree on SoCs that
have such a clock (r8a73a4 and r8a779x), and adds mininal runtime PM
support to the renesas-irqc driver, to make sure the clock is enabled
when needed by the external IRQ controller(s).
Before, the clock was assumed
This is just enough to let pm_clk_*() enable the functional clock, and
manage it for suspend/resume, if present.
Before, it was assumed enabled by the bootloader or reset state.
Signed-off-by: Geert Uytterhoeven
---
drivers/irqchip/irq-renesas-irqc.c | 8
1 file changed, 8
Link the external IRQ controller irqc0 to the IRQC module clock, so it
can be power managed using that clock.
Signed-off-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a7794.dtsi| 9 +
include/dt-bindings/clock/r8a7794-clock.h | 3 +++
2 files changed, 12 insertions(+)
diff
Signed-off-by: Geert Uytterhoeven
---
drivers/irqchip/irq-renesas-irqc.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/drivers/irqchip/irq-renesas-irqc.c
b/drivers/irqchip/irq-renesas-irqc.c
index 2ea3412fdf8cc668..2ce2edf8ec8ec182 100644
---
Link the external IRQ controller irqc0 to the IRQC module clock, so it
can be power managed using that clock.
Signed-off-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a7790.dtsi| 9 +
include/dt-bindings/clock/r8a7790-clock.h | 3 +++
2 files changed, 12 insertions(+)
diff
The external IRQ controller has a functional clock, which is used for
power management. Document it.
Fix a typo in the r8a73a4 SoC name while we're at it.
Signed-off-by: Geert Uytterhoeven
---
.../devicetree/bindings/interrupt-controller/renesas,irqc.txt | 4 +++-
1 file changed, 3
- Original Message -
> On Wed, Mar 18, 2015 at 04:52:14PM +, Mathieu Desnoyers wrote:
> > - Original Message -
> > > On Wed, Mar 18, 2015 at 12:23:02PM -0400, Mathieu Desnoyers wrote:
> > > > memory barriers in reader:1701557485 reads, 3129842 writes
> > > > signal-based
Em Wed, Mar 11, 2015 at 09:58:49AM +0100, Jiri Olsa escreveu:
> hi,
> moving features detection framework from perf to 'tools/build'
> plus other minor fixes.
>
> v2 changes:
> - omitted patch 1 from original version (Ingo)
> - added features build output dump (Arnaldo)
> - better scripting
When debugging the latencies on a 40 core box, where we hit 300 to
500 microsecond latencies, I found there was a huge contention on the
runqueue locks.
Investigating it further, running ftrace, I found that it was due to
the pulling of RT tasks.
The test that was run was the following:
On Wed, Mar 18, 2015 at 07:31:33PM +0100, Oleg Nesterov wrote:
> On 03/18, Cyrill Gorcunov wrote:
> >
> > On Wed, Mar 18, 2015 at 06:48:43PM +0100, Oleg Nesterov wrote:
> > >
> > > Shot in a dark afer a quick grep: restore_gpregs() should initialize ->ss?
> >
> > It hasn't been needed earlier, if
The cpu_do_idle() function is always used by the cpuidle drivers.
That led to have each driver including cpuidle.h and proc-fns.h, they are
always paired. That makes a lot of duplicate headers inclusion. Instead of
including both in each .c file, move the proc-fns.h header inclusion in the
With this change the cpuidle-arm64.c file calls the same function name
for both ARM and ARM64.
Signed-off-by: Daniel Lezcano
Acked-by: Kevin Hilman
Acked-by: Rob Herring
---
arch/arm64/include/asm/cpuidle.h | 4 ++--
arch/arm64/kernel/cpuidle.c | 2 +-
drivers/cpuidle/cpuidle-arm64.c |
Call the common ARM/ARM64 'arm_cpuidle_suspend' instead of cpu_suspend function
which is specific to ARM64.
Signed-off-by: Daniel Lezcano
Acked-by: Kevin Hilman
Acked-by: Rob Herring
---
drivers/cpuidle/cpuidle-arm64.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Some architectures have some cpus which does not support idle states.
Let the underlying low level code to return -ENOSYS when it is not
possible to set an idle state.
Signed-off-by: Daniel Lezcano
---
drivers/cpuidle/cpuidle-arm.c | 45 +--
1 file
The current state of the different cpuidle drivers is the different PM
operations are passed via the platform_data using the platform driver
paradigm.
This approach allowed to split the low level PM code from the arch specific
and the generic cpuidle code.
Unfortunately there are complaints
In the next patch, this driver will be common across ARM/ARM64. Remove all refs
to ARM64 as it will be shared with ARM32.
Signed-off-by: Daniel Lezcano
Acked-by: Kevin Hilman
Acked-by: Rob Herring
---
drivers/cpuidle/cpuidle-arm64.c | 34 +-
1 file changed, 17
On Mon, Mar 16, 2015 at 08:47:25AM +, Marc Zyngier wrote:
> Hi Stephen, Jason,
>
> On 16/03/15 03:47, Stephen Rothwell wrote:
> > Hi Jason,
> >
> > Today's linux-next merge of the irqchip tree got a conflict in
> > arch/arm/mach-exynos/suspend.c between commit ace283a04a4a ("ARM:
> > EXYNOS:
ARM32 and ARM64 have the same DT definitions and the same approaches.
The generic ARM cpuidle driver can be put in common for those two
architectures.
Signed-off-by: Daniel Lezcano
Acked-by: Kevin Hilman
Acked-by: Rob Herring
---
drivers/cpuidle/Kconfig| 7
Change the functions name:
arm_cpuidle_suspend => arm_idle
arm_cpuidle_init=> arm_idle_cpu_init
Signed-off-by: Daniel Lezcano
---
arch/arm/include/asm/cpuidle.h | 4 ++--
arch/arm/kernel/cpuidle.c| 4 ++--
arch/arm64/include/asm/cpuidle.h | 6 +++---
arch/arm64/kernel/cpuidle.c
On Mon, Mar 16, 2015 at 11:04:58AM +0100, Thierry Reding wrote:
> On Mon, Mar 16, 2015 at 02:55:08PM +1100, Stephen Rothwell wrote:
> > * PGP Signed by an unknown key
> >
> > Hi Jason,
> >
> > Today's linux-next merge of the irqchip tree got a conflict in
> > arch/arm/mach-tegra/irq.c between
There is a big number of cpuidle drivers for the ARM architecture.
These drivers have been cleaned up and grouped into the drivers/cpuidle
directory to keep track of the changes more easily and ensure the code
is following the same scheme across the drivers.
That had the benefit of simplifying
On Wed, Mar 18, 2015 at 11:20:08AM -0700, Andy Lutomirski wrote:
> >
> > Basically the initial registers values are fetched with ptrace
> > when program is been dumped, then on restore we copy them back
> > into sigcontext. That said we don't mangle fs/gs anyhow simply
> > restore the values back
On Wed, Mar 18, 2015 at 11:37:31AM -0700, Dmitry Torokhov wrote:
> I do not believe that we will be able to activate asynchronous probing
> by default in the next 2, 3, 4 merge windows: distributions will have to
> try and use it and see if they are ready for it. However there are
Async provides
On Wed, Mar 18, 2015 at 11:02:27AM +0100, Borislav Petkov wrote:
> I don't like the ifdeffery in your solution and would like to try to fix
> it in a cleaner way. Unless you come up with a better solution first.
Ok, how about this below? It is more involved but finds and loads the
microcode
kvm_ioapic_update_eoi() wasn't called if directed EOI was enabled.
We need to do that for irq notifiers. (Like with edge interrupts.)
Fix it by skipping EOI broadcast only.
Bug: https://bugzilla.kernel.org/show_bug.cgi?id=82211
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/ioapic.c | 4 +++-
On Wed, Mar 11, 2015 at 12:39:41PM +, Hanjun Guo wrote:
> Introduce ACPI_IRQ_MODEL_GIC which is needed for ARM64 as GIC is
> used, and then register device's gsi with the core IRQ subsystem.
>
> acpi_register_gsi() is similar to DT based irq_of_parse_and_map(),
> since gsi is unique in the
On Wed, Mar 18, 2015 at 02:27:42PM -0400, Tejun Heo wrote:
> Hello, Dmitry.
>
> On Wed, Mar 18, 2015 at 11:23:18AM -0700, Dmitry Torokhov wrote:
> > > Is this even useful for most drivers?
> >
> > Define useful. In my tests I was able to shave 2-3 seconds (out of 8-10)
> > of boot time for the
Sorry for the previous messed up email.
Here's a patch.
-- >8 --
Subject: [PATCH] arm,x86: limit strcmp() rc to {-1,0,1}
Signed-off-by: Arjun Sreedharan
---
arch/arm/boot/compressed/string.c | 2 +-
arch/x86/boot/string.c| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
On Wed, Mar 11, 2015 at 12:39:43PM +, Hanjun Guo wrote:
> Using the information presented by GTDT (Generic Timer Description Table)
> to initialize the arch timer (not memory-mapped).
>
> CC: Daniel Lezcano
> CC: Thomas Gleixner
> Originally-by: Amit Daniel Kachhap
> Tested-by: Suravee
On 03/18, Cyrill Gorcunov wrote:
>
> On Wed, Mar 18, 2015 at 06:48:43PM +0100, Oleg Nesterov wrote:
> >
> > Shot in a dark afer a quick grep: restore_gpregs() should initialize ->ss?
>
> It hasn't been needed earlier, if this would help it means abi is broken, no?
> :)
> Otherwise I don't
From: Martin Kepplinger
The MMA8653FC is a low-power, three-axis, capacitive micromachined
accelerometer with 10 bits of resolution with flexible user-programmable
options.
Embedded interrupt functions enable overall power savings, by relieving the
host processor from continuously polling data,
301 - 400 of 2046 matches
Mail list logo
