mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crash_dump: export is_kdump_kernel to modules, consolidate elfcorehdr_addr, setup_elfcorehdr and saved_max_pfn
Date: Thu, 27 Jan 2011 11:57:51 +0100	[thread overview]
Message-ID: <20110127105751.GB31360@aepfle.de> (raw)
In-Reply-To: <20110127024352.GC20334@redhat.com>

On Wed, Jan 26, Vivek Goyal wrote:

> Olaf, 
> 
> I think your HVM guest has booted into kdump kernel after the crash and
> now you want Xen PV driver to reset the connection with Dom0.

Yes, thats the case.

> If that's the case, I think instead of exporting is_kdump_kernel(), better
> make use of symbol "reset_devices". Kexec-tools passes this kernel command
> line option to kdump kernel which tells the kernel that it is booting
> in an unreliable environment and device drivers should reset the
> underlying devices and not rely on BIOS to have put devices in a known
> good state. So if reset_devices=1, then Xen PV driver should reset the
> underlying device hence the connection with Dom0.

I will use this variable, its passed unconditionally from the boot.kdump
script.


> Apart from that, moving the code from arch specific section to generic
> code helps. So that bit you can retain and get rid of export of
> is_kdump_kernel() and elfcorehdr_addr.


Andrew, do you want a new patch with the export of elfcorehdr_addr
removed, or can you edit my patch and remove that one line?

Olaf

  reply	other threads:[~2011-01-27 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 16:10 Olaf Hering
2011-01-26  5:24 ` WANG Cong
2011-01-27  0:04 ` Andrew Morton
2011-01-27 10:47   ` Olaf Hering
2011-01-27 22:49     ` Andrew Morton
2011-01-27  2:43 ` Vivek Goyal
2011-01-27 10:57   ` Olaf Hering [this message]
2011-01-27 22:49     ` Andrew Morton

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=20110127105751.GB31360@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.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 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®