<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Virtualization on Nalar</title>
    <link>https://nalar.dev/tags/virtualization/</link>
    <description>Recent content in Virtualization on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/virtualization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IOMMU Translates Device DMA Addresses and Limits Memory Access</title>
      <link>https://nalar.dev/iommu-translates-device-dma-addresses-and-limits-memory-access/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/iommu-translates-device-dma-addresses-and-limits-memory-access/</guid>
      <description>&lt;p&gt;High-speed devices often move data without asking the CPU to copy every byte. Direct memory access, or DMA, lets a device read from or write to system memory through addresses supplied by software. That speed also creates a control problem: unrestricted DMA could let a faulty or compromised device touch memory that belongs to the kernel or another workload.&lt;/p&gt;&#xA;&lt;p&gt;An input-output memory management unit, commonly called an IOMMU, sits on the device side of this path. It translates device-visible DMA addresses into physical memory addresses and checks whether the requested access is permitted.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
