[LAU] kernel release: which one?

[hermann meyer]

Am 24.08.2013 15:03, schrieb Barney Holmes:
> Quoting hermann meyer <brummer- at web.de>:
>
>> Am 24.08.2013 14:25, schrieb Ralf Mardorf:
>>> On Sat, 2013-08-24 at 14:13 +0200, hermann meyer wrote:
>>>> CONFIG_NO_HZ is available, but CONFIG_NO_HZ_FULL still isn't
>>> But it was. From a private mail a while ago:
>>>
>>> On Tue, 2013-08-13 at 19:01 +0200, Joakim Hernberg wrote:
>>>> jack at tor /home/jack $ uname -a
>>>> Linux tor 3.10.6-rt3-1-rt #1 SMP PREEMPT RT Tue Aug 13 13:59:13 CEST
>>>> 2013 x86_64 GNU/Linux
>>>> jack at tor /home/jack $ zgrep _HZ /proc/config.gz
>>>> CONFIG_NO_HZ_COMMON=y
>>>> # CONFIG_HZ_PERIODIC is not set
>>>> CONFIG_NO_HZ_IDLE=y
>>>> # CONFIG_NO_HZ_FULL is not set
>>>> CONFIG_NO_HZ=y
>>>> # CONFIG_HZ_100 is not set
>>>> # CONFIG_HZ_250 is not set
>>>> # CONFIG_HZ_300 is not set
>>>> CONFIG_HZ_1000=y
>>>> CONFIG_HZ=1000
>>>> jack at tor /home/jack $
>>> I was willing to test the kernel when it's enabled, but the kernel did
>>> cause an issue on my machine already when it was disabled.
>>>
>> Here is what I get
>>
>> uname -a
>> Linux box 3.10.9-rt5 #1 SMP PREEMPT RT Fri Aug 23 11:14:14 CEST 2013 
>> i686 GNU/Linux
>>
>> zgrep _HZ /proc/config.gz
>> CONFIG_HZ_PERIODIC=y
>> # CONFIG_NO_HZ_IDLE is not set
>> # CONFIG_NO_HZ is not set
>> # CONFIG_HZ_100 is not set
>> # CONFIG_HZ_250 is not set
>> # CONFIG_HZ_300 is not set
>> CONFIG_HZ_1000=y
>> CONFIG_HZ=1000
>>
>> This is plain vanila +rt patch.
>>
>

Aha, found out why I haven't the  CONFIG_NO_HZ_FULL option,
it is marked as 64bit only, but I run i686,

https://groups.google.com/forum/#!topic/linux.kernel/nq3HSPY3-Vg
>  - it's marked 64-bit only at the moment - the 32-bit support patch is
>    small but did not get ready in time. 



> There are some reasons for not having to set some of these high 
> resolution timers, especially if you are using MIDI through Jack. See 
> - http://www.linuxmusicians.com/viewtopic.php?f=27&t=10058&p=44078#p43871
>