From: Vivek Goyal <vgoyal@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Morton Andrew Morton <akpm@osdl.org>,
Fastboot mailing list <fastboot@lists.osdl.org>,
ak@suse.de
Subject: Re: [PATCH 8/10] kdump: x86_64 save cpu registers upon crash
Date: Sat, 19 Nov 2005 10:05:23 +0530 [thread overview]
Message-ID: <20051119043523.GB3665@in.ibm.com> (raw)
In-Reply-To: <m1mzk1mxni.fsf@ebiederm.dsl.xmission.com>
On Fri, Nov 18, 2005 at 02:52:33PM -0700, Eric W. Biederman wrote:
>
> > diff -puN arch/x86_64/kernel/crash.c~x86_64-save-cpu-registers-upon-crash
> > arch/x86_64/kernel/crash.c
> > ---
> > linux-2.6.15-rc1-1M-dynamic/arch/x86_64/kernel/crash.c~x86_64-save-cpu-registers-upon-crash
>
> > #ifdef CONFIG_SMP
> > static atomic_t waiting_for_crash_ipi;
> >
> > @@ -38,6 +106,7 @@ static int crash_nmi_callback(struct pt_
> > return 1;
> > local_irq_disable();
> >
> > + crash_save_this_cpu(regs, cpu);
> > disable_local_APIC();
> > atomic_dec(&waiting_for_crash_ipi);
> > /* Assume hlt works */
> > @@ -113,4 +182,5 @@ void machine_crash_shutdown(struct pt_re
> > disable_IO_APIC();
> > #endif
> >
> > + crash_save_self(regs);
> > }
>
> Where did this disable_local_APIC and disable_IO_APIC on x86_64 come
> from? I know we had it on x86 but that was supposed to be a stop gap
> until we have the real fix. Now I know it needs a little more
> debugging but the real fix has been written. Putting it there on
> x86_64 makes the code less reliable and it allows things to start
> depending on it.
>
Hi Eric,
Initially we had written the patch without disable_local_APIC and
disable_IO_APIC only. But realized later that fix provided by you to
move apic initialization in init_IRQ has not been merged yet.
Like i386, here also this is a stop gap solution only till your patch is
merged. After that we shall drop this code.
I understand that it is less reliable but at least it provides us a base
to move forward and test kdump on x86_64 and address the other issues.
Thanks
Vivek
next prev parent reply other threads:[~2005-11-19 4:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 13:13 [PATCH 0/10] Kdump Update i386/x86_64 Vivek Goyal
2005-11-17 13:18 ` [PATCH 1/10] kdump: i386 save ss esp bug fix Vivek Goyal
2005-11-17 13:20 ` [PATCH 2/10] kdump: dynamic per cpu allocation of memory for saving cpu registers Vivek Goyal
2005-11-17 13:21 ` [PATCH 3/10] kdump: export per cpu crash notes pointer through sysfs Vivek Goyal
2005-11-17 13:23 ` [PATCH 4/10] kdump: save registers early (inline functions) Vivek Goyal
2005-11-17 13:24 ` [PATCH 5/10] kdump: x86_64 add memmmap command line option Vivek Goyal
2005-11-17 13:25 ` [PATCH 6/10] kdump: x86_64 add elfcorehdr " Vivek Goyal
2005-11-17 13:26 ` [PATCH 7/10] kdump: x86_64 kexec on panic Vivek Goyal
2005-11-17 13:28 ` [PATCH 8/10] kdump: x86_64 save cpu registers upon crash Vivek Goyal
2005-11-17 13:29 ` [PATCH 9/10] kdump: read previous kernel's memory Vivek Goyal
2005-11-17 13:30 ` [PATCH 10/10] kexec: increase max segment limit Vivek Goyal
2005-11-17 22:20 ` [PATCH 9/10] kdump: read previous kernel's memory Andrew Morton
2005-11-17 23:14 ` Eric W. Biederman
2005-11-23 14:04 ` [Fastboot] " Rachita Kothiyal
2005-11-18 0:47 ` [PATCH 8/10] kdump: x86_64 save cpu registers upon crash Haren Myneni
2005-11-18 21:52 ` Eric W. Biederman
2005-11-19 4:35 ` Vivek Goyal [this message]
2005-11-17 22:07 ` [PATCH 3/10] kdump: export per cpu crash notes pointer through sysfs Andrew Morton
2005-11-18 12:33 ` Vivek Goyal
2005-11-17 22:01 ` [PATCH 2/10] kdump: dynamic per cpu allocation of memory for saving cpu registers Andrew Morton
2005-11-18 3:37 ` Vivek Goyal
2005-11-18 12:32 ` Vivek Goyal
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=20051119043523.GB3665@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@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
Powered by JetHome