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: [Fastboot] [PATCH]IA64 kexec/kdump patch for INIT
Date: Thu, 07 Sep 2006 03:21:20 +0000	[thread overview]
Message-ID: <83C6D22CB091C5indou.takao@jp.fujitsu.com> (raw)
In-Reply-To: <82C6D21B8B7A9Cindou.takao@jp.fujitsu.com>

On Thu, 7 Sep 2006 09:32:38 +0800, "Zou, Nanhai" wrote:

>> On Thu, 7 Sep 2006 08:57:13 +0800, "Zou, Nanhai" wrote:
>> 
>> >> On Wed, 06 Sep 2006 18:06:53 +0900, Takao Indoh wrote:
>> >>
>> >> >>>+		/* 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
>> >>                                 ~~~~~~~~~~~~~~~~e000000000ace170
>> >> Sorry, I mistook address...
>> >>
>> >>
>> >> Regards,
>> >> Takao Indoh
>> >>
>> >  You don't need to set gp here. Control page does not use GP, and
>> >purgatory code will set GP to a physical address which was pre-calculated
>> >at the time of crash kernel loading.
>> 
>> If gp points region7, panic occurs at kdump_disable_iosapic.
>> 
>> kdump_disable_iosapic(void)
>> {
>> 	u32 low32;
>> 	struct iosapic_intr_info *info;
>> 	struct iosapic_rte_info *rte;
>> 	for (info = iosapic_intr_info; info <
>> 			iosapic_intr_info + IA64_NUM_VECTORS; ++info) {
>> 		low32 = info->low32 |= IOSAPIC_MASK;
>> 		list_for_each_entry(rte, &info->rtes,
>> 				rte_list) {
>> (snip)
>> 
>> The panic occurs at list_for_each_entry. When I found this problem,
>> &info->rtes and rte->rte_list pointed same data but they had different
>> address.
>> 
>> &info->rtes   => 0xe0000000049231e0
>> rte->rte_list => 0xa0000001009231e0
>> 
>> info->rtes points region7 because its address is calculated from gp.
>> This difference of address caused panic.
>> 
>> Regards,
>> Takao Indoh
>>
>
>  Ok, ia64_setreg should be better.
>We should avoid put inline asm code in C file.

Yes, at first I used ia64_setreg, but this problem was not solved.

	if (sos->rv_rc != 1 && (kdump_send_ipi || kdump_on_init)) {
		extern char __gp[];
		local_irq_disable();
		set_curr_task(cpu, previous_current);

		/* change region of gp to region5 */
		ia64_setreg(_IA64_REG_GP, __gp);
		crash_kexec(regs);


The disassemble code:
a000000100047080:       0b 38 01 02 00 24       [MMI]       addl r39=0,r1;;
a000000100047086:       50 02 9c 00 42 00                   mov r37=r39
a00000010004708c:       00 00 04 00                         nop.i 0x0;;
a000000100047090:       0a 08 00 4a 00 21       [MMI]       mov r1=r37;;
a000000100047096:       c0 02 80 00 42 00                   mov r44=r32
a00000010004709c:       00 00 04 00                         nop.i 0x0
a0000001000470a0:       17 00 02 51 02 14       [BBB]       br.call.sptk.many b0 000001000db4a0 <crash_kexec>

This disassembled code does not change content of r1.
Am I missing something?

Regards,
Takao Indoh



  parent reply	other threads:[~2006-09-07  3:21 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 [this message]
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
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=83C6D22CB091C5indou.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