No one can remember where this came from, and it looks very hacky
anyway (we return 0 for config space address 0xfc of _every_ assigned
device, not only vga as the comment claims). So better remove it and
wait for the underlying issue to reappear.
Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
---
hw/device-assignment.c | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/hw/device-assignment.c b/hw/device-assignment.c
index 37c77e3..7db34c4 100644
--- a/hw/device-assignment.c
+++ b/hw/device-assignment.c
@@ -516,10 +516,6 @@ static uint32_t assigned_dev_pci_read_config(PCIDevice *d, uint32_t address,
return val;
}
- /* vga specific, remove later */
- if (address == 0xFC)
- goto do_log;
-
fd = pci_dev->real_device.config_fd;
again:
@@ -534,7 +530,6 @@ again:
exit(1);
}
-do_log:
DEBUG("(%x.%x): address=%04x val=0x%08x len=%d\n",
(d->devfn >> 3) & 0x1F, (d->devfn & 0x7), address, val, len);
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
