All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mohan Kumar M <mohan@in.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	kexec <kexec@lists.infradead.org>
Subject: Re: [PATCH] Support for relocatable kdump kernel
Date: Tue, 21 Oct 2008 23:51:48 +0530	[thread overview]
Message-ID: <48FE1DBC.7030202@in.ibm.com> (raw)
In-Reply-To: <1224569019.8228.29.camel@localhost>

Michael Ellerman wrote:

> Does it? I see CONFIG_CRASH_DUMP depending on PPC64, so there is no
> 32-bit kdump possible. Or is someone working on it out-of-tree?
> 

IIUC Anton Vorontsov is working on the 32-bit kdump kernel support.

>> Do you expect a function to do the checking in iommu.c?
> 
> You'd use the function in iommu.c, but it should be defined in some
> header.
> 
Yeah, I will do that.

> OK. Does old purgatory ensure that the register is 0? Otherwise I think
> it's possible that a new kernel could get confused by cruft left in that
> register by an old purgatory - causing the 2nd kernel to think it's a
> kdump kernel when it shouldn't be.

__kdump_flag is by default is 0 and old purgatory code even won't know 
that it need to modify __kdump_flag. So unless __kdump_flag is 1, the 
kernel will behave as a normal one.

Regards,
Mohan.

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

WARNING: multiple messages have this Message-ID (diff)
From: Mohan Kumar M <mohan@in.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	kexec <kexec@lists.infradead.org>
Subject: Re: [PATCH] Support for relocatable kdump kernel
Date: Tue, 21 Oct 2008 23:51:48 +0530	[thread overview]
Message-ID: <48FE1DBC.7030202@in.ibm.com> (raw)
In-Reply-To: <1224569019.8228.29.camel@localhost>

Michael Ellerman wrote:

> Does it? I see CONFIG_CRASH_DUMP depending on PPC64, so there is no
> 32-bit kdump possible. Or is someone working on it out-of-tree?
> 

IIUC Anton Vorontsov is working on the 32-bit kdump kernel support.

>> Do you expect a function to do the checking in iommu.c?
> 
> You'd use the function in iommu.c, but it should be defined in some
> header.
> 
Yeah, I will do that.

> OK. Does old purgatory ensure that the register is 0? Otherwise I think
> it's possible that a new kernel could get confused by cruft left in that
> register by an old purgatory - causing the 2nd kernel to think it's a
> kdump kernel when it shouldn't be.

__kdump_flag is by default is 0 and old purgatory code even won't know 
that it need to modify __kdump_flag. So unless __kdump_flag is 1, the 
kernel will behave as a normal one.

Regards,
Mohan.

  reply	other threads:[~2008-10-21 18:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18684.5062.154465.668614@drongo.ozlabs.ibm.com>
2008-10-20  6:43 ` [PATCH] Support for relocatable kdump kernel Michael Ellerman
2008-10-20  6:43   ` Michael Ellerman
2008-10-20  9:34   ` Mohan Kumar M
2008-10-20  9:34     ` Mohan Kumar M
2008-10-21  6:03     ` Michael Ellerman
2008-10-21  6:03       ` Michael Ellerman
2008-10-21 18:21       ` Mohan Kumar M [this message]
2008-10-21 18:21         ` Mohan Kumar M
2008-10-22  4:56 Milton Miller
  -- strict thread matches above, loose matches on Subject: below --
2008-10-22  3:38 Michael Ellerman
2008-10-12 23:34 Mohan Kumar M
2008-10-12 23:34 ` Mohan Kumar M
2008-10-13  1:30 ` Paul Mackerras
2008-10-13  1:30   ` Paul Mackerras
2008-10-16 10:33   ` Mohan Kumar M
2008-10-16 10:33     ` Mohan Kumar M
2008-10-01 18:26 Mohan Kumar M
2008-10-01 18:26 ` Mohan Kumar M
2008-10-09  5:27 ` Paul Mackerras
2008-10-09  5:27   ` Paul Mackerras
2008-10-09 16:35   ` Mohan Kumar M
2008-10-09 16:35     ` Mohan Kumar M

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=48FE1DBC.7030202@in.ibm.com \
    --to=mohan@in.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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.