public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Takao Indoh <indou.takao@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: why ms->pmsa_xip is used?
Date: Tue, 27 Oct 2009 22:21:11 +0000	[thread overview]
Message-ID: <6CA5753CA29E6indou.takao@jp.fujitsu.com> (raw)
In-Reply-To: <F6CA51BB11EE80indou.takao@jp.fujitsu.com>

On Tue, 27 Oct 2009 10:36:53 +1100, Keith Owens wrote:

>On Mon, 26 Oct 2009 18:15:22 -0400, 
>Takao Indoh <indou.takao@jp.fujitsu.com> wrote:
>>As Intel manual says, it seems that pmsa_iip has a value of ip register
>>where INIT interrupted when psr.ic is 0. Ok, I'll make a patch so that
>>pmsa_iip is used irrespective of a value of psr.ic.
>>
>>Please let me know if I need to confirm something else before I make a
>>patch.
>
>That looks good.  The only problem I can think of is an MCA/INIT
>arriving while code like SAVE_MIN or SAVE_REST is executing.  Back
>tracing at that point using pmsa_iip is going to be a problem, you have
>no idea what state the registers or stack are in.

I inserted another debug code into IA64_NATIVE_DO_SAVE_MIN to send
INIT during SAVE_MIN.

diff -Nurp a/arch/ia64/kernel/minstate.h b/arch/ia64/kernel/minstate.h
--- a/arch/ia64/kernel/minstate.h   2009-10-22 12:28:07.000000000 -0400
+++ b/arch/ia64/kernel/minstate.h   2009-10-27 12:42:02.000000000 -0400
@@ -55,6 +55,14 @@
    mov r21=ar.fpsr;        /* M */                         \
    __COVER;                /* B;; (or nothing) */              \
    ;;                                          \
+   movl r24Þbug_flag;    \
+   ;;  \
+   ld8 r23=[r24];  \
+   ;;  \
+   cmp.eq p2,p3=0,r23; \
+(p2) br.sptk 2f;   \
+1:   br.sptk 1b;   \
+2: \
    adds r16=IA64_TASK_THREAD_ON_USTACK_OFFSET,r16;                     \
    ;;                                          \
    ld1 r17=[r16];              /* load current->thread.on_ustack flag */   \

As a result, backtrace in the case using xip works, and backtrace in the
case using iip does NOT work, as you said. Hm, it seems that I have to
reconsider how to fix.

Thanks,
Takao Indoh

  parent reply	other threads:[~2009-10-27 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 19:25 why ms->pmsa_xip is used? Takao Indoh
2009-10-20 23:53 ` Keith Owens
2009-10-26 22:15 ` Takao Indoh
2009-10-26 23:36 ` Keith Owens
2009-10-27 22:21 ` Takao Indoh [this message]
2009-11-05 22:53 ` Takao Indoh
2009-11-05 23:10 ` Keith Owens

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=6CA5753CA29E6indou.takao@jp.fujitsu.com \
    --to=indou.takao@jp.fujitsu.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox