> Sorry for not noticing this earlier but this has nothing to do with the
> remaining part of the patch.
> To be able to set this flag, you need to mark timer & perf interrupts.
> If you already use IRQF_TIMER for the timer and perf interrupts are
> already coming as NMU then you are done. But
On 12/18/2013 06:42 AM, Allen Pais wrote:
> index 554995d..aae5aa9 100644
> --- a/arch/sparc/Kconfig
> +++ b/arch/sparc/Kconfig
> @@ -27,6 +27,7 @@ config SPARC
> select HAVE_DMA_API_DEBUG
> select HAVE_ARCH_JUMP_LABEL
> select HAVE_GENERIC_HARDIRQS
> + select
On 12/18/2013 06:42 AM, Allen Pais wrote:
index 554995d..aae5aa9 100644
--- a/arch/sparc/Kconfig
+++ b/arch/sparc/Kconfig
@@ -27,6 +27,7 @@ config SPARC
select HAVE_DMA_API_DEBUG
select HAVE_ARCH_JUMP_LABEL
select HAVE_GENERIC_HARDIRQS
+ select IRQ_FORCED_THREADING
Sorry for not noticing this earlier but this has nothing to do with the
remaining part of the patch.
To be able to set this flag, you need to mark timer perf interrupts.
If you already use IRQF_TIMER for the timer and perf interrupts are
already coming as NMU then you are done. But please
In the attempt of get PREEMPT_RT working on sparc64 using
linux-stable-rt version 3.10.22-rt19+, the kernel crash
with the following trace:
[ 1487.027884] I7:
[ 1487.027885] Call Trace:
[ 1487.027887] [004967dc] rt_mutex_setprio+0x3c/0x2c0
[ 1487.027892] [004afe20]
In the attempt of get PREEMPT_RT working on sparc64 using
linux-stable-rt version 3.10.22-rt19+, the kernel crash
with the following trace:
[ 1487.027884] I7: rt_mutex_setprio+0x3c/0x2c0
[ 1487.027885] Call Trace:
[ 1487.027887] [004967dc] rt_mutex_setprio+0x3c/0x2c0
[ 1487.027892]
6 matches
Mail list logo