Re: [PATCH] powerpc: re-enable dynticks

On Fri, Feb 13, 2015 at 01:38:36PM -0600, Paul Clarke wrote: > implement arch_irq_work_has_interrupt() for powerpc > > Commit 9b01f5bf3 introduced a dependency on "IRQ work self-IPIs" for > full dynamic ticks to be enabled, by expecting architectures to > implement a suitable arch_irq_work_has_int

[PATCH] powerpc: re-enable dynticks

implement arch_irq_work_has_interrupt() for powerpc Commit 9b01f5bf3 introduced a dependency on "IRQ work self-IPIs" for full dynamic ticks to be enabled, by expecting architectures to implement a suitable arch_irq_work_has_interrupt() routine. Several arches have implemented this routine, in

embedding dtb file into kernel

I'm having trouble figuring out how to embed a dtb file into my kernel. I'm thinking that there should be a standard, architecture independent facility for this akin to initramfs, yes? Could someone please either point me to the standard facility, relevant doc, a currently building board that

Re: suspicious RCU usage clockevents_lock, tick_broadcast_lock, hrtimer_bases.lock

On Fri, Feb 13, 2015 at 12:52:45PM +0530, Preeti U Murthy wrote: > On 02/13/2015 10:57 AM, Preeti U Murthy wrote: > > On 02/13/2015 06:27 AM, Sam Bobroff wrote: > >> Hello, > >> > >> I'm receiving this while booting a vanilla 3.19 kernel on a Power 8 > >> machine: > > > > Does the below patch fix

[PATCH v2] powerpc/powernv: Check image loaded or not before calling flash

Present code checks for update_flash_data in opal_flash_term_callback(). update_flash_data has been statically initialized to zero, and that is the value of FLASH_IMG_READY. Also code update initialization happens during subsys init. So if reboot is issued before the subsys init stage then we endu

[PATCH] powerpc/powernv: Check image loaded or not before calling flash

Present code checks for update_flash_data in opal_flash_term_callback(). update_flash_data has been statically initialized to zero, and that is the value of FLASH_IMG_READY. Also code update initialization happens during subsys init. So if reboot is issued before the subsys init stage then we endu

[PATCH v3 2/3] powerpc: Relax secure computing on syscall entry trace

The secure_computing_strict will just force the kernel to panic on secure_computing failure. Once SECCOMP_FILTER support is enabled in the kernel, syscalls can be denied without system failure. Signed-off-by: Bogdan Purcareata --- arch/powerpc/kernel/ptrace.c | 4 +++- 1 file changed, 3 insertio

[PATCH v3 3/3] powerpc: Enable HAVE_ARCH_SECCOMP_FILTER

Signed-off-by: Bogdan Purcareata --- arch/powerpc/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig index 22b0940..2588b57 100644 --- a/arch/powerpc/Kconfig +++ b/arch/powerpc/Kconfig @@ -104,6 +104,7 @@ config PPC select HAVE_EFFICIEN

[PATCH v3 1/3] powerpc: Don't force ENOSYS as error on syscall fail

In certain scenarios - e.g. seccomp filtering with ERRNO as default action - the system call fails for other reasons than the syscall not being available. The seccomp filter can be configured to store a user-defined error code on return from a blacklisted syscall. Don't always set ENOSYS on do_sysc

[PATCH v3 0/3] powerpc: Enable seccomp filter support

Add the missing pieces in order to enable SECCOMP_FILTER on PowerPC architectures, and enable this support. Testing has been pursued using libseccomp with the latest ppc support patches [1][2], on Freescale platforms for both ppc and ppc64. ppc64le support is untested. [1] https://groups.google.c