mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Itsuro Oda <oda@valinux.co.jp>
Cc: fastboot <fastboot@lists.osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: kdump on non-boot cpu
Date: 03 Feb 2005 12:12:32 +0530	[thread overview]
Message-ID: <1107412952.11609.174.camel@2fwv946.in.ibm.com> (raw)
In-Reply-To: <20050203140438.18E1.ODA@valinux.co.jp>

On Thu, 2005-02-03 at 10:42, Itsuro Oda wrote:
> Hi,
> 
> I found the following in an old mail:
> 
> >From vgoyal at in.ibm.com  Thu Jan  6 07:20:43 2005
> ...
> >2. Kdump can possibly fail on SMP machines if crash occurs on non-boot
> >cpu. Hari is finalizing the stop gap patch to handle this problem.
> 
> Is this finished ?  (It seems it is not in 2.6.11-rc2-mm1.)

Not yet. For the time being focus got shifted to other kdump issues. I
am not even sure if this is a problem. See below a clip from discussions
on fastboot.

> Hi Eric,
> > 
> > I had a quick look at kexec3. Had some queries.
> > 
> > 1. Code for relocating to boot cpu or enabling boot from non-boot cpu is
> > required.
> 
> Actually I just looked and it appears this snippet from smp_boot_cpus
> already handles that case.
> 
>         boot_cpu_physical_apicid = GET_APIC_ID(apic_read(APIC_ID));
>         boot_cpu_logical_apicid = logical_smp_processor_id();
>         x86_cpu_to_apicid[0] = boot_cpu_physical_apicid;
> 
> While looking I certainly did not see anything still in the
> kernel that would complain if we get this wrong.
> 
> Although I  am not really comfortable with a capture kernel using
> multiprocessors. 
> 
> Eric


Do you see a problem in the code flow somewhere?

Vivek


  reply	other threads:[~2005-02-03  5:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  5:12 Itsuro Oda
2005-02-03  6:42 ` Vivek Goyal [this message]
2005-02-03  8:37   ` Itsuro Oda
2005-02-03  9:58     ` [Fastboot] " Eric W. Biederman
2005-02-03 23:43       ` Itsuro Oda
2005-02-04  0:55         ` Eric W. Biederman
2005-02-04  6:02           ` Itsuro Oda
2005-02-07  7:37             ` Eric W. Biederman

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=1107412952.11609.174.camel@2fwv946.in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oda@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 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®