Il 09/02/2014 15:21, Peter Maydell ha scritto:
Consider a board model which puts together some RAM and devices. It ought to have the same interface for passing this up to the CPU whether it's doing so directly or via some SoC container device. For the SoC container case, this has to be by passing a MemoryRegion, since the SoC will want to add some devices of its own to that region. So the interface for passing things to the CPU should also be a MemoryRegion (which the CPU then turns into an AddressSpace for its own internal use.)
I haven't look closely at those final patches either, but I think I agree with Peter.
It's certainly okay if Andreas picks up these patches, since there's no formal MAINTAINER for the memory API.
However, I'd prefer to first apply the patch to fix exec.c in order to keep bisection as clean as possible.
Thanks! Paolo
