On Sat, Dec 14, 2019 at 04:28:08PM +0000, Peter Maydell wrote: > (It doesn't actually assert that it doesn't > overlap because we have some legacy uses, notably > in the x86 PC machines, which do overlap without using > the right function, which we've never tried to tidy up.) It's not exactly legacy uses. To be more exact, the way the non overlap versions are *used* is to mean "I don't care what happens when they overlap" as opposed to "will never overlap". There are lots of regions where guest can make things overlapping but doesn't, e.g. PCI BARs can be programmed to overlap almost anything. What happens on real hardware if you then access one of the BARs is undefined, but programming itself is harmless. That's why we can't assert. -- MST
