|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH v1 8/8] usb/ehci: Put RAM in undefined MMIO regions |
Date: | Thu, 25 Oct 2012 15:21:57 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1 |
On 10/25/2012 03:12 PM, Peter Maydell wrote: > (2) what should the memory system do for accesses where there is > no memory region? This is really system specific as it depends > what the bus fabric does. For ARM the usual thing would be to > generate a decode error response which will result in the guest > CPU taking a data abort or prefetch abort. I don't think our > memory system currently has any way of saying "for this access > generate an exception"... > You could easily have the top-level container have ->ops that generate an exception. > (3) I don't think "qemu segfaults" is a good response to bad > guest behaviour so that needs fixing somehow even if we can't > model what the h/w does :-) Right, a stack trace (or a patch) would be appreciated. -- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |