All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
Cc: parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] Crash dump module
Date: Wed, 22 Nov 2000 08:27:22 -0800	[thread overview]
Message-ID: <200011221627.IAA21459@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 22 Nov 2000 15:14:18 PST." <3A1BD4BA.B771D3BE@admin.france.hp.com>

Bruno Vidal wrote:
> 	Hi
> Good news, I've finished to recompile the entire chain on hpux 11.00 64bits.
> I've recompile my own kernel and booted a small 712/60. It work pretty well.
> Now I'm going to start the work about crash dump. So, In my mind, I'll start
> from the linux/kernel/panic.c function and I'll add a function dumpsys.c
> in the linux/arch/paric directory -> is it okay for you ?

YES!

> It will depend on the CONFIG_PARISC var
> (or do you prefer adding a CONFIG_DUMPSYS var ?)

As Randolph pointed out CONFIG_PARISC is deprecated.
Use "ifdef __hppa__" for changes in *common* (ie not arch/parisc)
files. They should not be needed for anything in arch/parisc
or linux/include/asm-parisc.

Adding a CONFIG_DUMPSYS is a good idea.
Look in linux/arch/parisc/config.in, linux/arch/parisc/defconfig, 
and the various Makefiles for how CONFIG_* flags work.

thanks Bruno!
grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

      parent reply	other threads:[~2000-11-22 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 14:14 [parisc-linux] Crash dump module Bruno Vidal
2000-11-22 14:44 ` Randolph Chung
2000-11-22 16:27 ` Grant Grundler [this message]

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=200011221627.IAA21459@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=bruno_vidal@hpfrcu03.france.hp.com \
    --cc=parisc-linux@puffin.external.hp.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.