From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lci1g-0005KZ-Rx for qemu-devel@nongnu.org; Thu, 26 Feb 2009 10:19:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lci1f-0005Jk-7N for qemu-devel@nongnu.org; Thu, 26 Feb 2009 10:19:52 -0500 Received: from [199.232.76.173] (port=32908 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lci1f-0005Je-1Z for qemu-devel@nongnu.org; Thu, 26 Feb 2009 10:19:51 -0500 Received: from mx20.gnu.org ([199.232.41.8]:25384) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lci1e-0001qx-Nc for qemu-devel@nongnu.org; Thu, 26 Feb 2009 10:19:50 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lci1c-0002ip-QX for qemu-devel@nongnu.org; Thu, 26 Feb 2009 10:19:49 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [5849] Change MMIO callbacks to use offsets, not absolute addresses. Date: Thu, 26 Feb 2009 15:19:42 +0000 References: <200902242228.11210.paul@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902261519.44234.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Blue Swirl > > You either have to explicitly sync state (In teh case of SPARC this > > means saving PC and NPC), or you have to know about the fault in the > > low-level TLB processing code where you still have enough information to > > recover this information. Once you get into an IO handler you've no way > > of figuring out what the current CPU state is. The "not in all > > cases"/"some faults" you mention above is relatively rare instructions > > that may fault v.s. every memory access. > > Well, until r4431 we always saved PC and NPC for all memory access > instructions, but with that commit, some of the checks could be > removed and everything still work. I don't believe that everything still works. Alignemnt checks work because they are enfored by the low-level TLB code. I'm pretty sure unassigned access faults are broken. Paul