Page MenuHomeFreeBSD

Build VirtIO modules on all architectures
ClosedPublic

Authored by jrtc27 on Jan 9 2021, 6:30 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Mar 7, 3:51 PM
Unknown Object (File)
Dec 22 2023, 10:35 PM
Unknown Object (File)
Dec 20 2023, 5:15 PM
Unknown Object (File)
Dec 4 2023, 12:54 AM
Unknown Object (File)
Dec 4 2023, 12:35 AM
Unknown Object (File)
Sep 19 2023, 6:23 PM
Unknown Object (File)
Sep 4 2023, 8:57 AM
Unknown Object (File)
Sep 4 2023, 8:53 AM
Subscribers

Details

Summary

Currently only amd64, i386 and powerpc build VirtIO modules, yet all other
architectures have at least one kernel configuration that includes the
transport drivers, and so they lack drivers for all the devices they don't
statically compile into the kernel. Instead, enable the build everywhere so all
architectures have the full set of device drivers available.

Test Plan

No tinderbox regressions

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 36057
Build 32946: arc lint + arc unit

Event Timeline

jrtc27 requested review of this revision.Jan 9 2021, 6:30 AM

Does this survive universe? mips has no virtualization support at all, last I checked... A quick peek at virtio suggests that it's entirely platform neutral...

In D28058#627077, @imp wrote:

Does this survive universe? mips has no virtualization support at all, last I checked... A quick peek at virtio suggests that it's entirely platform neutral...

Yes, tinderbox succeeded (well, except for LINT kernels due to the HID regression). MIPS supports VirtIO just fine, we use it with QEMU's MALTA machine regularly, with FreeBSD's std.MALTA enabling virtio_pci and common devices.

In that case, I'm good!

This revision is now accepted and ready to land.Jan 9 2021, 8:08 PM

It might be useful to also install virtio man pages on all architectures (in share/man/man4/Makefile) then?

This revision was automatically updated to reflect the committed changes.