Re: Stupid user with user-space questions, matrix LED driving with user space code only.

[Jonathan Andrews <jon@jonshouse.co.uk>]

> > The dim pixel code is timing critical (but as I said only a tiny
> > fraction of the total CPU usage). What I need to do is grab the CPU and
> > prevent any context switch (IRQ or PREEMPT) for this period.
> why you want to do this?
Because I need an I/O pin to change state for a short accurately timed
period. If the scheduler is activated during the generation of this
pulse then the timing will be stretched, this stretching is seen as
bright flash by the viewer of the LED display. 

>  
> > I cant find a user space mechanism other than changing the kernel to
> > disable preemtion ? No simple /proc switch to turn it on/off ? If not
> > why - I cant be the only one who wants to toggle preemption off without
> > swapping kernels ?
> you can't disable pre-emption from user space.
Part of why I asked this here.

Why not !

I would expect a "/proc/sys/kernel/sched_preemption" that I could toggle
a 1 or 0 into to turn it on/off.  

>From a user perspective it seems a bit crap to have to change the kernel
if you have a workload that preemption is harmful to.  
In the case of something like the Raspberry Pi changing the kernel if
the distribution has not done the work for me sounds like real effort.
The kernel is tied to binary obscurity from broadcom... To build I need
a working cross compiler, toolchain, kernel sources, Pi specific patches
then to get everything in the correct place on an SD card containing two
filesystems.  Its possible but its not going to "just work" at my skill
level....
> > The other issue is that of IRQs, my dim pixels on the display seem to
> > flash brighter from time to time, this I assume is partly preemption
> > (maybe possibly) and partly IRQ handling (more likely) allowing context
> > switches or just taking a while on slow hardware.
> > 
> > I need only a tiny fraction of the runtime to be hard real time, on
> > intel in the past i've simply disabled IRQs briefly with some inline
> > assembler. 
> you shouldn't fiddle with irq's from user space but...
> > The Raspberry Pi board would also probably survive this as the only
> > active peripheral is ethenet, I suspect couple of missed IRQs would not
> > matter as once IRQs are re-enabled the USB/ethernet hardware will likely
> > have the data or it can be re-tried.  Does anyone have an example of a
> > dirty hack along these lines they can share with me :-) 
> 
> > Do I have any simple mechanism available to disable (or defer) kernel
> > IRQ handling briefly from user space code, I suspect not but no harm in
> > asking ?
> Use any sysfs to disable/enable the irq. This approach is very bad but
> as you said you wanted a hack.
Sounds interesting, can I have some more specific clues how. Device is
not intel or PCI so I need to toggle something relevant to ARMs native
interrupt system, do I still have anything I can toggle that is relevant
in "Linux raspberrypi 3.6.11+ #375 PREEMPT" /sys ?

Many thanks,
Jon