From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LfFAg-0005lt-Bm
	for qemu-devel@nongnu.org; Thu, 05 Mar 2009 10:07:38 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LfFAe-0005lg-NB
	for qemu-devel@nongnu.org; Thu, 05 Mar 2009 10:07:37 -0500
Received: from [199.232.76.173] (port=33793 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LfFAe-0005ld-GZ
	for qemu-devel@nongnu.org; Thu, 05 Mar 2009 10:07:36 -0500
Received: from mx20.gnu.org ([199.232.41.8]:56332)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1LfFAd-00048c-UB
	for qemu-devel@nongnu.org; Thu, 05 Mar 2009 10:07:36 -0500
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1LfFAc-0008Mg-0h
	for qemu-devel@nongnu.org; Thu, 05 Mar 2009 10:07:34 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 7/7] PPC64: Don't fault at lwsync
Date: Thu, 5 Mar 2009 15:07:29 +0000
References: <1236262454-6293-1-git-send-email-agraf@suse.de>
	<1236262454-6293-7-git-send-email-agraf@suse.de>
	<1236262454-6293-8-git-send-email-agraf@suse.de>
In-Reply-To: <1236262454-6293-8-git-send-email-agraf@suse.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200903051507.30592.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com, Alexander Graf <alex@csgraf.de>, Alexander Graf <agraf@suse.de>

On Thursday 05 March 2009, Alexander Graf wrote:
> Right now we can throw a fault on lwsync, even though the fault is
> actually caused by the instruction after lwsync.
>
> I haven't found the magic that messed this up, but for now we can
> just end the TB on lwsync, forcing the next command to issue faults
> itself.
>
> If anyone knows how to really fix this, please step forward and do
> so. This only makes things work at all for me :-).

Where is the subsequent fault coming from? I suspect the real bug is nothing 
to do with lwsync, and the subsequent fault is actually just corrupting the 
CPU state. As discussed recently this is the same bug SPARC has with its 
unassigned access handlers.

Paul