22 Mar
2007
22 Mar
'07
7:02 a.m.
Had a qemu session for dynebolic request this:
sudo echo 1024 > /proc/sys/dev/rtc/max-user-freq
Wasn't this set up in the kernel or some sysconfig somewhere? The original
content was "64". definitely not good. I once had Rosegarden request
something like this as well and thought I had fixed it.
Anyway, there is nothing in .config. The rt-patched kernel .config has entries
for high hardware timer set but I am using an older computer.
22 Mar
22 Mar
7:23 a.m.
David Baron wrote:
Had a qemu session for dynebolic request this:
sudo echo 1024 > /proc/sys/dev/rtc/max-user-freq
Wasn't this set up in the kernel or some sysconfig somewhere? The original
content was "64". definitely not good. I once had Rosegarden request
something like this as well and thought I had fixed it.
Anyway, there is nothing in .config. The rt-patched kernel .config has entries
for high hardware timer set but I am using an older computer.
hi,
on debian you can just add the line 'dev.rtc.max-user-freq=1024' to
/etc/sysctl.conf.
cheers,
doc
7:36 a.m.
On Thursday 22 March 2007, Dragan Noveski wrote:
David Baron wrote:
And on any system having sysfs you can simply write the desired value to
/proc/sys/dev/rtc/max-user-freq
I.e. by:
echo 1024 > /proc/sys/dev/rtc/max-user-freq
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
Had a qemu session for dynebolic request this:
sudo echo 1024 > /proc/sys/dev/rtc/max-user-freq
Wasn't this set up in the kernel or some sysconfig somewhere? The
original content was "64". definitely not good. I once had Rosegarden
request something like this as well and thought I had fixed it.
Anyway, there is nothing in .config. The rt-patched kernel .config has
entries for high hardware timer set but I am using an older computer.
hi,
on debian you can just add the line 'dev.rtc.max-user-freq=1024' to
/etc/sysctl.conf. 
9:39 a.m.
New subject: [linux-audio-user] Re: High Resolution Timing
Dragan Noveski escribe:
on debian you can just add the line
'dev.rtc.max-user-freq=1024' to
/etc/sysctl.conf.
And sysctl -p as root.
Cordially, Ismael
--
Ismael Valladolid Torres m. +34679156321
La media hostia j. ivalladt(a)gmail.com
http://lamediahostia.blogspot.com/
12:11 p.m.
On 3/22/07, David Baron <d_baron(a)012.net.il> wrote:
Wasn't this set up in the kernel or some sysconfig
somewhere? The original
content was "64". definitely not good. I once had Rosegarden request
something like this as well and thought I had fixed it.
I think it's time to change the default to 1024. That default of 64
is ancient - the point was to not allow users to kill a slow machine
like a 386 or 486 with excessive interrupts. I've been meaning to
submit a patch to LKML...
Lee
12:24 p.m.
On Thursday 22 March 2007, Lee Revell wrote:
On 3/22/07, David Baron <d_baron(a)012.net.il>
wrote:
Or is the default configurable in the kernel? If not, maybe simply make it
user configurable at build time..
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
Wasn't this set up in the kernel or some
sysconfig somewhere? The
original content was "64". definitely not good. I once had Rosegarden
request something like this as well and thought I had fixed it.
I think it's time to change the default to 1024. That default of 64
is ancient - the point was to not allow users to kill a slow machine
like a 386 or 486 with excessive interrupts. I've been meaning to
submit a patch to LKML...
Lee 
12:45 p.m.
Florian Schmidt wrote:
On Thursday 22 March 2007, Lee Revell wrote:
Or even, perhaps, at run time?: echo 1024 > /sys/devices/system/timer/...
On 3/22/07, David Baron
<d_baron(a)012.net.il> wrote:
Or is the default configurable in the kernel? If not, maybe simply make it
user configurable at build time..
Flo
Wasn't this set up in the kernel or some
sysconfig somewhere? The
original content was "64". definitely not good. I once had Rosegarden
request something like this as well and thought I had fixed it.
I think it's time to change the default to 1024. That default of 64
is ancient - the point was to not allow users to kill a slow machine
like a 386 or 486 with excessive interrupts. I've been meaning to
submit a patch to LKML...
Lee
12:47 p.m.
On 3/22/07, Florian Schmidt <mista.tapas(a)gmx.net> wrote:
Or is the default configurable in the kernel? If not,
maybe simply make it
user configurable at build time..
No, it's not. And it's utterly trivial to generate way more than 1024
interrupts per second as an unprivileged user already. I think it's
better to just raise it to a useful value.
Lee
2:08 p.m.
On Thursday 22 March 2007, Lee Revell wrote:
On 3/22/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
Ok, true :)
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
Or is the default configurable in the kernel? If
not, maybe simply make
it user configurable at build time..
No, it's not. And it's utterly trivial to generate way more than 1024
interrupts per second as an unprivileged user already. I think it's
better to just raise it to a useful value.
11:41 p.m.
Florian Schmidt wrote:
On Thursday 22 March 2007, Lee Revell wrote:
look, here it is set like:
nowhiskey@murija2:~$ cat /proc/sys/dev/rtc/max-user-freq
8192
nowhiskey@murija2:~$
and it works good for me.
do you think. than might be ok?
cheers,
doc
On 3/22/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
Ok, true :)
Flo
Or is the default configurable in the kernel? If
not, maybe simply make
it user configurable at build time..
No, it's not. And it's utterly trivial to generate way more than
1024
interrupts per second as an unprivileged user already. I think it's
better to just raise it to a useful value.
24 Mar
24 Mar
7:10 a.m.
Florian Schmidt wrote:
> On Thursday 22 March 2007, Lee Revell wrote:
>
>> On 3/22/07, Florian Schmidt <mista.tapas(a)gmx.net> wrote:
>>
>>> Or is the default configurable in the kernel? If not, maybe simply make
>>> it user configurable at build time..
>>>
>> No, it's not. And it's utterly trivial to generate way more than 1024
>> interrupts per second as an unprivileged user already. I think it's
>> better to just raise it to a useful value.
>>
>
> Ok, true :)
hey,
I just took a good look at my config, an the default actually is 1024
(at boot time). My kernel is 2.6.18. For quite a few versions now I
had an option called CONFIG_HZ_1000 that is used to set the boot time
default value.
Cheers,
--
__________________
Marc-Olivier Barre,
Markinoko.
7:40 a.m.
On Saturday 24 March 2007, Marc-Olivier Barre wrote:
Erm, CONFIG_HZ is not related to the RTC. And i didn't know a kernel compile
time option for configuring the default max user freq for rtc existed.. Mind
to let us know more [i.e. the name of the config option?]..
Lee's proposal was to change the default max frequency an ordinary user could
set the rtc to from 64hz to something usable like 1024 hz. I would even plea
for going higher.. I.e. 4096hz.
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
Florian
Schmidt wrote:
> On Thursday 22 March 2007, Lee Revell wrote:
>> On 3/22/07, Florian Schmidt <mista.tapas(a)gmx.net> wrote:
>>> Or is the default configurable in the kernel? If not, maybe simply
>>> make it user configurable at build time..
>>
>> No, it's not. And it's utterly trivial to generate way more than 1024
>> interrupts per second as an unprivileged user already. I think it's
>> better to just raise it to a useful value.
>
> Ok, true :)
hey,
I just took a good look at my config, an the default actually is 1024
(at boot time). My kernel is 2.6.18. For quite a few versions now I
had an option called CONFIG_HZ_1000 that is used to set the boot time
default value.
6483
days inactive
6485
days old
linux-audio-user@lists.linuxaudio.org
11 comments
7 participants
participants (7)
-
David Baron -
Dragan Noveski -
Florian Schmidt -
Garett Shulman -
Ismael Valladolid Torres -
Lee Revell -
Marc-Olivier Barre