From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TRMP1-0007MT-EO for qemu-devel@nongnu.org; Thu, 25 Oct 2012 08:19:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TRMP0-0000tp-69 for qemu-devel@nongnu.org; Thu, 25 Oct 2012 08:19:11 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47184) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TRMOz-0000tY-UD for qemu-devel@nongnu.org; Thu, 25 Oct 2012 08:19:10 -0400 Message-ID: <50892E39.3070408@redhat.com> Date: Thu, 25 Oct 2012 14:19:05 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v1 8/8] usb/ehci: Put RAM in undefined MMIO regions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: vineshp@xilinx.com, edgar.iglesias@gmail.com, john.williams@xilinx.com, qemu-devel@nongnu.org, peter.maydell@linaro.org On 10/25/12 11:47, Peter Crosthwaite wrote: > Just put RAM regions in the unimplemented spaces in the MMIO region. These > regions have undefined behaviour, but this at least stops QEMU from segfaulting > when the guest bangs on these registers (and sucessfully fakes reading and > writing the registers with no side effects). Should not be needed, memory api should deal with that properly. Something is fishy somewhere. Maybe the dmacontext thing Peter Maydell noted for patch 5. cheers, Gerd