From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LfOK5-00039s-B2 for qemu-devel@nongnu.org; Thu, 05 Mar 2009 19:53:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LfOK2-00037v-Kn for qemu-devel@nongnu.org; Thu, 05 Mar 2009 19:53:56 -0500 Received: from [199.232.76.173] (port=49275 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LfOK2-00037k-HH for qemu-devel@nongnu.org; Thu, 05 Mar 2009 19:53:54 -0500 Received: from mx20.gnu.org ([199.232.41.8]:6039) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LfOK2-0004sj-6M for qemu-devel@nongnu.org; Thu, 05 Mar 2009 19:53:54 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LfOK0-0001SE-Rc for qemu-devel@nongnu.org; Thu, 05 Mar 2009 19:53:53 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 7/7] PPC64: Don't fault at lwsync Date: Fri, 6 Mar 2009 00:53:46 +0000 References: <1236262454-6293-1-git-send-email-agraf@suse.de> <200903051644.30883.paul@codesourcery.com> <20090305194222.GA3677@caradoc.them.org> In-Reply-To: <20090305194222.GA3677@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903060053.47093.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: blauwirbel@gmail.com, Alexander Graf , Alexander Graf On Thursday 05 March 2009, Daniel Jacobowitz wrote: > On Thu, Mar 05, 2009 at 04:44:30PM +0000, Paul Brook wrote: > > When an MMU exception occurs, qemu figures out the guest location from > > the location of the MMU access in guest code (see cpu_restore_state). My > > guess is that this breaks when two guest instructions have the same > > location. I'm not entirely sure what the correct fix is, or where the bug > > lies > > (cpu_restore_state, gen_intermediate_code_pc, or tcg_gen_code_search_pc) > > but hopefully this will point you in the right direction. > > Automatically pick the second instruction, on the principle that an > instruction with no opcodes is unlikely to trigger a synchronous > fault? Yes, that sounds like the right fix. Paul