All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
	Jan Willeke <willeke@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v5 1/5] vmcore: Introduce ELF header in new memory feature
Date: Fri, 14 Jun 2013 14:54:02 -0400	[thread overview]
Message-ID: <20130614185401.GL12023@redhat.com> (raw)
In-Reply-To: <1370624161-2298-2-git-send-email-holzheu@linux.vnet.ibm.com>

On Fri, Jun 07, 2013 at 06:55:57PM +0200, Michael Holzheu wrote:

[..]
> @@ -935,10 +967,17 @@ static int __init vmcore_init(void)
>  {
>  	int rc = 0;
>  
> -	/* If elfcorehdr= has been passed in cmdline, then capture the dump.*/
> -	if (!(is_vmcore_usable()))
> -		return rc;
> +	/*
> +	 * If elfcorehdr= has not been passed in cmdline, try to get the
> +	 * header from 2nd kernel, then capture the dump.
> +	 */
> +	if (!(is_vmcore_usable())) {
> +		rc = elfcorehdr_alloc();
> +		if (rc)
> +			return rc;
> +	}

Hi Michael,

Patch description says that elfcorehdr_alloc() returns the addr and 
size of elf headers. But that does not seem to be the case here. Has
it been modified in later patches.

Also will it be better if we call elfcorehdr_alloc() always and then
check for is_vmcore_usable().

Something like.

elfcorehdr_addr = elfcorehdr_alloc()
if (elfcorehdr_addr < )
	return elfcorehdr_addr

if (!(is_vmcore_usable()))
	return error

Thanks
Vivek

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	kexec@lists.infradead.org, Jan Willeke <willeke@de.ibm.com>,
	linux-kernel@vger.kernel.org,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH v5 1/5] vmcore: Introduce ELF header in new memory feature
Date: Fri, 14 Jun 2013 14:54:02 -0400	[thread overview]
Message-ID: <20130614185401.GL12023@redhat.com> (raw)
In-Reply-To: <1370624161-2298-2-git-send-email-holzheu@linux.vnet.ibm.com>

On Fri, Jun 07, 2013 at 06:55:57PM +0200, Michael Holzheu wrote:

[..]
> @@ -935,10 +967,17 @@ static int __init vmcore_init(void)
>  {
>  	int rc = 0;
>  
> -	/* If elfcorehdr= has been passed in cmdline, then capture the dump.*/
> -	if (!(is_vmcore_usable()))
> -		return rc;
> +	/*
> +	 * If elfcorehdr= has not been passed in cmdline, try to get the
> +	 * header from 2nd kernel, then capture the dump.
> +	 */
> +	if (!(is_vmcore_usable())) {
> +		rc = elfcorehdr_alloc();
> +		if (rc)
> +			return rc;
> +	}

Hi Michael,

Patch description says that elfcorehdr_alloc() returns the addr and 
size of elf headers. But that does not seem to be the case here. Has
it been modified in later patches.

Also will it be better if we call elfcorehdr_alloc() always and then
check for is_vmcore_usable().

Something like.

elfcorehdr_addr = elfcorehdr_alloc()
if (elfcorehdr_addr < )
	return elfcorehdr_addr

if (!(is_vmcore_usable()))
	return error

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2013-06-14 18:54 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 16:55 [PATCH v5 0/5] kdump: Allow ELF header creation in new kernel Michael Holzheu
2013-06-07 16:55 ` Michael Holzheu
2013-06-07 16:55 ` [PATCH v5 1/5] vmcore: Introduce ELF header in new memory feature Michael Holzheu
2013-06-07 16:55   ` Michael Holzheu
2013-06-10 13:35   ` HATAYAMA Daisuke
2013-06-10 13:35     ` HATAYAMA Daisuke
2013-06-10 13:53     ` Michael Holzheu
2013-06-10 13:53       ` Michael Holzheu
2013-06-14 18:54   ` Vivek Goyal [this message]
2013-06-14 18:54     ` Vivek Goyal
2013-06-21 14:17     ` Michael Holzheu
2013-06-21 14:17       ` Michael Holzheu
2013-06-27 19:32       ` Vivek Goyal
2013-06-27 19:32         ` Vivek Goyal
2013-06-27 20:10         ` Cliff Wickman
2013-06-27 20:10           ` Cliff Wickman
2013-06-27 20:23         ` Vivek Goyal
2013-06-27 20:23           ` Vivek Goyal
2013-06-28  8:15           ` Michael Holzheu
2013-06-28  8:15             ` Michael Holzheu
2013-07-01 17:37             ` Vivek Goyal
2013-07-01 17:37               ` Vivek Goyal
2013-07-01 18:29               ` Michael Holzheu
2013-07-01 18:29                 ` Michael Holzheu
2013-06-07 16:55 ` [PATCH v5 2/5] s390/vmcore: Use " Michael Holzheu
2013-06-07 16:55   ` Michael Holzheu
2013-06-10 13:36   ` HATAYAMA Daisuke
2013-06-10 13:36     ` HATAYAMA Daisuke
2013-06-10 13:48     ` Michael Holzheu
2013-06-10 13:48       ` Michael Holzheu
2013-06-14 19:16   ` Vivek Goyal
2013-06-14 19:16     ` Vivek Goyal
2013-06-07 16:55 ` [PATCH v5 3/5] vmcore: Introduce remap_oldmem_pfn_range() Michael Holzheu
2013-06-07 16:55   ` Michael Holzheu
     [not found]   ` <CAJGZr0+_W0dp2f9VtVAiUT2fqiwe91gHXd9zYzfMMzBZSZogww@mail.gmail.com>
2013-06-10  8:00     ` Michael Holzheu
2013-06-10  8:00       ` Michael Holzheu
2013-06-10 13:40   ` HATAYAMA Daisuke
2013-06-10 13:40     ` HATAYAMA Daisuke
2013-06-10 14:03     ` Michael Holzheu
2013-06-10 14:03       ` Michael Holzheu
2013-06-10 15:37     ` Michael Holzheu
2013-06-10 15:37       ` Michael Holzheu
2013-06-11 12:42       ` HATAYAMA Daisuke
2013-06-11 12:42         ` HATAYAMA Daisuke
2013-06-12  9:13         ` Michael Holzheu
2013-06-12  9:13           ` Michael Holzheu
2013-06-13  1:32           ` HATAYAMA Daisuke
2013-06-13  1:32             ` HATAYAMA Daisuke
2013-06-13  8:54             ` Michael Holzheu
2013-06-13  8:54               ` Michael Holzheu
2013-06-13  4:00           ` HATAYAMA Daisuke
2013-06-13  4:00             ` HATAYAMA Daisuke
2013-06-11 13:20       ` HATAYAMA Daisuke
2013-06-11 13:20         ` HATAYAMA Daisuke
2013-06-07 16:56 ` [PATCH v5 4/5] s390/vmcore: Implement remap_oldmem_pfn_range for s390 Michael Holzheu
2013-06-07 16:56   ` Michael Holzheu
2013-06-14 20:08   ` Vivek Goyal
2013-06-14 20:08     ` Vivek Goyal
2013-06-07 16:56 ` [PATCH v5 5/5] s390/vmcore: Use vmcore for zfcpdump Michael Holzheu
2013-06-07 16:56   ` Michael Holzheu
2013-06-11 23:47   ` HATAYAMA Daisuke
2013-06-11 23:47     ` HATAYAMA Daisuke
2013-06-12  9:14     ` Michael Holzheu
2013-06-12  9:14       ` Michael Holzheu
2013-06-14 18:54 ` [PATCH v5 0/5] kdump: Allow ELF header creation in new kernel Vivek Goyal
2013-06-14 18:54   ` Vivek Goyal
2013-06-21 13:39   ` Michael Holzheu
2013-06-21 13:39     ` Michael Holzheu

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=20130614185401.GL12023@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=willeke@de.ibm.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.