qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] subregion collisions


From: Michael S. Tsirkin
Subject: [Qemu-devel] subregion collisions
Date: Sun, 15 Sep 2013 00:31:53 +0300

Enabling the print in memory.c shows quite a lot
of these:
warning: subregion collision fec00000/1000 (ioapic) vs 8000000/f8000000
(pci-hole)
warning: subregion collision fed00000/400 (hpet) vs 8000000/f8000000
(pci-hole)
warning: subregion collision 0/80 (ich9-pm) vs 8/8 (dma-cont)
warning: subregion collision 0/80 (ich9-pm) vs 0/8 (dma-chan)
warning: subregion collision 0/80 (ich9-pm) vs 64/1 (i8042-cmd)
warning: subregion collision 0/80 (ich9-pm) vs 60/1 (i8042-data)
warning: subregion collision 0/80 (ich9-pm) vs 61/1 (elcr)
warning: subregion collision 0/80 (ich9-pm) vs 40/4 (pit)
warning: subregion collision 0/80 (ich9-pm) vs 70/2 (rtc)
warning: subregion collision 0/80 (ich9-pm) vs 20/2 (pic)
warning: subregion collision 0/80 (ich9-pm) vs 7e/2 (kvmvapic)
warning: subregion collision b0000000/10000000 (pcie-mmcfg) vs
8000000/f8000000 (pci-hole)

They likely work fine because the initialization order
happens to give priority to regions which are
registered later.
But we really should fix these, should we not?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]