From: Andrew Morton <akpm@osdl.org>
To: Gerrit Huizenga <gh@us.ibm.com>
Cc: sharada@in.ibm.com, paulus@samba.org, torvalds@osdl.org,
anton@samba.org, linux-kernel@vger.kernel.org, miltonm@bga.com,
fastboot@lists.osdl.org
Subject: Re: [PATCH] ppc64: kexec support for ppc64
Date: Fri, 6 May 2005 17:32:11 -0700 [thread overview]
Message-ID: <20050506173211.0bc2db7e.akpm@osdl.org> (raw)
In-Reply-To: <E1DUCQS-0005Sq-00@w-gerrit.beaverton.ibm.com>
Gerrit Huizenga <gh@us.ibm.com> wrote:
>
> [ ... ]
>
But you didn't address the question of whether the kexec feature is
sufficiently useful in its own right to justify merging.
>
> If it takes a little list or test matrix of platforms tested over the
> short term to help verify what machines work, we might be able to set
> something like that up as well.
Yes, please do that. But remember that Linux has a distributed test team
of thousands. I have a separate proposal:
My big checkbox for kdump is "can I personally use kdump to diagnose and
solve testers' bug reports?".
If we can reach the stage where a random person downloads a -mm kernel,
hits a bug and, with a reasonable success rate, can send me a kernel core
file which I find useful then yeah, it's proven.
Problem is, I haven't gotten around to moving this idea an inch forward and
am unlikely to do so.
It would really help if some of the kdump developers could assist: make
sure the instructions are easy, that the tools are available, work with
people on the mailing list to get a core file from them, then, using the
core file, work with the relevant maintainer to identify and solve the bug.
We did this a few weeks ago with the -mm timer deadlock. Off-list, I think.
Possible?
next prev parent reply other threads:[~2005-05-07 0:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 6:28 [PATCH] ppc64: global interrupt queue cleanup Paul Mackerras
2005-05-06 12:41 ` [PATCH] ppc64: native hash clear R Sharada
2005-05-06 12:44 ` [PATCH] ppc64: kexec support for ppc64 R Sharada
2005-05-06 23:05 ` Andrew Morton
2005-05-06 23:40 ` Gerrit Huizenga
2005-05-07 0:32 ` Andrew Morton [this message]
2005-05-07 2:02 ` Gerrit Huizenga
2005-05-07 2:36 ` Paul Mackerras
2005-05-07 8:40 ` [Fastboot] " Dipankar Sarma
2005-05-07 16:49 ` Suparna Bhattacharya
2005-05-09 11:55 ` Maneesh Soni
2005-05-09 12:05 ` R Sharada
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=20050506173211.0bc2db7e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=anton@samba.org \
--cc=fastboot@lists.osdl.org \
--cc=gh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@bga.com \
--cc=paulus@samba.org \
--cc=sharada@in.ibm.com \
--cc=torvalds@osdl.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.