Page MenuHomeFreeBSD

bhyve: allow building device specific ACPI tables
ClosedPublic

Authored by corvink on Mar 29 2023, 1:24 PM.
Tags
None
Referenced Files
F142547951: D39320.id119609.diff
Tue, Jan 20, 9:00 PM
F142545018: D39320.id119609.diff
Tue, Jan 20, 8:24 PM
F142535023: D39320.id119869.diff
Tue, Jan 20, 5:30 PM
F142523463: D39320.id.diff
Tue, Jan 20, 3:09 PM
Unknown Object (File)
Tue, Jan 20, 2:56 PM
Unknown Object (File)
Tue, Jan 20, 2:09 PM
Unknown Object (File)
Tue, Jan 20, 2:34 AM
Unknown Object (File)
Fri, Jan 16, 10:02 AM
Subscribers

Details

Summary

Some ACPI devices require a device specific acpi table. E.g. a TPM2
device requires a TPM2 table. Use the acpi_device_emul struct to define
such a device specific table.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 50765
Build 47656: arc lint + arc unit

Event Timeline

usr.sbin/bhyve/acpi_device.c
143

This can be an assertion.

usr.sbin/bhyve/acpi_device.h
23

The name build_table is quite general, so some comment should explain what this callback is for.

  • add comment to explain the usage of acpi_device_emul.build_table
corvink added inline comments.
usr.sbin/bhyve/acpi_device.c
143

No, it can't. A build_table callback isn't used by all acpi_devices. F.e. qemu_fwcfg has no such callback.

markj added inline comments.
usr.sbin/bhyve/acpi.c
814
This revision is now accepted and ready to land.Apr 11 2023, 2:18 PM
This revision was automatically updated to reflect the committed changes.
corvink marked an inline comment as done.