linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 8/8] ARM64: Add uprobe support
Date: Mon, 12 Jan 2015 10:20:18 +0530	[thread overview]
Message-ID: <54B3528A.6070606@redhat.com> (raw)
In-Reply-To: <20150109174524.GA13161@redhat.com>



On Friday 09 January 2015 11:15 PM, Oleg Nesterov wrote:
> 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.
>

I think most of the stuff can be picked from arch/arm. But I do not have 
a platform to test this feature.So, I will not be taking up as of now.

~Pratyush

  reply	other threads:[~2015-01-12  4:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31 15:21 [RFC 0/8] ARM64: Uprobe support added Pratyush Anand
2015-01-01  1:59 ` Pratyush Anand
     [not found] ` <0694af6935f9c6873ef8d25ad51630a40a74a116.1420038188.git.panand@redhat.com>
2015-01-02 17:23   ` [RFC 8/8] ARM64: Add uprobe support Oleg Nesterov
2015-01-04 13:49     ` Pratyush Anand
2015-01-04 18:40       ` Oleg Nesterov
2015-01-05  4:17         ` Pratyush Anand
2015-01-08 17:03   ` Will Deacon
2015-01-08 17:54     ` Pratyush Anand
2015-01-09 17:45       ` Oleg Nesterov
2015-01-12  4:50         ` Pratyush Anand [this message]
2015-01-09 17:59   ` Oleg Nesterov
2015-01-12  5:04     ` Pratyush Anand
2015-01-12  6:45       ` Pratyush Anand
2015-01-12 14:38         ` Oleg Nesterov
2015-01-12 14:28       ` Oleg Nesterov
     [not found] ` <c40bb09f1edad6899c3855eb56bf4a4f541c49f7.1420038188.git.panand@redhat.com>
2015-01-02 17:43   ` [RFC 3/8] Kernel/uprobe: Define arch_uprobe_exception_notify as __weak Oleg Nesterov
2015-01-04 13:50     ` Pratyush Anand
     [not found] ` <f41f96aaed90007076ce496b9a0746c6f1a01ddb.1420038188.git.panand@redhat.com>
2015-01-02 17:51   ` [RFC 5/8] ARM64: Re-factor flush_ptrace_access Oleg Nesterov
2015-01-02 18:19     ` Oleg Nesterov
2015-01-04 13:50       ` Pratyush Anand
     [not found] ` <1e0a9e778669bb2a2e40bf101eff8ae85110ce54.1420038188.git.panand@redhat.com>
2015-01-02 18:05   ` [RFC 6/8] ARM64: Handle TRAP_HWBRKPT for user mode as well Oleg Nesterov
2015-01-08 17:01     ` Will Deacon
2015-01-08 17:51       ` Pratyush Anand
     [not found] ` <5beb1ff58d4928a873be5e898b62d8cc2003ec7c.1420038188.git.panand@redhat.com>
2015-01-08 16:55   ` [RFC 1/8] ARM64: Move BRK opcodes defines from kprobes.h to insn.h Will Deacon
2015-01-08 17:31     ` Pratyush Anand
     [not found] ` <9a86c217f387f45568c18b724024b0d3e040d2c6.1420038188.git.panand@redhat.com>
2015-01-08 16:55   ` [RFC 2/8] ARM64: Refactor kprobes-arm64 Will Deacon
2015-01-08 17:33     ` Pratyush Anand
2015-01-08 17:36       ` Will Deacon
2015-01-08 17:39         ` Pratyush Anand
     [not found] ` <028aab951a24c56075b1060afa1c2b2d88c09083.1420038188.git.panand@redhat.com>
2015-01-08 16:59   ` [RFC 4/8] ARM64: Add instruction_pointer_set function Will Deacon
2015-01-09  5:18     ` Pratyush Anand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B3528A.6070606@redhat.com \
    --to=panand@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).