From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Jinyang He <hejinyang@loongson.cn>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Burton <paulburton@kernel.org>,
Jun-Ru Chang <jrjang@realtek.com>
Subject: Re: [PATCH 4/4] MIPS: Add is_jr_ra_ins() to end the loop early
Date: Sat, 23 Oct 2021 20:32:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2110232023171.38243@angie.orcam.me.uk> (raw)
In-Reply-To: <1610454557-25867-5-git-send-email-hejinyang@loongson.cn>
On Tue, 12 Jan 2021, Jinyang He wrote:
> For those leaf functions, they are likely to have no stack operations.
> Add is_jr_ra_ins() to determine whether jr ra has been touched before
> the frame_size is found. Without this patch, the get frame_size operation
> may be out of range and get the frame_size from the next nested function.
>
> Signed-off-by: Jinyang He <hejinyang@loongson.cn>
> ---
> arch/mips/kernel/process.c | 34 +++++++++++++++++++++++++++++++++-
> 1 file changed, 33 insertions(+), 1 deletion(-)
>
> diff --git a/arch/mips/kernel/process.c b/arch/mips/kernel/process.c
> index bef8f8d..9e6f194 100644
> --- a/arch/mips/kernel/process.c
> +++ b/arch/mips/kernel/process.c
> @@ -205,6 +205,36 @@ struct mips_frame_info {
> #define J_TARGET(pc,target) \
> (((unsigned long)(pc) & 0xf0000000) | ((target) << 2))
>
> +static inline int is_jr_ra_ins(union mips_instruction *ip)
> +{
> +#ifdef CONFIG_CPU_MICROMIPS
> + /*
> + * jr16 ra
> + * jr ra
> + */
> + if (mm_insn_16bit(ip->word >> 16)) {
> + if (ip->mm16_r5_format.opcode == mm_pool16c_op &&
> + ip->mm16_r5_format.rt == mm_jr16_op &&
> + ip->mm16_r5_format.imm == 31)
> + return 1;
> + return 0;
> + }
> +
> + if (ip->r_format.opcode == mm_pool32a_op &&
> + ip->r_format.func == mm_pool32axf_op &&
> + ((ip->u_format.uimmediate >> 6) & GENMASK(9,0)) == mm_jalr_op &&
> + ip->r_format.rs == 31)
> + return 1;
> + return 0;
> +#else
Without looking into it much, this is likely missing the point, because
while technically inteed JR and JR16 can be used with $ra in microMIPS
machine code (there's JRS too), in reality either JRC or JRADDIUSP will.
[Wading through e-mail recovered from mid-Jan linux-mips.org crash.]
Maciej
next prev parent reply other threads:[~2021-10-23 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 12:29 [PATCH 0/4] MIPS: process: Some fixes and improvements about get_frame_info() Jinyang He
2021-01-12 12:29 ` [PATCH 1/4] MIPS: process: Reorder header files Jinyang He
2021-01-13 0:27 ` Huacai Chen
2021-01-15 14:46 ` Thomas Bogendoerfer
2021-01-18 10:02 ` Jinyang He
2021-01-18 11:27 ` Jinyang He
2021-01-18 22:11 ` Thomas Bogendoerfer
2021-01-12 12:29 ` [PATCH 2/4] MIPS: microMIPS: Fix the judgment of mm_jr16_op and mm_jalr_op Jinyang He
2021-01-12 12:29 ` [PATCH 3/4] MIPS: Fix get_frame_info() handing of function size Jinyang He
2021-01-12 12:29 ` [PATCH 4/4] MIPS: Add is_jr_ra_ins() to end the loop early Jinyang He
2021-10-23 18:32 ` Maciej W. Rozycki [this message]
2021-10-25 2:11 ` Jinyang He
2021-01-18 1:51 ` [PATCH 0/4] MIPS: process: Some fixes and improvements about get_frame_info() Jiaxun Yang
2021-01-19 1:29 ` Jinyang He
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=alpine.DEB.2.21.2110232023171.38243@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=hejinyang@loongson.cn \
--cc=jrjang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).