Date: Mon, 22 May 2017 11:12:43 -0700 From: Krishna Yenduri <kyenduri@brkt.com> To: freebsd-drivers@freebsd.org Subject: ACPI mediated Hotplug? Message-ID: <3DDBEFB3-AB51-4AD2-845D-A8B81ECB417A@brkt.com>
next in thread | raw e-mail | index | archive | help
Hi Folks,
I have a AWS instance (m4.large) running FreeBSD =
11.0-STABLE-amd64-2017-04-20.
The system came up with a primary interface ixv0. Per pciconf -
ixv0@pci0:0:3:0: class=3D0x020000 card=3D0x00000000 =
chip=3D0x10ed8086 rev=3D0x01 hdr=3D0x00
vendor =3D 'Intel Corporation'
device =3D '82599 Ethernet Controller Virtual Function'
class =3D network
subclass =3D ethernet
I attached another network interface while the system is up. But, it =
does
not show up in the pciconf -l output. Doing
# devctl rescan pci0
causes it to appear.
I want to make the interface appear automatically rather
than having to run the devctl command. BTW, this works on Linux.
Is there a way to use the ACPI framework in FreeBSD so
that the Hotplug happens automatically?
DTracing shows that adding a new interface triggers calls to
AcpiEvSciXruptHandler and AcpiEvAsynchExecuteGpeMethod.
Is it safe to add a hook in to pci_rescan_method() from these
routines? Any pointers to the ACPI<->FreeBSD kernel interface
are much appreciated.
Thanks,
-Krishna=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DDBEFB3-AB51-4AD2-845D-A8B81ECB417A>