[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160422214013.GA2234@yury-N73SV>
Date: Sat, 23 Apr 2016 00:40:13 +0300
From: Yury Norov <ynorov@...iumnetworks.com>
To: Catalin Marinas <catalin.marinas@....com>
CC: <arnd@...db.de>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-arch@...r.kernel.org>,
<linux-s390@...r.kernel.org>, <pinskia@...il.com>,
<Prasun.Kapoor@...iumnetworks.com>, <schwab@...e.de>,
<broonie@...nel.org>, <linux-doc@...r.kernel.org>,
<heiko.carstens@...ibm.com>, <agraf@...e.de>,
<klimov.linux@...il.com>, <bamvor.zhangjian@...wei.com>,
<schwidefsky@...ibm.com>, <Nathan_Lynch@...tor.com>,
<joseph@...esourcery.com>,
<christoph.muellner@...obroma-systems.com>
Subject: Re: [PATCH 19/25] arm64: ptrace: handle ptrace_request differently
for aarch32 and ilp32
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.
Powered by blists - more mailing lists