On 05/22/2011 06:44 PM, Anthony Liguori wrote:
At any rate, I'm fairly sure it doesn't belong in the MemoryRegion
structure.
Since it isn't a global property, where does it belong?
The chipset should have an intercept in the dispatch path that
enforces this (this assumes hierarchical dispatch).
So instead of region->ops->valid.*, region->ops->intercept()?
btw, that still doesn't require hierarchical dispatch. If intercepts
only check if the access is valid, it can still be flattened.
Hierarchical dispatch means that chipset callbacks get to choose which
subregion callbacks are called, which isn't the case here. If it were,
it would be impossible to figure out the kvm slot layout.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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
