[SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
High
|
Manoj Iyer |
Bug Description
[Impact]
uio device binding inside VM would fail with errors
EAL: Detected 3 lcore(s)
EAL: Probing VFIO support...
EAL: PCI device 0000:00:01.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 net_virtio
EAL: Cannot open /sys/bus/
EAL: Cannot open /sys/bus/
EAL: Error - exiting with code: 1
Cause: Requested device 0000:00:01.0 cannot be used
[Fix]
Fixed in linus kernel 4.13 by patch David Woodhouse (4):
PCI: Move multiple declarations of pci_mmap_
PCI: Use BAR index in sysfs attr->private instead of resource pointer
PCI: Add BAR index argument to pci_mmap_
PCI: Add pci_mmap_
[Test]
Please see comment #3 and comment #4 for ARM64 testing on QDF2400 system, and subsequent comments for testing on other arches.
[Regression Potential]
Patch touches PCI subsystem on all architectures, and PCI drivers. Regression tested on ARM64, ppc64el and AMD64.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1712580
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.