Re: Device ID for PCI platform

[Paul Durrant <xadimgnik@xxxxxxxxx>]

On 08/03/2021 16:47, Connor Davis wrote:
> Hi all,
>
> AIS is working on getting modified winpv drivers signed. To this point 
> we've been using device ID 0001 for the platform device, but I think it 
> is best to use a different one so no unwanted collisions occur on 
> windows update. What is the process for new device ID assignment?
Hi Connor,

  You need to send a patch to 
docs/man/xen-pci-device-reservations.7.pod in xen.git, so git send-email 
to xen-devel. In that file you'll see there are PCI device id ranges 
reserved for various purposes. I suspect you'll want to grab c300 - c3ff 
for AIS.
  BTW, in case you don't know, the correct thing to do to expose a 
device with your reserved id to the guest is to add a 'xen-pvdevice' to 
your guest:
root@debian:~# /usr/local/lib/xen/bin/qemu-system-i386 -device 
xen-pvdevice,help
xen-pvdevice options:
  addr=<int32>           - Slot and optional function number, example: 
06.0 or 06 (default: -1)
  device-id=<uint16>     -  (default: 65535)

  Paul


> BTW, the code was recently open sourced for our Windows dom0 research. 
> The drivers are located here[0] in case you want to peek at it.
> Thanks,
> Connor
>
> [0] https://github.com/Bareflank/MicroV/tree/mono/drivers/winpv 
> <https://github.com/Bareflank/MicroV/tree/mono/drivers/winpv>