aboutsummaryrefslogtreecommitdiff
path: root/linux-user/m68k
diff options
context:
space:
mode:
authorLaurent Vivier <laurent@vivier.eu>2018-05-28 21:48:12 +0200
committerLaurent Vivier <laurent@vivier.eu>2018-06-04 01:30:43 +0200
commitb8e13ba94e39aae79be5724b2a382091e4c91c83 (patch)
treeff97ebfcdd53b3600c12d8b35aad37cb322cedbf /linux-user/m68k
parent871f95c6171d5301d14dbc73997aa8fbd8e9e7ef (diff)
downloadqemu-b8e13ba94e39aae79be5724b2a382091e4c91c83.zip
qemu-b8e13ba94e39aae79be5724b2a382091e4c91c83.tar.gz
qemu-b8e13ba94e39aae79be5724b2a382091e4c91c83.tar.bz2
linux-user: SPARC "rd %tick" can be used by user application
we have the same problem decribed in 7d6b1daedd ("linux-user, ppc: mftbl can be used by user application") for ppc in the case of sparc. When we use an application trying to resolve a name, it hangs in 0x00000000ff5dd40c: rd %tick, %o5 0x00000000ff5dd410: srlx %o5, 0x20, %o4 0x00000000ff5dd414: btst %o5, %g4 0x00000000ff5dd418: be %icc, 0xff5dd40c because %tick is staying at 0. As QEMU_CLOCK_VIRTUAL is not available in linux-user mode, simply use cpu_get_host_ticks() instead. Signed-off-by: Laurent Vivier <laurent@vivier.eu> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Message-Id: <20180528194812.31216-1-laurent@vivier.eu>
Diffstat (limited to 'linux-user/m68k')
0 files changed, 0 insertions, 0 deletions