All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jinyang He <hejinyang@loongson.cn>
To: "open list:MIPS" <linux-mips@vger.kernel.org>
Subject: [Question] How to save_stack_trace_tsk_reliable() on mips?
Date: Thu, 4 Feb 2021 20:31:11 +0800	[thread overview]
Message-ID: <a0823990-420f-8091-7866-8ad588ef542d@loongson.cn> (raw)

Hi, all,

Excuse me. Here is a question mail. How to get a reliable stack
of tasks on mips?

First, why save_stack_trace_tsk() to get stack is unreliable? Is it
because the asm code does not obey with gcc's stack rules, or others?

Secondly, can we use some methods to make the task stack reliable? For
example, use the fp register, can this method work? But it seems make
no sense for asm code unless each asm code do some fp work.

I found that the powerpc implemented save_stack_trace_tsk_reliable(),
and the x86 and s390 implemented the arch_stack_walk_reliable(). x86
implemented it through ORC unwind. For powerpc, it may implement it
through its ABI (I guess, I'm not familiar with them). Do we have a
chance to implement it in some way?

Finally, I found that some emails related to ORC unwind on ARM from the
livepatch mail list. It is difficult for me to understand. Is anyone
interested in ORC unwind on MIPS and have researched it?

Any comment is welcome. :-)

Thanks!


             reply	other threads:[~2021-02-04 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 12:31 Jinyang He [this message]
2021-03-01  0:10 ` [Question] How to save_stack_trace_tsk_reliable() on mips? Maciej W. Rozycki
2021-03-01  2:46   ` Jinyang He
2021-03-01 17:17     ` Maciej W. Rozycki

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=a0823990-420f-8091-7866-8ad588ef542d@loongson.cn \
    --to=hejinyang@loongson.cn \
    --cc=linux-mips@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.