All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jay Lan <jlan@sgi.com>, Bernhard Walle <bwalle@suse.de>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: kdump broken on Altix 350
Date: Thu, 2 Oct 2008 15:13:50 +1000	[thread overview]
Message-ID: <20081002051348.GA1027@verge.net.au> (raw)
In-Reply-To: <200809292342.m8TNgq4u004680@agluck-lia64.sc.intel.com>

On Mon, Sep 29, 2008 at 04:42:52PM -0700, Luck, Tony wrote:
> Does this make kexec/kdump happier?  Bare minimum testing so far
> (builds and boots on tiger ... didn't try kexec yet).

Hi Tony,

your analysis (in your previous email) was more or less the same
conclusion that I had come too, though I was puzzling over
why you had put the reserved area for cpu0 where you had - I assumed
I was misunderstanding things.

This patch looks good to me.

Jay,

With this patch I assume that we still need an order of operations fix for
kexec-tools but no section merging changes. Is that correct?

-- 
Simon Horman
  VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
  H: www.vergenet.net/~horms/             W: www.valinux.co.jp/en


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jay Lan <jlan@sgi.com>, Bernhard Walle <bwalle@suse.de>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: kdump broken on Altix 350
Date: Thu, 02 Oct 2008 05:13:50 +0000	[thread overview]
Message-ID: <20081002051348.GA1027@verge.net.au> (raw)
In-Reply-To: <200809292342.m8TNgq4u004680@agluck-lia64.sc.intel.com>

On Mon, Sep 29, 2008 at 04:42:52PM -0700, Luck, Tony wrote:
> Does this make kexec/kdump happier?  Bare minimum testing so far
> (builds and boots on tiger ... didn't try kexec yet).

Hi Tony,

your analysis (in your previous email) was more or less the same
conclusion that I had come too, though I was puzzling over
why you had put the reserved area for cpu0 where you had - I assumed
I was misunderstanding things.

This patch looks good to me.

Jay,

With this patch I assume that we still need an order of operations fix for
kexec-tools but no section merging changes. Is that correct?

-- 
Simon Horman
  VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
  H: www.vergenet.net/~horms/             W: www.valinux.co.jp/en


  parent reply	other threads:[~2008-10-02  5:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 16:03 kdump broken on Altix 350 Bernhard Walle
2008-08-29 16:03 ` Bernhard Walle
2008-08-29 16:05 ` Bernhard Walle
2008-08-29 16:05   ` Bernhard Walle
2008-08-29 20:42   ` Luck, Tony
2008-08-29 20:42     ` Luck, Tony
2008-08-29 20:48     ` Bernhard Walle
2008-08-29 20:48       ` Bernhard Walle
2008-09-10 11:48     ` Bernhard Walle
2008-09-10 11:48       ` Bernhard Walle
2008-09-10 20:21       ` Jay Lan
2008-09-10 20:21         ` Jay Lan
2008-09-27  1:00         ` Jay Lan
2008-09-27  1:00           ` Jay Lan
2008-09-29 20:55           ` Luck, Tony
2008-09-29 20:55             ` Luck, Tony
2008-09-29 23:42             ` Luck, Tony
2008-09-29 23:42               ` Luck, Tony
2008-09-30  0:30               ` Jay Lan
2008-09-30  0:30                 ` Jay Lan
2008-10-02  5:13               ` Simon Horman [this message]
2008-10-02  5:13                 ` Simon Horman
2008-10-02 17:04                 ` Jay Lan
2008-10-02 17:04                   ` Jay Lan
2008-09-10 12:19 ` Bernhard Walle
2008-09-10 12:19   ` Bernhard Walle

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=20081002051348.GA1027@verge.net.au \
    --to=horms@verge.net.au \
    --cc=bwalle@suse.de \
    --cc=jlan@sgi.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=tony.luck@intel.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 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.