<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Real-Time on Christian Spoo</title><link>https://www.christian-spoo.de/tags/real-time/</link><description>Recent content in Real-Time on Christian Spoo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Jul 2026 19:47:18 +0200</lastBuildDate><atom:link href="https://www.christian-spoo.de/tags/real-time/index.xml" rel="self" type="application/rss+xml"/><item><title>How miniOS began: chasing real-time latency in userspace</title><link>https://www.christian-spoo.de/posts/2026/07/how-minios-began-chasing-real-time-latency-in-userspace/</link><pubDate>Sat, 18 Jul 2026 12:00:00 +0200</pubDate><guid>https://www.christian-spoo.de/posts/2026/07/how-minios-began-chasing-real-time-latency-in-userspace/</guid><description>&lt;p&gt;I recently published &lt;a href="https://github.com/tehplague/miniOS" target="_blank"&gt;miniOS&lt;/a&gt; on GitHub, a hobby x86_64 kernel I&amp;rsquo;ve been poking at on and off for years.
Docs are &lt;a href="https://www.christian-spoo.de/docs/minios/"&gt;here&lt;/a&gt; if you want the technical deep-dive. But before miniOS was a kernel with SMP scheduling and a network stack, it was a small test harness I wrote during university to answer one specific question.&lt;/p&gt;
&lt;h2 id="the-question"&gt;The question&lt;/h2&gt;
&lt;p&gt;Back then, &lt;a href="https://xenomai.org/" target="_blank"&gt;Xenomai&lt;/a&gt; and &lt;a href="https://en.wikipedia.org/wiki/RTLinux" target="_blank"&gt;RTLinux&lt;/a&gt; already existed, and both gave you hard real-time guarantees by running your time-critical code as a kernel task, next to (or underneath) a regular Linux kernel.
That works, but it means your real-time code has to live in kernel space, with everything that implies for development, debugging, and safety.&lt;/p&gt;</description></item></channel></rss>