From: Anju T Sudhakar <anju@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
ananth@in.ibm.com, naveen.n.rao@linux.vnet.ibm.com,
paulus@samba.org, srikar@linux.vnet.ibm.com,
benh@kernel.crashing.org, mpe@ellerman.id.au,
mahesh@linux.vnet.ibm.com
Subject: Re: [PATCH V2 2/4] powerpc: add helper to check if offset is within rel branch range
Date: Fri, 16 Dec 2016 22:01:03 +0530 [thread overview]
Message-ID: <fb24e588-9dc4-4c2c-b8a4-b23c0fb856bc@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161216205221.b6368901a9eea6a8cb7a84ff@kernel.org>
Hi Masami,
Thank you for reviewing the patch set.
On Friday 16 December 2016 05:22 PM, Masami Hiramatsu wrote:
> On Wed, 14 Dec 2016 21:48:30 +0530
> Anju T Sudhakar <anju@linux.vnet.ibm.com> wrote:
>
>> From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
>>
> The coding is OK to me. Please add a description for this patch
> here, e.g. what is done by this patch, what kind of branch
> instruction will be covered, and why thse checks are needed etc.
Sure. I will give a description for this patch.
Thanks and Regards,
-Anju
>
> Thank you,
>
>> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
>> Signed-off-by: Anju T Sudhakar <anju@linux.vnet.ibm.com>
>> ---
>> arch/powerpc/include/asm/code-patching.h | 1 +
>> arch/powerpc/lib/code-patching.c | 24 +++++++++++++++++++++++-
>> 2 files changed, 24 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/include/asm/code-patching.h b/arch/powerpc/include/asm/code-patching.h
>> index 2015b07..75ee4f4 100644
>> --- a/arch/powerpc/include/asm/code-patching.h
>> +++ b/arch/powerpc/include/asm/code-patching.h
>> @@ -22,6 +22,7 @@
>> #define BRANCH_SET_LINK 0x1
>> #define BRANCH_ABSOLUTE 0x2
>>
>> +bool is_offset_in_branch_range(long offset);
>> unsigned int create_branch(const unsigned int *addr,
>> unsigned long target, int flags);
>> unsigned int create_cond_branch(const unsigned int *addr,
>> diff --git a/arch/powerpc/lib/code-patching.c b/arch/powerpc/lib/code-patching.c
>> index d5edbeb..f643451 100644
>> --- a/arch/powerpc/lib/code-patching.c
>> +++ b/arch/powerpc/lib/code-patching.c
>> @@ -32,6 +32,28 @@ int patch_branch(unsigned int *addr, unsigned long target, int flags)
>> return patch_instruction(addr, create_branch(addr, target, flags));
>> }
>>
>> +bool is_offset_in_branch_range(long offset)
>> +{
>> + /*
>> + * Powerpc branch instruction is :
>> + *
>> + * 0 6 30 31
>> + * +---------+----------------+---+---+
>> + * | opcode | LI |AA |LK |
>> + * +---------+----------------+---+---+
>> + * Where AA = 0 and LK = 0
>> + *
>> + * LI is a signed 24 bits integer. The real branch offset is computed
>> + * by: imm32 = SignExtend(LI:'0b00', 32);
>> + *
>> + * So the maximum forward branch should be:
>> + * (0x007fffff << 2) = 0x01fffffc = 0x1fffffc
>> + * The maximum backward branch should be:
>> + * (0xff800000 << 2) = 0xfe000000 = -0x2000000
>> + */
>> + return (offset >= -0x2000000 && offset <= 0x1fffffc && !(offset & 0x3));
>> +}
>> +
>> unsigned int create_branch(const unsigned int *addr,
>> unsigned long target, int flags)
>> {
>> @@ -43,7 +65,7 @@ unsigned int create_branch(const unsigned int *addr,
>> offset = offset - (unsigned long)addr;
>>
>> /* Check we can represent the target in the instruction format */
>> - if (offset < -0x2000000 || offset > 0x1fffffc || offset & 0x3)
>> + if (!is_offset_in_branch_range(offset))
>> return 0;
>>
>> /* Mask out the flags and target, so they don't step on each other. */
>> --
>> 2.7.4
>>
>
next prev parent reply other threads:[~2016-12-16 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 16:18 [PATCH V2 0/4] OPTPROBES for powerpc Anju T Sudhakar
2016-12-14 16:18 ` [PATCH V2 3/4] arch/powerpc: Implement Optprobes Anju T Sudhakar
2016-12-16 14:02 ` Masami Hiramatsu
2016-12-16 17:54 ` Anju T Sudhakar
2016-12-14 16:18 ` [PATCH V2 4/4] arch/powerpc: Optimize kprobe in kretprobe_trampoline Anju T Sudhakar
2016-12-16 14:09 ` Masami Hiramatsu
2016-12-14 16:18 ` [PATCH V2 1/4] powerpc: asm/ppc-opcode.h: introduce __PPC_SH64() Anju T Sudhakar
2016-12-14 16:18 ` [PATCH V2 2/4] powerpc: add helper to check if offset is within rel branch range Anju T Sudhakar
2016-12-16 11:52 ` Masami Hiramatsu
2016-12-16 16:31 ` Anju T Sudhakar [this message]
2016-12-16 14:46 ` [PATCH V2 0/4] OPTPROBES for powerpc Balbir Singh
2016-12-16 17:19 ` Naveen N. Rao
2016-12-16 17:20 ` Anju T Sudhakar
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=fb24e588-9dc4-4c2c-b8a4-b23c0fb856bc@linux.vnet.ibm.com \
--to=anju@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mhiramat@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=srikar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).