[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150109174524.GA13161@redhat.com>
Date: Fri, 9 Jan 2015 18:45:24 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Pratyush Anand <panand@...hat.com>
Cc: Will Deacon <will.deacon@....com>,
"tixy@...aro.org" <tixy@...aro.org>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"ananth@...ibm.com" <ananth@...ibm.com>,
"sandeepa.prabhu@...aro.org" <sandeepa.prabhu@...aro.org>,
Catalin Marinas <Catalin.Marinas@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"anil.s.keshavamurthy@...el.com" <anil.s.keshavamurthy@...el.com>,
"masami.hiramatsu.pt@...achi.com" <masami.hiramatsu.pt@...achi.com>,
"wcohen@...hat.com" <wcohen@...hat.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC 8/8] ARM64: Add uprobe support
On 01/08, Pratyush Anand wrote:
>
> On Thursday 08 January 2015 10:33 PM, Will Deacon wrote:
>>
>> I'm assuming that means you don't support compat (AArch32) tasks with this?
>
> Hummm.. Yes, compat not yet supported.
>
> I will come back on this.
I obviously do not know how difficult is to support the compat tasks, and
in any case I leave this to you and Will.
But if this is not simple, perhaps the initial implementation could simply
nack the probe in arch_uprobe_analyze_insn() if this mm is not 64-bit.
Although I do not see something like is_64bit_mm() in arch/arm64... So may be
the first version can even ignore this problem and just document the fact
that AArch32 tasks are not supported.
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists