Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 5 Aug 2002 16:08:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 5 Aug 2002 16:08:49 -0400 Received: from mailout03.sul.t-online.com ([194.25.134.81]:49807 "EHLO mailout03.sul.t-online.com") by vger.kernel.org with ESMTP id ; Mon, 5 Aug 2002 16:08:48 -0400 Content-Type: text/plain; charset=US-ASCII From: Oliver Neukum To: Linus Torvalds , Jamie Lokier Subject: Re: context switch vs. signal delivery [was: Re: Accelerating usermode linux] Date: Mon, 5 Aug 2002 22:01:31 +0200 X-Mailer: KMail [version 1.3.1] Cc: linux-kernel@vger.kernel.org References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-ID: <17boD0-1BMTyaC@fmrl08.sul.t-online.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 698 Lines: 17 > Also, people who play games with FP actually change the FP data on the > stack frame, and depend on signal return to reload it. Admittedly I've > only ever seen this on SIGFPE, but anyway - this is all done with integer > instructions that just touch bitpatterns on the stack.. The kernel can't > catch it sanely. Could the fp state be put on its own page and the dirty bit evaluated in the decision whether to restore fpu state ? Regards Oliver - 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/