Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Tony Wu <tung7970@gmail.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 2/2] MIPS: get schedule_mfi info from __schedule
Date: Thu, 09 May 2013 19:11:43 +0400	[thread overview]
Message-ID: <518BBCAF.60608@cogentembedded.com> (raw)
In-Reply-To: <20130509144911.GD3562@hades>

Hello.

On 09-05-2013 18:49, Tony Wu wrote:

> schedule_mfi is supposed to be extracted from schedule(), and
> is used in thread_saved_pc and get_wchan.

> But, after optimization, schedule() is reduced to a sibling
> call to __schedule(), and no real frame info can be extracted.

> One solution is to compile schedule() with -fno-omit-frame-pointer
> and -fno-optimize-sibling-calls, but that will incur performance
> degradation.

> This patch follows the sibling call and extracts the
> schedule_mfi from the __schedule with and without KALLSYMS enabled.

> Signed-off-by: Tony Wu <tung7970@gmail.com>
> ---
>   arch/mips/kernel/process.c |   28 ++++++++++++++++++++++++++--
>   1 file changed, 26 insertions(+), 2 deletions(-)

> diff --git a/arch/mips/kernel/process.c b/arch/mips/kernel/process.c
> index a794eb5..289ea69 100644
> --- a/arch/mips/kernel/process.c
> +++ b/arch/mips/kernel/process.c
> @@ -314,15 +314,39 @@ err:
>
>   static struct mips_frame_info schedule_mfi __read_mostly;
>
> +static unsigned long get___schedule_addr(void)
> +{
> +#ifdef CONFIG_KALLSYMS
> +	return kallsyms_lookup_name("__schedule");
> +#else
> +	union mips_instruction *ip = (void *)schedule;
> +	int max_insns = 8;
> +	int i;
> +
> +	for (i = 0; i < max_insns; i++, ip++) {
> +		if (ip->j_format.opcode == j_op)
> +			return J_TARGET(ip, ip->j_format.target);
> +	}
> +	return 0;
> +#endif
> +}
> +

     #ifdef's inside function body are frowned upon. Better code it as:

#ifdef CONFIG_KALLSYMS
static unsigned long get___schedule_addr(void)
{
	return kallsyms_lookup_name("__schedule");
}
#else
static unsigned long get___schedule_addr(void)
{
	union mips_instruction *ip = (void *)schedule;
[...]
	return 0;
}
#endif

WBR, Sergei

      reply	other threads:[~2013-05-09 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 14:49 [PATCH 2/2] MIPS: get schedule_mfi info from __schedule Tony Wu
2013-05-09 15:11 ` Sergei Shtylyov [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=518BBCAF.60608@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tung7970@gmail.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