public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: Crash Dump Region
Date: Tue, 06 Mar 2007 07:34:51 +0000	[thread overview]
Message-ID: <20070306073450.GA20205@verge.net.au> (raw)
In-Reply-To: <20070306015655.GA27129@verge.net.au>

On Tue, Mar 06, 2007 at 10:32:09AM +0800, Zou Nan hai wrote:
> On Tue, 2007-03-06 at 09:56, Horms wrote:
> > Hi,
> > 
> > I am currently looking over the code that places the crashdump
> > region into /proc/iomem, and the code that determines its base
> > address if it is not passed on the kernel comamnd. It seems to me that
> > the current code allows the crashkernel to be placed incide a
> > /proc/iomem region of any type. Is this behaviour correct?
> > If not, should it be restricted to "System RAM" regions?
> 
> Please review the patch.

This looks good to me.

Acked-by: Simon Horman <horms@verge.net.au>

> Thanks
> Zou Nan hai
> 
> Signed-off-by: Zou Nan hai <nanhai.zou@intel.com>
> 
> --- a/arch/ia64/kernel/efi.c	2007-02-27 00:42:06.000000000 -0500
> +++ b/arch/ia64/kernel/efi.c	2007-03-05 22:09:40.000000000 -0500
> @@ -1154,7 +1154,7 @@ kdump_find_rsvd_region (unsigned long si
>  
>    for (p = efi_map_start; p < efi_map_end; p += efi_desc_size) {
>  	  md = p;
> -	  if (!efi_wb(md))
> +	  if (!is_memory_available(md))
>  		  continue;
>  	  start = ALIGN(md->phys_addr, alignment);
>  	  end = efi_md_end(md);
> 
> 

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


      parent reply	other threads:[~2007-03-06  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06  1:56 Crash Dump Region Horms
2007-03-06  2:10 ` Zou, Nanhai
2007-03-06  2:18 ` Zou, Nanhai
2007-03-06  2:32 ` Zou Nan hai
2007-03-06  2:44 ` Horms
2007-03-06  7:34 ` Horms [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=20070306073450.GA20205@verge.net.au \
    --to=horms@verge.net.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox