From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752650AbaGLSwH (ORCPT ); Sat, 12 Jul 2014 14:52:07 -0400 Received: from one.firstfloor.org ([193.170.194.197]:53862 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752186AbaGLSwE (ORCPT ); Sat, 12 Jul 2014 14:52:04 -0400 Date: Sat, 12 Jul 2014 20:52:02 +0200 From: Andi Kleen To: "H. Peter Anvin" Cc: Andi Kleen , Andy Lutomirski , Linus Torvalds , "linux-kernel@vger.kernel.org" , Al Viro , the arch/x86 maintainers Subject: Re: [PATCH 2/2] x86_64,signal: Remove 'fs' and 'gs' from sigcontext Message-ID: <20140712185202.GX18735@two.firstfloor.org> References: <20140712183748.GW18735@two.firstfloor.org> <0795204d-575c-40b9-b5b0-75ab14eee330@email.android.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0795204d-575c-40b9-b5b0-75ab14eee330@email.android.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 12, 2014 at 11:40:03AM -0700, H. Peter Anvin wrote: > Because you are doing something weird (like Pin, for example) and take an asynchronous fault? But even for pin that would need executing 16 bit code, or really weird 32bit code. AFAIK for 32bit the only good use case was NX emulation (and old virtualization) which are both completely obsolete. I don't think it's worth messing with the signal handlers for 16bit code. If there's any problem with saving/restoring state that emulator can always handle it by itself. -Andi