From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Takao Indoh <indou.takao@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, amwang@redhat.com,
ebiederm@xmission.com, vgoyal@redhat.com, rdunlap@xenotime.net,
lenb@kernel.org, linux-doc@vger.kernel.org,
linux-acpi@vger.kernel.org, mjg@redhat.com
Subject: Re: [PATCH v2] acpi: introduce "acpi_rsdp=" parameter for kdump
Date: Mon, 11 Jul 2011 13:23:18 -0400 [thread overview]
Message-ID: <20110711172318.GA18279@dumpdata.com> (raw)
In-Reply-To: <E8CC3FDD41FF9Findou.takao@jp.fujitsu.com>
On Mon, Jul 11, 2011 at 11:14:41AM -0400, Takao Indoh wrote:
> Revised version of the patch which was posted by Cong WANG
>
> v1:
> https://lkml.org/lkml/2011/3/10/206
>
> There is a problem with putting the first kernel in EFI virtual mode,
> it is that when the second kernel comes up it tries to initialize the
> EFI again and once we have put EFI in virtual mode we can not really
> do that.
>
> Actually, EFI is not necessary for kdump, we can boot the second kernel
> with "noefi" parameter, but the boot will mostly fail because 2nd kernel
> cannot find RSDP.
>
> In this situation, we introduced "acpi_rsdp=" kernel parameter, so that
> kexec-tools can pass the "noefi acpi_rsdp=X" to the second kernel to make
> kdump works.
>
> Changes in v2:
> * Change parameter name from "acpi_addr" to "acpi_rsdp"
> * Add CONFIG_KEXEC
How will the tools get the physical address of the RSDP?
next prev parent reply other threads:[~2011-07-11 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 15:14 [PATCH v2] acpi: introduce "acpi_rsdp=" parameter for kdump Takao Indoh
2011-07-11 17:23 ` Konrad Rzeszutek Wilk [this message]
2011-07-11 17:27 ` Matthew Garrett
2011-07-12 10:30 ` Cong Wang
2011-07-12 13:31 ` Konrad Rzeszutek Wilk
2011-07-14 22:05 ` Takao Indoh
2011-07-16 22:41 ` Len Brown
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=20110711172318.GA18279@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=amwang@redhat.com \
--cc=ebiederm@xmission.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rdunlap@xenotime.net \
--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