From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Horms <horms@verge.net.au>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Kazuo Moriwaka <moriwaka@valinux.co.jp>,
xen-devel@lists.xensource.com, "Zou,
Nanhai" <nanhai.zou@intel.com>,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
Isaku Yamahata <yamahata@valinux.co.jp>,
Magnus Damm <magnus@valinux.co.jp>,
Mark Williamson <mark.williamson@cl.cam.ac.uk>,
xen-ia64-devel@lists.xensource.com
Subject: Re: Re: [PATCH] kexec: framework and i386 (Take XIV)
Date: Tue, 05 Sep 2006 06:45:35 +0900 [thread overview]
Message-ID: <BDC6D06B746C01takebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <20060901102116.GN17801@verge.net.au>
Hi, Horms
I tested the following patch with Horms kexec patch.
My tests is:
push NMI bottun after loading kdump kernel.
The results is:
OK, I could get vmcore
diff -r b688d4a68a3e xen/arch/x86/traps.c
--- a/xen/arch/x86/traps.c Tue Aug 22 14:59:16 2006 +0100
+++ b/xen/arch/x86/traps.c Tue Sep 05 06:37:49 2006 +0900
@@ -105,6 +105,8 @@ static int debug_stack_lines = 20;
static int debug_stack_lines = 20;
integer_param("debug_stack_lines", debug_stack_lines);
+extern void crash_kexec(struct cpu_user_regs *regs);
+
#ifdef CONFIG_X86_32
#define stack_words_per_line 8
#define ESP_BEFORE_EXCEPTION(regs) ((unsigned long *)®s->esp)
@@ -1611,8 +1613,10 @@ asmlinkage void do_nmi(struct cpu_user_r
mem_parity_error(regs);
else if ( reason & 0x40 )
io_check_error(regs);
- else if ( !nmi_watchdog )
+ else if ( !nmi_watchdog ){
+ crash_kexec(NULL);
unknown_nmi_error((unsigned char)(reason&0xff));
+ }
}
}
Best Regards,
Akio Takebe
>On Fri, Sep 01, 2006 at 05:45:59PM +0900, Akio Takebe wrote:
>> >Hi, Horms
>> >
>> >>That seems like a good idea to me. Though I think you are missing { }.
>> >>Can you test to see if this works?
>> >Oops, You're right. But I think unknown_nmi_error() is not called,
>> >because crash_kexec() is called before that.
>> Sorry.
>> In the only case of CONFIG_KEXEC=y, the above is right.
>
>Yes, I think that is the case. I will put your patch into the kexec
>series, as I think that it is a worthy addition.
>
>--
>Horms
> H: http://www.vergenet.net/~horms/
> W: http://www.valinux.co.jp/en/
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-09-04 21:45 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 7:42 [PATCH]: kexec: framework and i386 Horms
2006-04-07 15:00 ` Don Zickus
2006-04-10 5:09 ` Hirokazu Takahashi
2006-04-10 15:38 ` Don Zickus
2006-04-11 1:44 ` Horms
2006-04-12 15:56 ` Don Zickus
2006-04-07 15:09 ` Gerd Hoffmann
2006-04-08 4:39 ` Horms
2006-04-12 9:12 ` Horms
2006-04-17 6:06 ` Horms
2006-04-21 1:28 ` [PATCH]: kexec: framework and i386 (Take IV) Horms
2006-04-21 6:10 ` Re: [PATCH]: kexec: framework and i386 Akio Takebe
2006-04-21 6:55 ` horms-home
2006-04-21 7:53 ` Akio Takebe
2006-04-23 14:45 ` Mark Williamson
2006-04-24 1:10 ` Akio Takebe
2006-04-24 1:53 ` Hypercall number assignment convension (was Re: Re: [PATCH]: kexec: framework and i386) Isaku Yamahata
2006-04-24 7:32 ` Keir Fraser
2006-04-24 11:20 ` Muli Ben-Yehuda
2006-04-25 0:11 ` Horms
2006-04-25 9:57 ` Keir Fraser
2006-04-26 6:08 ` [PATCH]: kexec: framework and i386 Take V Horms
2006-05-02 8:17 ` [PATCH]: kexec: framework and i386 (Take VI) Simon Horman [Horms]
2006-05-03 7:16 ` Akio Takebe
2006-05-05 1:03 ` horms
2006-05-06 8:46 ` Akio Takebe
2006-05-07 4:46 ` Horms
2006-05-07 9:45 ` Akio Takebe
2006-05-08 9:02 ` Ian Campbell
2006-05-11 11:35 ` horms
2006-05-15 8:29 ` Akio Takebe
2006-05-06 8:44 ` Akio Takebe
2006-05-07 4:45 ` Horms
2006-05-09 4:16 ` [PATCH]: kexec: framework and i386 (Take VII) Horms
2006-05-09 9:18 ` [PATCH]: kexec: framework and i386 (Take VIII) Horms
2006-05-09 13:28 ` Akio Takebe
2006-05-16 10:43 ` Akio Takebe
2006-05-16 10:44 ` Keir Fraser
2006-05-16 11:03 ` Akio Takebe
2006-05-16 12:39 ` Keir Fraser
2006-05-17 2:44 ` Horms
2006-05-17 4:53 ` Horms
2006-05-17 9:52 ` Re: [PATCH]: kexec: framework and i386 (Take IX) Horms
2006-05-17 10:10 ` Keir Fraser
2006-05-18 3:37 ` Horms
2006-05-25 7:20 ` [PATCH] kexec: framework and i386 (Take X) Horms
2006-06-05 2:53 ` Akio Takebe
2006-06-15 7:29 ` [PATCH] kexec: framework and i386 (Take XI) Horms
2006-07-11 3:39 ` [PATCH] kexec: framework and i386 (Take XII) Horms
2006-08-11 7:48 ` [PATCH] kexec: framework and i386 (Take XIII) Horms
2006-08-31 7:43 ` [PATCH] kexec: framework and i386 (Take XIV) Horms
2006-08-31 8:55 ` Akio Takebe
2006-09-01 2:56 ` Horms
2006-09-01 8:41 ` Akio Takebe
2006-09-01 8:45 ` Akio Takebe
2006-09-01 10:21 ` Horms
2006-09-04 21:45 ` Akio Takebe [this message]
2007-05-28 5:28 ` Horms
2007-05-28 6:25 ` [Xen-devel] " Akio Takebe
2007-05-29 1:05 ` Horms
2007-05-29 9:04 ` Ian Campbell
2007-05-31 10:43 ` [Xen-devel] " Akio Takebe
2007-05-31 10:49 ` Keir Fraser
2007-05-31 11:07 ` [Xen-devel] " Akio Takebe
2007-05-31 11:17 ` Akio Takebe
2006-09-05 11:43 ` [Xen-devel] " Kazuo Moriwaka
2006-09-05 13:06 ` Horms
2006-04-26 2:09 ` Hypercall number assignment convension (was Re: Re: [PATCH]: kexec: framework and i386) Isaku Yamahata
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=BDC6D06B746C01takebe_akio@jp.fujitsu.com \
--to=takebe_akio@jp.fujitsu.com \
--cc=horms@verge.net.au \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=magnus@valinux.co.jp \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=moriwaka@valinux.co.jp \
--cc=nanhai.zou@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.