<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Computer-Architecture on grit8086</title><link>https://grit8086.github.io/tags/computer-architecture/</link><description>Recent content in Computer-Architecture on grit8086</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 03 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://grit8086.github.io/tags/computer-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Computer Architecture for Reverse Engineers and Malware Developers</title><link>https://grit8086.github.io/posts/computer-architecture/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0800</pubDate><guid>https://grit8086.github.io/posts/computer-architecture/</guid><description>&lt;h1 id="computer-architecture-for-reverse-engineers-and-malware-developers"&gt;Computer Architecture for Reverse Engineers and Malware Developers&lt;/h1&gt;
&lt;p&gt;Before you can break a program you have to know where it lives and how it runs.&lt;/p&gt;
&lt;p&gt;We start with memory, because the CPU spends most of its life waiting on it. How storage is layered from registers down to disk. Why DRAM is slow. What cache is actually for. How virtual memory hands every process a private view of the machine and enforces it in hardware. Then the CPU itself, what it does with an instruction and which registers you need to recognise. Then the stack, where the first two meet.&lt;/p&gt;</description></item></channel></rss>