recent changed in vmm lead to panic: AMD, ivhd_setup_intr

[Oleg Ginzburg]

Both patch ( quick patch and/or https://reviews.freebsd.org/D29521 ) solve
panic:

# kldload vmm
amdiommu0 at device 0.2 on pci0
AMD-Vi: IVRS Info VAsize = 64 PAsize = 48 GVAsize = 2 flags:0
driver bug: Unable to set devclass (class: ppc devname: (unknown))
driver bug: Unable to set devclass (class: ppc devname: (unknown))
ivhd0: <AMD-Vi/IOMMU ivhd with EFR> on acpi0
ivhd0: Flag:b0<IotlbSup,Coherent>
ivhd0: Features(type:0x11) MsiNumPPR = 0 PNBanks= 2 PNCounters= 0
ivhd0: Extended features[31:0]:22294ada<PPRSup,NXSup,GTSup,IASup> HATS =
0x2 GATS = 0x0 GLXSup = 0x1 SmiFSup = 0x1 SmiFRC = 0x2 GAMSup = 0x1
DualPortLogSup = 0x2 DualEventLogSup = 0x2
ivhd0: Extended features[62:32]:4f77ef<USSup> Max PASID: 0x2f DevTblSegSup
= 0x3 MarcSup = 0x1
ivhd0: supported paging level:7, will use only: 4
ivhd0: device range: 0x0 - 0xffff
ivhd0: PCI cap 0x190b640f at 0x40 feature:19<IOTLB,EFR,CapExt>

However, the bhyve process is crashed:

..
fbuf frame buffer base: 0x844600000 [sz 16777216]
pci_xhci no USB devices configured
ld-elf.so.1: /usr/sbin/bhyve: Undefined symbol "vm_munmap_memseg"

On Thu, Apr 1, 2021 at 1:18 AM Ka Ho Ng <khng at freebsd.org> wrote:

> On 4/1/21 5:27 am, Ka Ho Ng wrote:
> > On 4/1/21 4:43 am, Ka Ho Ng wrote:
> >> On 4/1/21 4:41 am, Ka Ho Ng wrote:
> >>> On 4/1/21 4:36 am, Oleg Ginzburg wrote:
> >>>> pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached)
> >>>
> >>> That is the most related cause to the panic. Currently the code
> >>> assumes evaluating a propagated ACPI ivrs table will come with
> >>> attached amd iommu devices as well.
> >>>
> >>> Thanks,
> >>> Ka Ho
> >>
> >> Forgot to mention, /usr/local/bin/acpidump comes from
> >> sysutils/acpica-tools.
> >>
> >> Ka Ho
> >> _______________________________________________
> >> freebsd-virtualization at freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> >> To unsubscribe, send any mail to
> >> "freebsd-virtualization-unsubscribe at freebsd.org"
> >
> > Could you try the attached quick dirty fix and see if it works?
> >
> > Ka Ho
>
> For your reference, here is the differential:
> https://reviews.freebsd.org/D29521
>
> Best,
> Ka Ho
>