Home
last modified time | relevance | path

Searched refs:hostaddr (Results 1 – 4 of 4) sorted by relevance

/openbmc/qemu/hw/xen/
H A Dxen_pt.c833 s->hostaddr.bus, s->hostaddr.slot, s->hostaddr.function, in xen_pt_realize()
976 s->hostaddr.bus, s->hostaddr.slot, s->hostaddr.function); in xen_pt_realize()
996 DEFINE_PROP_PCI_HOST_DEVADDR("hostaddr", XenPCIPassthroughState, hostaddr),
1026 s->hostaddr.domain, s->hostaddr.bus, in xen_igd_clear_slot()
1027 s->hostaddr.slot, s->hostaddr.function, in xen_igd_clear_slot()
H A Dxen_pt.h236 PCIHostDeviceAddress hostaddr; member
/openbmc/openbmc/poky/meta/recipes-extended/tcp-wrappers/tcp-wrappers-7.6/
H A D13_shlib_weaksym.patch136 - void (*hostaddr) (); /* address to printable address */
140 + void (*hostaddr) (struct host_info *); /* address to printable address */
222 { (r)->hostname = sock_hostname; (r)->hostaddr = sock_hostaddr; }
/openbmc/qemu/docs/system/devices/
H A Dusb.rst160 ``usb-host,hostbus=bus,hostaddr=addr``
328 ``hostaddr=<nr>``
347 - ``hostbus`` and ``hostaddr`` -- most useful for ad-hoc pass through as the
348 hostaddr isn't stable. The next time you plug the device into the host it
349 will get a new hostaddr.