/* NOTE: vmk_PCIGetDeviceName is defined in vmvisor64-vmkernel */

  vmk_PCIGetDeviceName(vmkDev, vmkDevName, sizeof(vmkDevName)-1) != VMK_OK))

{

    vmkDevName[0] = 0;

}

[...]

/* VMKAPI_MODULE_CALL_VOID is a macro calling driver's remove() here */

VMKAPI_MODULE_CALL_VOID(pciDevExt->moduleID,

                        linuxDev->driver->remove,

                        linuxDev);

</pre>        

</p>

<p>The function, <code>vmk_PCIGetDeviceName()</code> must be defined, with an

      implementation, for this code above to work, or even compile.

      Inside <code>BLD/build/HEADERS/vmkapi-current-all-public/vmkernel64/release/device/vmkapi_pci_incompat.h</code>,

      found in the <code>vmkdrivers</code> package of ESXi 5.5U2, shows a

      function header definition for <code>vmk_PCIGetDeviceName()</code>.

      However, the source of its implementation is not provided there or

      anywhere in the source release.</p>

<p>Further evidence that the implementation of this function occurs elsewhere

  can by found by running <code>objdump -x</code> on the un-vmtar'ed

  <code>vmklinux_9</code> module.  Note the following output in the &ldquo;SYMBOL

  TABLE” section:

<pre>

0000000000000000         *UND*  0000000000000000 vmk_PCIGetDeviceName

</pre>

…and the following lines found in the  “RELOCATION RECORDS FOR

[.text]” section:

<pre>

00000000000327ff R_X86_64_PC32     vmk_PCIGetDeviceName+0xfffffffffffffffc

0000000000035318 R_X86_64_PC32     vmk_PCIGetDeviceName+0xfffffffffffffffc

00000000000387e1 R_X86_64_PC32     vmk_PCIGetDeviceName+0xfffffffffffffffc

000000000003cf40 R_X86_64_PC32     vmk_PCIGetDeviceName+0xfffffffffffffffc

</pre>

</p>

<p>The above two properties both suggest that the <code>vmklinux_9</code>

 module requires: (a) a definition of the <code>vmk_PCIGetDeviceName()</code>

 function to operate, but (b) that function is not defined

 inside <code>vmklinux_9</code> itself.</p>

<p>The definition can however be found in binary-only software provided in

  ESXi 5.5U2 &mdash; specifically, inside a file named <code>k.b00</code>,

  which is located in partition 5 on a disk where ESXi has been installed (or

  in the ESXi 5.5U2 installer ISO image).  Running <code>file</code>