--- On Thu, 6/23/11, Natanael Olaiz <nolaiz@xxxxxxxxx> wrote: > From: Natanael Olaiz <nolaiz@xxxxxxxxx> > Subject: Re: Kernel 2.6.39 > To: linux-audio-user@xxxxxxxxxxxxxxxxxxxx > Date: Thursday, June 23, 2011, 6:05 AM > Hi, > > Rui Nuno Capela wrote: > > On 06/23/2011 07:17 AM, Ralf Mardorf wrote: > >> > >> I used the config from the self-build kernel > 2.6.33.9-rt31 and run > >> oldconfig only to configure 2.6.39. I didn't make > music until now using > >> this kernel. Yes, I wish to "emulate" the > PREEMPT_RT, since common > >> PREEMPT only kernels never did, what I needed. > >> > >> What do I need to set? > >> > >> $ cat config-2.6.39.1 | grep PREEMPT > >> CONFIG_TREE_PREEMPT_RCU=y > >> CONFIG_PREEMPT_RCU=y > >> CONFIG_PREEMPT_NOTIFIERS=y > >> # CONFIG_PREEMPT_NONE is not set > >> # CONFIG_PREEMPT_VOLUNTARY is not set > >> CONFIG_PREEMPT=y > >> > >> IIUC this is correct?! > >> > > > > yes. > > > > and don't forget to add "threadirqs" to your kernel > bootloader > > line--only then you'll get "rtirq" to do its magic as > it used to do on > > a genuine -rt kernel. > > > > I'm just setting up a new computer, and I also installed > the same 2.6.39 > kernel... > I guess that passing "threadirqs" as a kernel argument is > equivalent to > have CONFIG_IRQ_FORCED_THREADING=y as a kernel option. Am I > right? > no it's not. One is a boot argument, the other is a kernel compilation config option which matters if you compile the kernel. The boot argument will of course only work at runtime if the config option had been turned on before compiling the kernel. J. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
