Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: Re: Support /proc/kcore for MIPS
Date: Sun, 13 Feb 2005 21:02:09 -0500	[thread overview]
Message-ID: <20050214020209.GA25335@nevyn.them.org> (raw)
In-Reply-To: <20050121005954.GA10260@nevyn.them.org>

Ping.  I've now tested this patch in both 32-bit and 64-bit kernels.

On Thu, Jan 20, 2005 at 07:59:54PM -0500, Daniel Jacobowitz wrote:
> I wanted to do live debugging on an ornery task_struct this morning, so I
> hooked up /proc/kcore for MIPS.  I'm pretty sure that the CKSEG0 bits are
> wrong, but I did need to cover that region - because the SB-1 kernel links
> at 0xffffffff80100000 or so, disassembly and printing static variables don't
> work unless the debugger can read that region.
> 
> Signed-off-by: Daniel Jacobowitz <dan@codesourcery.com>
> 
> Index: linux/arch/mips/mm/init.c
> ===================================================================
> --- linux.orig/arch/mips/mm/init.c	2005-01-20 16:26:58.791321462 -0500
> +++ linux/arch/mips/mm/init.c	2005-01-20 16:34:27.231213174 -0500
> @@ -24,6 +24,7 @@
>  #include <linux/bootmem.h>
>  #include <linux/highmem.h>
>  #include <linux/swap.h>
> +#include <linux/proc_fs.h>
>  
>  #include <asm/bootinfo.h>
>  #include <asm/cachectl.h>
> @@ -197,6 +198,11 @@
>  	return 0;
>  }
>  
> +static struct kcore_list kcore_mem, kcore_vmalloc;
> +#ifdef CONFIG_MIPS64
> +static struct kcore_list kcore_kseg0;
> +#endif
> +
>  void __init mem_init(void)
>  {
>  	unsigned long codesize, reservedpages, datasize, initsize;
> @@ -247,6 +253,16 @@
>  	datasize =  (unsigned long) &_edata - (unsigned long) &_etext;
>  	initsize =  (unsigned long) &__init_end - (unsigned long) &__init_begin;
>  
> +#ifdef CONFIG_MIPS64
> +	if ((unsigned long) &_text > (unsigned long) CKSEG0)
> +		/* The -4 is a hack so that user tools don't have to handle
> +		   the overflow.  */
> +		kclist_add(&kcore_kseg0, (void *) CKSEG0, 0x80000000 - 4);
> +#endif
> +	kclist_add(&kcore_mem, __va(0), max_low_pfn << PAGE_SHIFT);
> +	kclist_add(&kcore_vmalloc, (void *)VMALLOC_START,
> +		   VMALLOC_END-VMALLOC_START);
> +
>  	printk(KERN_INFO "Memory: %luk/%luk available (%ldk kernel code, "
>  	       "%ldk reserved, %ldk data, %ldk init, %ldk highmem)\n",
>  	       (unsigned long) nr_free_pages() << (PAGE_SHIFT-10),
> 
> -- 
> Daniel Jacobowitz
> 
> 

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-02-14  2:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21  0:59 Support /proc/kcore for MIPS Daniel Jacobowitz
2005-02-14  2:02 ` Daniel Jacobowitz [this message]
2006-01-16 15:53   ` Martin Michlmayr
2006-02-06 13:42     ` [PATCH] use CONFIG_64BIT for /proc/kcore fix Atsushi Nemoto
2006-02-06 23:24       ` Ralf Baechle

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=20050214020209.GA25335@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox