All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Matthew Garrett <mjg@redhat.com>,
	linux-kernel@vger.kernel.org, Takao Indoh <tindoh@redhat.com>,
	Randy Dunlap <rdunlap@xenotime.net>, Len Brown <lenb@kernel.org>,
	linux-doc@vger.kernel.org, linux-acpi@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Patch] acpi: introduce "acpi_addr=" parameter for kdump
Date: Tue, 22 Mar 2011 14:31:44 +0800	[thread overview]
Message-ID: <4D884250.3040302@redhat.com> (raw)
In-Reply-To: <20110321155629.GF2694@redhat.com>

于 2011年03月21日 23:56, Vivek Goyal 写道:
>
> Matthew and I were chatting in general about it couple of days back and
> mattew suggested how about if we embrace the idea of booting the kernel
> always in physical mode (both first and second) and keep that extra set
> of pagetables around to make EFI calls. That way kexec/kdump should just
> work and kernel changes also might not be too much.
>
> The potential problem with this is that this might expose various kind
> of BIOS issues with different vendors as vendors might not test the
> physical path.

First I have to say I know a little about EFI.

I am wondering what benefits we will lose if we use physical mode?
comparing it with virtual mode? If very few, this could be a solution.

Thanks.

  reply	other threads:[~2011-03-22  6:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 14:10 [Patch] acpi: introduce "acpi_addr=" parameter for kdump Amerigo Wang
2011-03-10 14:39 ` Vivek Goyal
2011-03-10 15:59   ` Takao Indoh
2011-03-10 17:50   ` Eric W. Biederman
2011-03-10 18:50     ` Matthew Garrett
2011-03-21  6:40       ` Cong Wang
2011-03-21  8:05         ` Eric W. Biederman
2011-03-21 15:56           ` Vivek Goyal
2011-03-22  6:31             ` Cong Wang [this message]
2011-03-10 16:26 ` Randy Dunlap
2011-03-21  6:43   ` Cong Wang
2011-03-21  6:43     ` Cong Wang
2011-03-23  4:28     ` Len Brown
2011-03-23  4:36       ` Eric W. Biederman
2011-03-23 17:40         ` Matthew Garrett

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=4D884250.3040302@redhat.com \
    --to=amwang@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.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=tindoh@redhat.com \
    --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 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.