From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KXilG-0006Go-Qh
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 16:34:02 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KXilG-0006GP-1Z
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 16:34:02 -0400
Received: from [199.232.76.173] (port=52232 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KXilF-0006GL-U5
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 16:34:01 -0400
Received: from rn-out-0910.google.com ([64.233.170.188]:6785)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1KXilF-0007gU-JN
	for qemu-devel@nongnu.org; Mon, 25 Aug 2008 16:34:01 -0400
Received: by rn-out-0910.google.com with SMTP id m61so331006rnd.8
	for <qemu-devel@nongnu.org>; Mon, 25 Aug 2008 13:34:00 -0700 (PDT)
Message-ID: <f43fc5580808251334u2127c88fv18465b4d0ba263be@mail.gmail.com>
Date: Mon, 25 Aug 2008 23:34:00 +0300
From: "Blue Swirl" <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] linux-user exception handling
In-Reply-To: <20080825162105.T45325@stanley.csl.cornell.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080825162105.T45325@stanley.csl.cornell.edu>
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

On 8/25/08, Vince Weaver <vince@csl.cornell.edu> wrote:
> Hello
>
>  so I'm tracking down a problem on sparc32plus-linux-user.
>  SPARC has register windows, and when it tried to save another register
> context, but all available ones are full, it causes a TT_SPILL exception. In
> theory the OS would handle this and move some of the registers to RAM
> somewhere.
>
>  In any case, this doesn't seem to be working properly.  I've traced through
> the code, and I find in cpu-exec.c where userspace exceptions are handled.

No, register window handling and other exceptions are handled in
linux-user/main.c.