All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russ Anderson <rja@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] Fix large MCA bootmem allocation
Date: Tue, 05 Feb 2008 23:54:39 +0000	[thread overview]
Message-ID: <20080205235439.GA10413@sgi.com> (raw)
In-Reply-To: <20080205193232.GA8834@sgi.com>

On Tue, Feb 05, 2008 at 04:24:33PM -0700, Bjorn Helgaas wrote:
> On Tuesday 05 February 2008 04:12:32 pm Russ Anderson wrote:
> > On Tue, Feb 05, 2008 at 01:21:00PM -0700, Bjorn Helgaas wrote:
> > 
> > > What happens if this alloc fails?
> > 
> > The updated patch will panic is alloc fails.
> 
> I don't know this code well, so I apologize for asking basic
> questions.
> 
> Is panic the only choice here?  It seems unfriendly to panic
> just because we can't successfully add a new CPU.  It'd be
> nicer to somehow make the addition fail so the new CPU is
> just not usable.

It wasn't my first choice, but ia64_mca_cpu_init() is void
so it's not as simple as returning a failing status.  That
code was written as part of early boot and if you can't 
get through boot without running out of memory you have
bigger problems.  For example, __alloc_bootmem() calls panic
if it cannot allocate memory.  There is no easy unwind path
out of that code.

Given that ia64_mca_cpu_init() does not get called in
the hot-plug path, the scenario of hot adding a cpu hitting
this panic is not possible.  If/When the hot-plug code starts
calling ia64_mca_cpu_init(), it will be an issue.  

Thanks,
-- 
Russ Anderson, OS RAS/Partitioning Project Lead  
SGI - Silicon Graphics Inc          rja@sgi.com

  parent reply	other threads:[~2008-02-05 23:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 19:32 [patch] Fix large MCA bootmem allocation Russ Anderson
2008-02-05 20:21 ` Bjorn Helgaas
2008-02-05 23:12 ` Russ Anderson
2008-02-05 23:24 ` Bjorn Helgaas
2008-02-05 23:54 ` Luck, Tony
2008-02-05 23:54 ` Russ Anderson [this message]
2008-02-06  0:00 ` Luck, Tony
2008-02-06  0:30 ` Hidetoshi Seto
2008-02-06  1:34 ` Robin Holt
2008-02-06  2:23 ` Hidetoshi Seto
2008-02-06  3:50 ` Hidetoshi Seto
2008-02-06 10:44 ` Robin Holt
2008-02-06 12:39 ` Hidetoshi Seto
2008-02-06 13:22 ` Robin Holt
2008-02-06 15:13 ` Russ Anderson
2008-02-06 23:32 ` Russ Anderson

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=20080205235439.GA10413@sgi.com \
    --to=rja@sgi.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 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.