For years now, driver development has been starting earlier in the product life-cycle. Using QEMU for liberating driver developers from being bound to hardware schedules isn't new. Not so common however, is adding support for new hardware to QEMU while the spec is still being revised. The coupling of driver development and emulation development helped find spec issues early, and allowed us to submit patches for a basic driver on the day that the specification wasreleased.
This talk will discuss how we used QEMU to meet our goals, the challenges in enabling CXL 2.0 for QEMU, an review of what CXL is, an overview of the architecture and implementation, and ways in which we'd love to get help.