From: Itsuro Oda <oda@valinux.co.jp>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Hariprasad Nellitheertha <hari@in.ibm.com>,
suparna bhattacharya <suparna@in.ibm.com>
Subject: Re: [lkdump-develop] Re: [ANNOUNCE 0/7] Diskdump 1.0 Release
Date: Wed, 01 Dec 2004 14:57:24 +0900 [thread overview]
Message-ID: <20041201141427.3DA7.ODA@valinux.co.jp> (raw)
In-Reply-To: <1101810405.14413.329.camel@wks126533wss.in.ibm.com>
Hi,
On 30 Nov 2004 15:56:45 +0530
Vivek Goyal <vgoyal@in.ibm.com> wrote:
>
> Now kexec based dump is in -mm tree. Could you please have a look at the
> code and point out if any problems you see.
(I looked 2.6.10-rc1-mm3.)
At first crash_machine_kexec() should be called before bust_spinlock(0)
in the panic() function :-)
In disable_IO_APIC() (this is called from crash_dump_stop_cpus())
spin_lock_irqsave(&ioapic_lock, flags) is required. It may be cause
a deadlock. (The other CPU may be stoped with this lock hold.)
It seems no lock required except the point mentioned above from
crash_machine_kexec called to jumping the new kernel. I feel it is
fine.
(BTW. The disconnect_bsp_APIC() in the crash_dump_stop_cpus()
is called twice if both CONFIG_X86_IO_APIC and CONFIG_X86_LOCAL_APIC
are set. The code is beter as follows.
#if defined(CONFIG_X86_IO_APIC)
disable_IO_APIC();
#elif defined(CONFIG_X86_LOCAL_APIC)
disconnect_bsp_APIC();
#endif
)
Thank you.
--
Itsuro ODA <oda@valinux.co.jp>
next prev parent reply other threads:[~2004-12-01 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 0:31 Itsuro Oda
2004-11-30 10:26 ` Vivek Goyal
2004-12-01 5:57 ` Itsuro Oda [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-29 11:19 Arjan van de Ven
2004-11-29 12:34 ` [lkdump-develop] " Takao Indoh
2004-11-29 12:45 ` Arjan van de Ven
2004-11-30 1:15 ` Takao Indoh
2004-11-30 12:35 ` Arjan van de Ven
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=20041201141427.3DA7.ODA@valinux.co.jp \
--to=oda@valinux.co.jp \
--cc=hari@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.com \
--cc=vgoyal@in.ibm.com \
/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
all inboxes | Powered by JetHome®