hard-real-time

I've just built and set up a vanilla Linux kernel with the RT patch applied. Everything went fine and I can now correctly boot into the new kernel. What leaves me wondering is this: I have a simulator program that I've made in C, and I want it to execute in hard real time mode, as should be allowed by the new kernel. Probably the whole simulator doesn't need to be run with real-time priority, but some of the tasks inside do. How can I accomplish this? I take it that simply running the program won't do. andersoj If you are asking how to run some of the threads in real-time context, and others

I have read the definitions for the different notions of real-time , and the examples provided for hard and soft real-time systems make sense to me. But, there is no real explanation or example of a firm real-time system. According to the link above: Firm: Infrequent deadline misses are tolerable, but may degrade the system's quality of service. The usefulness of a result is zero after its deadline. Is there a clear distinction between firm real-time vs. hard or soft real-time, and is there a good example that illustrates that distinction? In comments, Charles asked that I submit tag wikis for

I've been curious to understand if it is possible to apply the power of Haskell to embedded realtime world, and in googling have found the Atom package. I'd assume that in the complex case the code might have all the classical C bugs - crashes, memory corruptions, etc, which would then need to be traced to the original Haskell code that caused them. So, this is the first part of the question: "If you had the experience with Atom, how did you deal with the task of debugging the low-level bugs in compiled C code and fixing them in Haskell original code ?" I searched for some more examples for