From: Pratyush Anand <panand@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: steve.capper@linaro.org, srikar@linux.vnet.ibm.com,
vijaya.kumar@caviumnetworks.com, will.deacon@arm.com,
oleg@redhat.com, linux-kernel@vger.kernel.org, wcohen@redhat.com,
linux-arm-kernel@lists.infradead.org,
David Long <dave.long@linaro.org>
Subject: Re: [PATCH V3 0/6] ARM64: Uprobe support added
Date: Mon, 7 Nov 2016 23:03:44 +0530 [thread overview]
Message-ID: <5cb8b7bc-df6f-8744-b345-4762f2435201@redhat.com> (raw)
In-Reply-To: <20161107113944.GB28876@MBP.local>
On Monday 07 November 2016 05:09 PM, Catalin Marinas wrote:
>> diff --git a/arch/arm64/kernel/probes/decode-insn.c
>> > b/arch/arm64/kernel/probes/decode-insn.c
>> > index 8a29d29..6bf6657 100644
>> > --- a/arch/arm64/kernel/probes/decode-insn.c
>> > +++ b/arch/arm64/kernel/probes/decode-insn.c
>> > @@ -17,7 +17,6 @@
>> > #include <linux/kprobes.h>
>> > #include <linux/module.h>
>> > #include <linux/kallsyms.h>
>> > -#include <asm/kprobes.h>
>> > #include <asm/insn.h>
>> > #include <asm/sections.h>
>> >
>> > So, do you want me to send V4 or a separate topup fixup patch. Please let me
>> > know, will do accordingly.
> Just a separate patch on top of your series would do. Also please test
> your series with CONFIG_KPROBE disabled and I assume this wasn't done
> (just in case there is an interaction we were not aware of).
OK, I tested by disabling CONFIG_KPROBE, and uprobe tests worked fine.
~Pratyush
prev parent reply other threads:[~2016-11-07 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 9:10 Pratyush Anand
2016-11-02 9:10 ` [PATCH V3 1/6] arm64: kprobe: protect/rename few definitions to be reused by uprobe Pratyush Anand
2016-11-02 9:10 ` [PATCH V3 2/6] arm64: kgdb_step_brk_fn: ignore other's exception Pratyush Anand
[not found] ` <CAMNZz5Bjr1f-uzgCx-svFXV_u8xfKudChURVULAqFzu158cxfg@mail.gmail.com>
2016-11-02 10:14 ` Pratyush Anand
2016-11-02 9:10 ` [PATCH V3 3/6] arm64: Handle TRAP_TRACE for user mode as well Pratyush Anand
2016-11-02 9:10 ` [PATCH V3 4/6] arm64: Handle TRAP_BRKPT " Pratyush Anand
2016-11-02 9:10 ` [PATCH V3 5/6] arm64: introduce mm context flag to keep 32 bit task information Pratyush Anand
2016-11-02 9:10 ` [PATCH V3 6/6] arm64: Add uprobe support Pratyush Anand
2016-11-04 17:49 ` [PATCH V3 0/6] ARM64: Uprobe support added Catalin Marinas
2016-11-04 18:46 ` Catalin Marinas
2016-11-05 5:31 ` Pratyush Anand
2016-11-07 11:39 ` Catalin Marinas
2016-11-07 17:33 ` Pratyush Anand [this message]
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=5cb8b7bc-df6f-8744-b345-4762f2435201@redhat.com \
--to=panand@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=steve.capper@linaro.org \
--cc=vijaya.kumar@caviumnetworks.com \
--cc=wcohen@redhat.com \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®