<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Can We Prove Time Protection? · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1901.08338/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1901.08338/feed.xml" rel="self" type="application/rss+xml" /><item><title>Can We Prove Time Protection? — mentioned by GregarianChild</title><link>https://news.ycombinator.com/item?id=26342279</link><guid isPermaLink="false">urn:hackerpapers:mention:1901.08338:26342279</guid><pubDate>Thu, 04 Mar 2021 13:44:52 GMT</pubDate><description>&lt;p&gt;That would be great. But isn&amp;#x27;t there a danger, that such a CPU, at least if implemented naievely, would basically mostly idle, since modern OoO processors schedule memory access dynamically? For hard real-time tasks, some CPUs don&amp;#x27;t have caches, to make timing more predictable, but there is a heavy performance penalty to be paid for that predictability. Are you familiar with works like [1]? That is thinking in this direction, but from a different angle. [1] G. Heiser, G. Klein, T. Murray, Can We Prove Time Protection?. https://arxiv.org/pdf/1901.08338.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1901.08338/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.OS</category></item><item><title>Can We Prove Time Protection? — HN submission</title><link>https://news.ycombinator.com/item?id=19047609</link><guid isPermaLink="false">urn:hackerpapers:submission:1901.08338:19047609</guid><pubDate>Thu, 31 Jan 2019 18:57:38 GMT</pubDate><description>&lt;p&gt;Can We Prove Time Protection?&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;27 points; 3 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1901.08338/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.OS</category></item></channel></rss>
