From: Yu Luming <luming.yu@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fastboot] [PATCH]IA64 kexec/kdump patch for INIT
Date: Thu, 07 Sep 2006 08:48:19 +0000 [thread overview]
Message-ID: <200609071648.20275.luming.yu@intel.com> (raw)
In-Reply-To: <82C6D21B8B7A9Cindou.takao@jp.fujitsu.com>
> I agree. I'm also happy if kdb and kdump share the code.
> I'll check kdb code.
>
> >>+ /* change region of gp to region5 */
> >>+ asm volatile ("movl gp=__gp"::: "memory");
> >
> >Why? gp is already pointing at the kernel code before we enter
> >ia64_init_handler().
>
> The purpose of this code is just changing region of gp from region7 to
> region5. For example, if gp is e000000004ace170, I want to change gp to
> a000000104ace170, but I couldn't find good method. Is there good method
> to change region?
>
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
--
Thanks,
Luming
next prev parent reply other threads:[~2006-09-07 8:48 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 [this message]
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
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=200609071648.20275.luming.yu@intel.com \
--to=luming.yu@intel.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