diff options
author | Mike Frysinger <vapier@gentoo.org> | 2015-12-26 19:02:07 -0500 |
---|---|---|
committer | Mike Frysinger <vapier@gentoo.org> | 2015-12-26 19:09:43 -0500 |
commit | 466b619e95908dc073b78413f0d0d0b1cb97e4b5 (patch) | |
tree | 2b3a47fc43dab9497495d232fd6769945db63aff /zlib | |
parent | b72dd4c228d71b44e487ff2c53c0d2883653bce7 (diff) | |
download | gdb-466b619e95908dc073b78413f0d0d0b1cb97e4b5.zip gdb-466b619e95908dc073b78413f0d0d0b1cb97e4b5.tar.gz gdb-466b619e95908dc073b78413f0d0d0b1cb97e4b5.tar.bz2 |
sim: bfin: push down mmr address/size checks
The bfin port is using the WITH_DEVICES framework for two reasons:
- get access to the cpu making the request (if available)
- check the alignment & size for core & system MMRs
We addressed the first part with commit dea10706e9159ba6e94eab4c25010f3,
and we handle the second part with this commit. Arguably this is more
correct too because trying to do bad reads/writes directly (when devices
support is disabled) often results in bad memory accesses.
As part of this clean up, we also adjust all of the existing logic that
would reject invalid accesses: the code was relying on the checks never
returning, but that's not the case when things like gdb (via the user's
commands) are making the requests. Thus we'd still end up with bad mem
accesses, or sometimes gdb being hung due to while(1) loops.
Now we can connect (most of) these models into any address and have them
work correctly.
Diffstat (limited to 'zlib')
0 files changed, 0 insertions, 0 deletions