Date: Sat, 23 Apr 2016 00:40:13 +0300
From: Yury Norov <ynorov@caviumnetworks.com>
To: Catalin Marinas <catalin.marinas@arm.com>
CC: <arnd@arndb.de>, <linux-arm-kernel@lists.infradead.org>,
        <linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
        <linux-s390@vger.kernel.org>, <pinskia@gmail.com>,
        <Prasun.Kapoor@caviumnetworks.com>, <schwab@suse.de>,
        <broonie@kernel.org>, <linux-doc@vger.kernel.org>,
        <heiko.carstens@de.ibm.com>, <agraf@suse.de>, <klimov.linux@gmail.com>,
        <bamvor.zhangjian@huawei.com>, <schwidefsky@de.ibm.com>,
        <Nathan_Lynch@mentor.com>, <joseph@codesourcery.com>,
        <christoph.muellner@theobroma-systems.com>
Subject: Re: [PATCH 19/25] arm64: ptrace: handle ptrace_request differently
 for aarch32 and ilp32
Message-ID: <20160422214013.GA2234@yury-N73SV>
References: <1459894127-17698-1-git-send-email-ynorov@caviumnetworks.com>
 <1459894127-17698-20-git-send-email-ynorov@caviumnetworks.com>
 <20160422171009.GR2998@e104818-lin.cambridge.arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160422171009.GR2998@e104818-lin.cambridge.arm.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Apr 2016 21:40:51.4891 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR07MB609
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 564
Lines: 20

On Fri, Apr 22, 2016 at 06:10:09PM +0100, Catalin Marinas wrote:
> On Wed, Apr 06, 2016 at 01:08:41AM +0300, Yury Norov wrote:
> > Here new aarch32 ptrace syscall handler is introsuced to avoid run-time
> > detection of the task type.
> 
> The reason for this patch isn't clear to me. What's wrong with the
> run-time detection? It's not some performance critical code.
> 
> -- 
> Catalin

Hi Catalin,

It was requested by Arnd, 
It's not 'new' syscall basically,
just an attempt to avoid run-time 
detection of things that may be
detected an compile-time.

Yury.