public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fastboot] [PATCH]IA64 kexec/kdump patch for INIT
Date: Mon, 11 Sep 2006 06:56:54 +0000	[thread overview]
Message-ID: <8808.1157957814@ocs3.ocs.com.au> (raw)
In-Reply-To: <82C6D21B8B7A9Cindou.takao@jp.fujitsu.com>

Takao Indoh (on Thu, 07 Sep 2006 23:48:51 +0900) wrote:
>On Thu, 7 Sep 2006 21:01:17 +0800, "Yu, Luming" wrote:
>
>>>>Did  saved Os gp in SAL OS state  somehow get overridden before 
>>>>ia64_set_kernel_registers prior to invocation of ia64_init_handler?
>>>>
>>>>I assume the following code (in ia64_set_kernel_registers ) 
>>>should restore 
>>>>correct GP value.
>>>>
>>>>ia64_set_kernel_registers:
>>>>	...
>>>>        ;;
>>>>        ld8 r1=[temp4]          // OS GP from SAL OS state
>>>
>>>Yes, but this gp value is physical address.
>>>In the next line, gp is changed to virtual address.
>>>
>>>DATA_PA_TO_VA(r1,temp1)
>>>
>>>This macro just sets region7 bit, so gp value becomes region7 address.
>>
>>Ok, could you please confirm what is the value of r1 before
>>DATA_PA_TO_VA(r1, temp1)?
>>I guess we need to set r1 = __gp in ia64_set_kernel_registers.
>>If not,  this is a bug.  Am I right?
>
>In the ia64_mca_init, the value of ia64_tpa(ia64_getreg(_IA64_REG_GP)
>is registered as gp value. When cpu comes into the above code, r1 is set
>to this value, I think. Therefore, r1 has physical address of __gp
>before DATA_PA_TO_VA(r1, temp1). How do you think?
>
>I think you are right, I also think r1 has to be set to __gp before 
>calling ia64_init_handler.

It already is set in mca_asm.S.  Remember that ia64_init_handler is by
definition part of the kernel, it cannot be a module.  Therefore before
entering ia64_init_handler, r1 must be set to what the kernel expects
to be in r1.  The standard kernel's r1 is a region 7 address, not a
region 5 address.  The kernel (including __gp) is compiled as region 5
but relocated to region 7 during kernel load.

Is the kexec kernel running in region 5?  That may be where the
confusion is coming from.


  parent reply	other threads:[~2006-09-11  6:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07  1:18 [Fastboot] [PATCH]IA64 kexec/kdump patch for INIT Takao Indoh
2006-09-07  1:32 ` Zou, Nanhai
2006-09-07  3:21 ` Takao Indoh
2006-09-07  8:45 ` Zou, Nanhai
2006-09-07  8:48 ` Yu Luming
2006-09-07  9:08 ` Andreas Schwab
2006-09-07  9:17 ` Takao Indoh
2006-09-07 13:01 ` Yu, Luming
2006-09-07 14:48 ` Takao Indoh
2006-09-07 16:38 ` Luck, Tony
2006-09-07 16:44 ` Andreas Schwab
2006-09-07 17:03 ` Luck, Tony
2006-09-08  1:20 ` Zou, Nanhai
2006-09-11  6:12 ` Zou Nan hai
2006-09-11  6:56 ` Keith Owens [this message]
2006-09-11 16:18 ` Luck, Tony
2006-09-13  2:27 ` Takao Indoh
2006-09-13  7:10 ` Keith Owens
2006-09-13  7:58 ` Zou, Nanhai

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=8808.1157957814@ocs3.ocs.com.au \
    --to=kaos@sgi.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