Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Philipp Rudo <prudo@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org,  omair.javaid@linaro.org,
	 yao.qi@linaro.org,  peter.griffin@linaro.org,
	 arnez@linux.vnet.ibm.com
Subject: Re: [RFC v4 9/9] Add S390 support for linux-kernel target
Date: Mon, 19 Jun 2017 13:20:00 -0000	[thread overview]
Message-ID: <86poe0nmfx.fsf@gmail.com> (raw)
In-Reply-To: <20170612193900.234bc540@ThinkPad> (Philipp Rudo's message of	"Mon, 12 Jun 2017 19:39:00 +0200")

Philipp Rudo <prudo@linux.vnet.ibm.com> writes:

> +/* S390s kernel stack is split up on several memory locations:
> +
> +   - kernel stack (per task)
> +   - async aka. interrupt stack (per cpu)
> +   - panic stack (per cpu)
> +   - restart stack (unique, global)
> +
> +   Each memory location is page aligned and has a size of four consecutive
> +   pages (except the panic stack with only one page).  */
> +
> +enum s390_lk_stack_location
> +{
> +  S390_LK_STACK_INVALID = -1,
> +  S390_LK_STACK_USER,
> +  S390_LK_STACK_KERNEL,
> +  S390_LK_STACK_ASYNC,
> +  S390_LK_STACK_PANIC,
> +  S390_LK_STACK_RESTART
> +};
> +

Did you consider adding different frame unwinders for frames on
different memory locations?  Your patches only adds two, but IMO, we
need more unwinders for different frames,

> +
> +/* Helper macro for s390_lk_get_stack_location to check for stacks which
> +   locations are stored in the lowcore.
> +
> +      _addr	address to be checked for
> +      _lc	address of the corresponding lowcore
> +      _stack	field name of stack in lowcore
> +      _type	type to be returned if _addr is on _stack
> +      _size	size of _stack
> +*/
> +
> +#define s390_lk_check_lowcore_stack(_addr, _lc, _stack, _type, _size)	\
> +  do									\
> +    {									\
> +      CORE_ADDR _##_stack, _##_stack##_top, _##_stack##_bottom;		\
> +      _##_stack = lk_read_addr ((_lc) + LK_OFFSET (lowcore, _stack));	\
> +      _##_stack##_top = S390_LK_ROUNDUP (_##_stack, S390_LK_PAGESIZE);	\
> +      _##_stack##_bottom = _##_stack##_top - (_size);			\
> +      if ((_addr) <= _##_stack##_top && (_addr) >= _##_stack##_bottom)	\
> +	return (_type);							\
> +    }									\
> +  while (0)
> +
> +/* Find and return the stack location of ADDR belonging to TASK.  */
> +
> +static enum s390_lk_stack_location
> +s390_lk_get_stack_location (CORE_ADDR task, CORE_ADDR addr)
> +{
> +  CORE_ADDR lowcore, top, bottom;
> +  unsigned int cpu = lk_task_running (task);
> +
> +
> +  /* Kernel stack.  */
> +  bottom = lk_read_addr (task + LK_OFFSET (task_struct, stack));
> +  top = bottom + S390_LK_STACKSIZE;
> +  if (addr <= top && addr >= bottom)
> +    return S390_LK_STACK_KERNEL;
> +
> +  /* A sleeping task only has the kernel stack.  If a sleeping task reaches
> +     this point ADDR isn't on the stack.  */
> +  if (cpu == LK_CPU_INVAL)
> +    return S390_LK_STACK_INVALID;
> +
> +  lowcore = s390_lk_get_lowcore (cpu);
> +
> +  /* Async aka. interrupt stack.  */
> +  s390_lk_check_lowcore_stack (addr, lowcore, async_stack,
> +			       S390_LK_STACK_ASYNC, S390_LK_ASYNCSIZE);
> +
> +  /* Panic stack.
> +     Note: The panic stack only has a size of one page.  */
> +  s390_lk_check_lowcore_stack (addr, lowcore, panic_stack,
> +			       S390_LK_STACK_PANIC, S390_LK_PAGESIZE);
> +
> +  /* Restart stack.  */
> +  s390_lk_check_lowcore_stack (addr, lowcore, restart_stack,
> +			       S390_LK_STACK_RESTART, S390_LK_ASYNCSIZE);
> +
> +  return S390_LK_STACK_INVALID;
> +}

The unwinders for different frames should be chained in this order.

-- 
Yao (齐尧)


  reply	other threads:[~2017-06-19 13:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 17:08 [RFC v4 0/9] Support for Linux kernel debugging Philipp Rudo
2017-06-12 17:08 ` [RFC v4 2/9] Add libiberty/concat styled concat_path function Philipp Rudo
2017-06-12 17:08 ` [RFC v4 4/9] Add kernel module support for linux-kernel target Philipp Rudo
2017-06-12 17:08 ` [RFC v4 7/9] Add privileged registers for s390x Philipp Rudo
2017-06-19 13:34   ` Yao Qi
2017-06-19 15:46     ` Philipp Rudo
2017-06-12 17:08 ` [RFC v4 1/9] Convert substitute_path_component to C++ Philipp Rudo
2017-06-12 17:08 ` [RFC v4 3/9] Add basic Linux kernel support Philipp Rudo
2017-06-15 15:23   ` Yao Qi
2017-06-16 10:10     ` Philipp Rudo
2017-06-16 11:43       ` Pedro Alves
2017-06-19  7:56         ` Philipp Rudo
2017-06-19  9:52       ` Yao Qi
2017-06-19 13:35         ` Omair Javaid
2017-06-19 15:44         ` Philipp Rudo
2017-06-12 17:08 ` [RFC v4 5/9] Add commands for linux-kernel target Philipp Rudo
2017-06-12 17:08 ` [RFC v4 8/9] Link frame_info to thread_info Philipp Rudo
2017-06-19 13:07   ` Yao Qi
2017-06-19 15:46     ` Philipp Rudo
2017-06-12 17:09 ` [RFC v4 6/9] Separate common s390-tdep.* from s390-linux-tdep.* Philipp Rudo
2017-06-12 17:39 ` [RFC v4 9/9] Add S390 support for linux-kernel target Philipp Rudo
2017-06-19 13:20   ` Yao Qi [this message]
2017-06-19 15:45     ` Philipp Rudo
2017-06-12 21:17 ` Philipp Rudo

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=86poe0nmfx.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=omair.javaid@linaro.org \
    --cc=peter.griffin@linaro.org \
    --cc=prudo@linux.vnet.ibm.com \
    --cc=yao.qi@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox