On 06. 11. 25, 11:53, Peter Maydell wrote:
The reason for the commit above is that devices should
not call hw_error() as that crashes QEMU itself.
But that was exactly my intention. Students should see an immediate
crash, not random, undebuggable (in the given class hours) writes
somewhere. And crashing a qemu instance was an intended pun.
Sorry, your educational device doesn't get to break QEMU's
usual rules.
The device is unusual.
(Eventually we might be able to get rid of
hw_error() altogether, though it's hardly a high priority.)
OK, then plan B, don't corrupt.
People debugging drivers can turn on the GUEST_ERROR logging
which should be a big clue.
Hm, so errors are not logged by default? Neither the man page, nor
google yields anything useful on how to enable this. This does not look
very promising.
Incidentally, restricting DMA to "4K starting at 0x40000"
makes the device not usable on all machine types -- there is
no guarantee that the machine even has any RAM there at all.
It's not 0x40000 in the physical space at all.
thanks,
--
js
suse labs
