Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 5 Aug 2002 18:12:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 5 Aug 2002 18:12:36 -0400 Received: from ns.suse.de ([213.95.15.193]:22020 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Mon, 5 Aug 2002 18:12:35 -0400 Date: Tue, 6 Aug 2002 00:16:05 +0200 From: Andi Kleen To: Jamie Lokier Cc: Andi Kleen , Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: context switch vs. signal delivery [was: Re: Accelerating user mode linux] Message-ID: <20020806001605.B18891@wotan.suse.de> References: <20020805163910.C7130@kushida.apsleyroad.org.suse.lists.linux.kernel> <20020805223006.A8773@kushida.apsleyroad.org> <20020805233542.A12753@wotan.suse.de> <20020805230941.A8816@kushida.apsleyroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020805230941.A8816@kushida.apsleyroad.org> User-Agent: Mutt/1.3.22.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 942 Lines: 22 On Mon, Aug 05, 2002 at 11:09:41PM +0100, Jamie Lokier wrote: > Andi Kleen wrote: > > > 2: What happens when the user's signal handler decides it wants to save > > > the FPU state itself (after all) and proceed with some FPU use. Will > > > sigreturn restore the user-saved FPU state? Just curious. > > > > Nope it won't because there is no saved state. The previous context's FPU > > state will be silently corrupted. > > I meant if the user's signal handler decides it wants to save the FPU > state directly into the signal context struct, after deciding to do > that. Won't that work? In theory yes. The space should be already allocated on the stack, it just has to be filled in. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/