Skip to content

vm-device: Always zero fill the PIO/MMIO data buffer - #8817

Open
rbradford wants to merge 1 commit into
cloud-hypervisor:mainfrom
rbradford:202608/always-fill-pio-read
Open

vm-device: Always zero fill the PIO/MMIO data buffer#8817
rbradford wants to merge 1 commit into
cloud-hypervisor:mainfrom
rbradford:202608/always-fill-pio-read

Conversation

@rbradford

Copy link
Copy Markdown
Member

This aligns with the QEMU, Firecracker and CrosVM behaviour and means
that a PIO read will not see the old data from the kernel's kvm_run
struct.

There was special case hanlding for the ACPI CPU controller so move it
to the common bus implementation.

Signed-off-by: Rob Bradford rbradford@meta.com

@rbradford
rbradford requested a review from a team as a code owner August 28, 2026 14:58
@rbradford
rbradford force-pushed the 202608/always-fill-pio-read branch from d988c4e to bbc0031 Compare August 28, 2026 15:04
@rbradford rbradford changed the title vm-device: Always zero fill the PIO data buffer vm-device: Always zero fill the PIO/MMIO data buffer Aug 28, 2026
@rbradford
rbradford enabled auto-merge August 28, 2026 15:08
Comment thread vm-device/src/bus.rs Outdated
@rbradford
rbradford force-pushed the 202608/always-fill-pio-read branch from bbc0031 to 98da219 Compare August 28, 2026 15:51
This aligns with the QEMU, Firecracker and CrosVM behaviour and means
that a PIO or MMIO read will not see the old data from the kernel's
kvm_run struct.

There was special case hanlding for the ACPI CPU controller so move it
to the common bus implementation.

Signed-off-by: Rob Bradford <rbradford@meta.com>
@rbradford
rbradford force-pushed the 202608/always-fill-pio-read branch from 98da219 to 109040d Compare August 28, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants