mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
	horms@verge.net.au, keir@xen.org, david.vrabel@citrix.com,
	konrad.wilk@oracle.com
Subject: Re: [PATCH 11/14] crashdump/ppc64: Add print_crashkernel_region_size() function
Date: Wed, 9 Dec 2015 10:52:19 +0800	[thread overview]
Message-ID: <20151209025219.GC14426@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <1449611867-15672-12-git-send-email-daniel.kiper@oracle.com>

On 12/08/15 at 10:57pm, Daniel Kiper wrote:
> Provide just print_crashkernel_region_size() stub. This way
> we can properly build kexec utility on ppc64 arch even
> if the functionality is not available on it.

Ditto as ppc, you can read procfs file to get the values..

> 
> Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
> ---
>  kexec/arch/ppc64/crashdump-ppc64.c |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/kexec/arch/ppc64/crashdump-ppc64.c b/kexec/arch/ppc64/crashdump-ppc64.c
> index b3c8928..49af7a6 100644
> --- a/kexec/arch/ppc64/crashdump-ppc64.c
> +++ b/kexec/arch/ppc64/crashdump-ppc64.c
> @@ -527,6 +527,11 @@ int is_crashkernel_mem_reserved(void)
>  	return 1;
>  }
>  
> +void print_crashkernel_region_size(void)
> +{
> +	printf("-1\n");
> +}
> +
>  #if 0
>  static int sort_regions(mem_rgns_t *rgn)
>  {
> -- 
> 1.7.10.4
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 
> 

  reply	other threads:[~2015-12-09  2:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 21:57 [PATCH 00/14] kexec: Add option to get crash kernel region size Daniel Kiper
2015-12-08 21:57 ` [PATCH 01/14] purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe Daniel Kiper
2015-12-08 21:57 ` [PATCH 02/14] kexec: Remove redundant space from help message Daniel Kiper
2015-12-08 21:57 ` [PATCH 03/14] crashdump: Remove stray get_crashkernel_region() declaration Daniel Kiper
2015-12-08 21:57 ` [PATCH 04/14] crashdump/x86: Add print_crashkernel_region_size() function Daniel Kiper
2015-12-08 21:57 ` [PATCH 05/14] crashdump/arm: " Daniel Kiper
2015-12-08 21:57 ` [PATCH 06/14] crashdump/cris: " Daniel Kiper
2015-12-09  2:55   ` Dave Young
2015-12-08 21:57 ` [PATCH 07/14] crashdump/ia64: " Daniel Kiper
2015-12-08 21:57 ` [PATCH 08/14] crashdump/m68k: " Daniel Kiper
2015-12-08 21:57 ` [PATCH 09/14] crashdump/mips: " Daniel Kiper
2015-12-08 21:57 ` [PATCH 10/14] crashdump/ppc: " Daniel Kiper
2015-12-09  2:51   ` Dave Young
2015-12-08 21:57 ` [PATCH 11/14] crashdump/ppc64: " Daniel Kiper
2015-12-09  2:52   ` Dave Young [this message]
2015-12-08 21:57 ` [PATCH 12/14] crashdump/s390: " Daniel Kiper
2015-12-08 21:57 ` [PATCH 13/14] crashdump/sh: " Daniel Kiper
2015-12-08 21:57 ` [PATCH 14/14] kexec: Add option to get crash kernel region size Daniel Kiper

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=20151209025219.GC14426@dhcp-128-65.nay.redhat.com \
    --to=dyoung@redhat.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=horms@verge.net.au \
    --cc=keir@xen.org \
    --cc=kexec@lists.infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®