From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v2 02/16] sparc/compat: Provide an accurate in_compat_syscall implementation Date: Mon, 25 Jan 2016 22:51:00 -0800 (PST) Message-ID: <20160125.225100.1932707129794761764.davem@davemloft.net> References: <20160126062951.GA17107@ravnborg.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20160126062951.GA17107@ravnborg.org> Sender: linux-arch-owner@vger.kernel.org List-Archive: List-Post: To: sam@ravnborg.org Cc: luto@kernel.org, akpm@linux-foundation.org, viro@zeniv.linux.org.uk, torvalds@linux-foundation.org, x86@kernel.org, linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, cmetcalf@ezchip.com, linux-parisc@vger.kernel.org, linux-mips@linux-mips.org, sparclinux@vger.kernel.org List-ID: From: Sam Ravnborg Date: Tue, 26 Jan 2016 07:29:51 +0100 > Could you please add a comment about where 0x110 comes from. > I at least failed to track this down. Frankly I'm fine with this. Someone who understands sparc64 can look at the trap table around entry 0x110 and see: tl0_resv10e: BTRAP(0x10e) BTRAP(0x10f) tl0_linux32: LINUX_32BIT_SYSCALL_TRAP tl0_oldlinux64: LINUX_64BIT_SYSCALL_TRAP