Skip to content

RFC ioemu: specify the slot for pass-through devices

Simon Horman xen-devel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest4 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4ioemu: Register dpci_infos.php_devs.pt_dev in a common locationhw/pass-through.c+2 -50 replies
2/4lSubject: ioemu: Do slot parsing inside of next_bdfhw/pass-through.c+27 -151 reply
3/4ioemu: make __insert_to_pci_slot indempotenthw/pass-through.c+14 -40 replies
4/4ioemu: allow xend to specify the slot for pass-through deviceshw/pass-through.c hw/pass-through.h+9 -160 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [rfc 0/4] ioemu: specify the slot for pass-through devices

[ I am "reposting" these because yesterday's initial post
never made it off my PC ]

Currently a slot may be specified for a hot-plug device, but not for a pass-through device that is inserted at boot time. This patch adds support for the latter.

The syntax is:

     BUS:DEV.FUNC[@VSLOT]
     e.g: 0000:00:1d:0@7

This may be important as recent changes that allow any free PCI slot to be used for pass-through (and hotplug) may case pass-through devices to be assigned in different locations to before. Amongst other things, specifying the slot will allow users to move them back, if there is a need.

These changes need the patches that I posted today as the series "[patch 0/2] ioemu: Allow any unused PCI device to be used for pass-through"

There is also a xend portion of this patch, which will be posted separately.

Signature · 3 lines
Simon Horman
  VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
  H: www.vergenet.net/~horms/             W: www.valinux.co.jp/en