public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, ebiederm@xmission.com,
	hpa@zytor.com, akpm@linux-foundation.org
Subject: Re: [PATCH 2/2] check if crashk_res_low exists when exclude it from crash mem ranges
Date: Tue, 12 Aug 2014 17:02:53 -0400	[thread overview]
Message-ID: <20140812210253.GH16961@redhat.com> (raw)
In-Reply-To: <1407821368-2358-2-git-send-email-bhe@redhat.com>

On Tue, Aug 12, 2014 at 01:29:28PM +0800, Baoquan He wrote:
> Add a check if crashk_res_low exists just like GART region does. If
> crashk_res_low doesn't exist, calling exclude_mem_range is unnecessary.
> 
> Meanwhile, since crashk_res_low has been initialized at definition, it's
> safe just use "if (crashk_low_res.end)" to check if it's exist. And this
> can make it consistent with other places of check.
> 
> Signed-off-by: Baoquan He <bhe@redhat.com>

This patch looks good.

Acked-by: Vivek Goyal <vgoyal@redhat.com>

Vivek

> ---
>  arch/x86/kernel/crash.c | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c
> index 0553a34..c9e83f9 100644
> --- a/arch/x86/kernel/crash.c
> +++ b/arch/x86/kernel/crash.c
> @@ -238,7 +238,7 @@ static void fill_up_crash_elf_data(struct crash_elf_data *ced,
>  	ced->max_nr_ranges++;
>  
>  	/* If crashk_low_res is not 0, another range split possible */
> -	if (crashk_low_res.end != 0)
> +	if (crashk_low_res.end)
>  		ced->max_nr_ranges++;
>  }
>  
> @@ -336,9 +336,11 @@ static int elf_header_exclude_ranges(struct crash_elf_data *ced,
>  	if (ret)
>  		return ret;
>  
> -	ret = exclude_mem_range(cmem, crashk_low_res.start, crashk_low_res.end);
> -	if (ret)
> -		return ret;
> +	if (crashk_low_res.end) {
> +		ret = exclude_mem_range(cmem, crashk_low_res.start, crashk_low_res.end);
> +		if (ret)
> +			return ret;
> +	}
>  
>  	/* Exclude GART region */
>  	if (ced->gart_end) {
> -- 
> 1.8.5.3

  reply	other threads:[~2014-08-12 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  5:29 [PATCH 1/2] take the segment adding out of locate_mem_hole functions Baoquan He
2014-08-12  5:29 ` [PATCH 2/2] check if crashk_res_low exists when exclude it from crash mem ranges Baoquan He
2014-08-12 21:02   ` Vivek Goyal [this message]
2014-08-12 21:00 ` [PATCH 1/2] take the segment adding out of locate_mem_hole functions Vivek Goyal
2014-08-12 21:53   ` Baoquan He

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=20140812210253.GH16961@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@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