Re: [PATCH libpciaccess] hurd: Clients or nested arbiters don't touch ioports

2022-08-23 Thread Damien Zammit
Hi, On 23/8/22 10:23 pm, Joan Lledó wrote: > El 23/8/22 a les 10:36, Damien Zammit ha escrit: >> @@ -600,14 +599,14 @@ static const struct pci_system_methods >> hurd_pci_methods = { >> .read = pci_device_hurd_read, >> .write = pci_device_hurd_write, >> .fill_capabilities = pci_f

Re: [PATCH libpciaccess] hurd: Clients or nested arbiters don't touch ioports

2022-08-23 Thread Joan Lledó
Hi, El 23/8/22 a les 10:36, Damien Zammit ha escrit: @@ -600,14 +599,14 @@ static const struct pci_system_methods hurd_pci_methods = { .read = pci_device_hurd_read, .write = pci_device_hurd_write, .fill_capabilities = pci_fill_capabilities_generic, -.open_legacy_io = pci_d

Re: [PATCH] rumpkernel: pci-userspace: Ask for permission to use PCI CONF2 registers

2022-08-23 Thread Samuel Thibault
Damien Zammit, le dim. 21 août 2022 07:00:49 +, a ecrit: > Rationale: QEMU allocates actual io ports in the 0xc000 - 0xcfff > range, therefore we still need to allow rump to access these ports, > in case they are allocated to real pci hardware. Applied, thanks! > --- > debian/patches/machirq

Re: [PATCH] gnumach: Remove PCI_CFG2_* as a reserved ioport range

2022-08-23 Thread Samuel Thibault
Damien Zammit, le mar. 23 août 2022 03:26:49 +, a ecrit: > PCI CONF2 access method was deprecated in PCI v2.0 > > Also, the conf2 ioport range is only activated for use > as pci configuration space when conf1 registers are accessed > in a particular sequence. > > Since the pci-arbiter does no

[PATCH libpciaccess] hurd: Clients or nested arbiters don't touch ioports

2022-08-23 Thread Damien Zammit
I tested this patch and linked it to both pci-arbiter.static and rumpdisk.static, everything still works. I/O ports are not needed at all by nested arbiters/clients of master because we are not reserving them per device. This design may need to change if we want to be more fine-grained over i/o p