bhyve: add PCI IDs of Intel GPUs from Linux v6.15
ClosedPublic
Actions

Authored by corvink on Jun 12 2025, 1:45 PM.

Details

Reviewers

markj
jhb

Group Reviewers

bhyve

Commits

rGfb2b8c307d2e: bhyve: add PCI IDs of Intel GPUs from Linux v6.15

Summary

Linux maintains a list of all known PCI IDs for Intel GPUs. We need this list
in the future because the quirks applied by our GVT-d don't work for the latest
generation of Intels integrated graphcis devices. We have to detect the
generation and then apply some generation specific quirks to it. Fortunately,
Linux has macros for each graphic device type making it easy for us to use that
header to detect the generation of the device in the next step.

Copied from Linux v6.15:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/include/drm/intel/pciids.h?h=v6.15

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Skipped

Unit

Tests Skipped

Build Status

Buildable 64797
Build 61681: arc lint + arc unit

Event Timeline

corvink created this revision.Jun 12 2025, 1:45 PM

Herald added subscribers: bcran, rgrimes, imp. · View Herald TranscriptJun 12 2025, 1:45 PM

corvink requested review of this revision.Jun 12 2025, 1:45 PM

Harbormaster completed remote builds in B64797: Diff 156880.Jun 12 2025, 1:45 PM

corvink added a child revision: D50807: bhyve: scan PCI device ID to properly set BDSM address.Jun 12 2025, 1:47 PM

corvink mentioned this in D45333: x86/pci: add sysctl for intel_graphics_gen.

corvink edited the summary of this revision. (Show Details)Jun 12 2025, 1:51 PM

markj added inline comments.Jun 16 2025, 2:30 PM

usr.sbin/bhyve/pciids_intel_gpus.h
41	These two macros can't be used--can we remove them? There is no `kernel_ulong_t`, for instance. Alternately, if this is supposed to be a pristine copy of the upstream header, some comment at the top of the file with the source would be nice to have.

corvink added inline comments.Jun 17 2025, 6:33 AM

usr.sbin/bhyve/pciids_intel_gpus.h
41	I don't have a strong preference. At the moment, it's a 1:1 copy without any modifications which should make updating this file very easy. I've added the source to the commit message, so a git log will show you the source of the file. However, I can add a comment on top of the file and remove these macros if you like to.