pipedal_kconfig cli usage

[mockbot]

Hello,
during some debugging sessions and install tests, I've noticed, that the pipedal_kconfig terminal ui is not nice to handle for me... because wrong or poor terminal emulation, I was not able to select the realtime kernel options and save it.
Now my question: is it possible to use pipedal_kconfig with commadline optiones without using the ui?

I had situation, where I was not able to handle the ui and the system was unresponsible for user interactions, because of (maybe) wrong/missing kernel parameters.

Pipedal is a beast and I was not able to reconfigure anything - all cli interactions were delayed for minues ;-)

It's cosmetic, but I was not sure...

FYI: I was playing with routed pipedal environments inside VMs !!!
Windows10 with browser====>Router VM====>PiPedal
All devices are VMs!!! using VirtualBox ;-(

I was trying to setup a reproducable environment to debug the issue with remote access to pipedal ui from outside of the local broadcast subnet ...
Browser-SubnetA---Router/Firewall---SubnetB-PiPdal

[rerdavies]

PiPedal will not run in a VM.

I suspect that the VM scheduler will not be able to properly schedule PiPedal's realtime threads. And I also suspect that, although you can reserve a USB device for exclusive use by a VM, you cannot reserve the USB bridge devices in front of the audio device for a particular VM. Things are not going to run well unless the USB audio device (and perhaps it's associated USB bridge devices) are completely de-virtualized. I have tried it, but gave up pretty quickly.

CLI-interactions being delayed for minutes: very possibly a problem with incorrect virtualization of realtime threads, and an audio device that is constantly overrunning.

To reconfigure Ubuntu to use a PREEMPT scheduler, edit the file /etc/default/grub'. Look for the line that starts with GRUB_CMDLINE_LINUX_DEFAULT=` and add the following arguments.

 threadirqs preempt=full

Save the results and then run

update-grub

If you get further than I did, let me know. But I am currently of the opinion that it just cannot be done.

Things you might pursue if you really must:

• The USB audio device must definitely be de-virtualized, and reserved for exclusive use by the Pipedal VM.
• Reserving CPU cores might help.
• I'm not sure what provisions there are for de-virtualizing IRS, or setting ISR priorities. The VM host will need to give highest priority to USB audio IRS.

Beyond that, I don't think I can give you much help.

[rerdavies]

PS: I have a fix for the routing issue. It will show up in the next release of PiPedal (either today or tomorrow).