d142788172
Should we add a proxy_port that does the v->p address translation? Should the proxy port return a fault on translation errors, if we add one? arch/alpha/alpha_linux_process.cc: Syscalls use a memPort through the CPU now instead of a xc functional memory. cpu/base.hh: Add a pointer to the memPort syscalls will use. Should this be a proxy_port that does address translation? cpu/exec_context.cc: cpu/exec_context.hh: Remove functional memory from the exec context cpu/simple/cpu.cc: Set the memPort to be used as the syscall port as the dcache port sim/syscall_emul.cc: sim/syscall_emul.hh: Syscalls use a memPort through the CPU now instead of a xc functional memory. Also, fix the fact that readStringFunctional doesn't return a fault... should proxy_port handle this because it is doing the translation? --HG-- extra : convert_revision : 1f65318c6594301a75dc4dc0c99fdd436b094a7f |
||
---|---|---|
.. | ||
alpha_linux_process.cc | ||
alpha_linux_process.hh | ||
alpha_memory.cc | ||
alpha_memory.hh | ||
alpha_tru64_process.cc | ||
alpha_tru64_process.hh | ||
aout_machdep.h | ||
arguments.cc | ||
arguments.hh | ||
ecoff_machdep.h | ||
ev5.cc | ||
ev5.hh | ||
faults.cc | ||
faults.hh | ||
isa_desc | ||
isa_traits.hh | ||
osfpal.cc | ||
osfpal.hh | ||
pseudo_inst.cc | ||
pseudo_inst.hh | ||
stacktrace.cc | ||
stacktrace.hh | ||
vptr.hh | ||
vtophys.cc | ||
vtophys.hh |