Except it's still a horrible patch that special-cases all the wrong things
(ie random resources that we just happen to know that ACPI etc cares
There's no way to know in general if ACPI might care deeply where some
random resource is (say, graphics memory) and it might be done with a BAR.
So that's why I think the approach stinks.
Well, we should probably just remove the IORESOURCE_BUSY part.
Again, that comes from the fact that the e820 resources used to _override_
everything - they were inserted first, and nothing else was _ever_ allowed
to allocate in that region.
But if we're changing that, then the whole IORESOURCE_BUSY part doesn't
In fact, in general, IORESOURCE_BUSY doesn't much make sense any more in
general, because it was actually more of an ISA-timeframe locking model
saying "you can't touch this region". But if the whole point is that we
now try to allow PCI device BAR's and the e820 maps to co-exist, then the
whole - and only - reason for IORESOURCE_BUSY for them goes away..