# Explore secure device attach in Arm CCA Realms

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-device-attach/)
- [About CCA Realms](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-device-attach/1-introduction/)
- [VirtIO for device attach](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-device-attach/2-virtio/)
- [Bounce buffers in Realms](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-device-attach/3.bounce_buffers/)
- [Exercise: observe bounce buffers in a Realm](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-device-attach/4.lab-observe-bounce-buffers/)
- [Next Steps](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-device-attach/_next-steps/)

## About this Learning Path

- **Skill level:** Advanced
- **Reading time:** 1 hr 30 min
- **Last updated:** 01 Sep 2026
- **Author:** [Arnaud de Grandmaison, Arm](https://github.com/Arnaud-de-Grandmaison-ARM)  
  [LinkedIn](https://linkedin.com/in/arnauddegrandmaison)
- **Arm IP:** [Neoverse](https://support.arm.com/?tab=compute-ip&Product%20Type=Infrastructure%20Processors), [Cortex-A](https://support.arm.com/?tab=compute-ip&Product%20Type=Application%20Processors)
- **Tags:** [Performance and Architecture](https://learn.arm.com/tag/performance-and-architecture/), [Linux](https://learn.arm.com/tag/linux), [macOS](https://learn.arm.com/tag/macos), [CCA](https://learn.arm.com/tag/cca), [RME](https://learn.arm.com/tag/rme), [Docker](https://learn.arm.com/tag/docker)

## Who is this for?

This is an advanced topic for developers who want to understand how Arm CCA Realms interact with I/O devices using VirtIO, bounce buffers, and secure device attach mechanisms.

## What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

- Define device attach and distinguish VirtIO paravirtualized attach from secure physical device attach
- Summarize what a Realm is and how RME isolates Realm memory
- Describe how VirtIO enables paravirtualized I/O without full device emulation
- Explain when and why SWIOTLB bounce buffers are used in Realms
- Describe how PCIe‑TDISP and PCIe‑IDE support secure physical device attach and attestation

## Prerequisites

Before starting, you'll need the following prerequisites:

- An AArch64 or x86_64 computer running Linux or macOS. You can also use a cloud instance from one of these [Arm cloud service providers](https://learn.arm.com/learning-paths/servers-and-cloud-computing/csp/).
- Completion of [Get Started with CCA Attestation and Veraison](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-veraison/) Learning Path
- Completion of the [Run an application in a Realm using the Arm Confidential Computing Architecture (CCA)](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-container/) Learning Path
- Completion of the [Run an end-to-end Attestation Flow](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-essentials/) Learning Path

## Summary

You’ll examine how Arm CCA Realms attach to I/O devices through two models: paravirtualized VirtIO and secure physical device attach. First, you’ll learn about Realm isolation with RME, how VirtIO enables mediated device access, and why SWIOTLB bounce buffers are used when devices can’t DMA directly to Realm memory. You’ll also explore how PCIe‑TDISP and PCIe‑IDE provide secure device attach with attestation. Then, you’ll run a pre-built Key Broker demo inside a Realm and use kernel tracing to observe SWIOTLB activity during VirtIO network I/O. By the end, you’ll recognize when data paths rely on bounce buffers and how this relates to the chosen device attach method.
