[was a private thread due to typo in qemu list address] On 2012-10-05 14:40, Anthony Liguori wrote: > Paolo Bonzini <[email protected]> writes: > >> Il 05/10/2012 00:06, Lucas Meneghel Rodrigues ha scritto: >>> +static void debugexit_ioport_write(void *opaque, uint32_t addr, uint32_t >>> val) >>> +{ >>> + exit((val << 1) | 1); >>> +} >>> + >> >> This "| 1" might be the problem. Anthony, are you relying on it in >> qemu-test and/or can you work out the changes if we use just >> "exit(val)"? > > The reason for ' | 1' was to make sure that the guest couldn't trigger > an exit(0). > > If there's a compelling reason to drop '| 1', I can adjust my tests > accordingly.
assert(val); (or hw_error) exit(val); I would suggest. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux
