All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Bernhard Walle <bwalle@suse.de>,
	x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] x86: Find offset for crashkernel reservation automatically
Date: Mon, 14 Jul 2008 10:30:28 -0700	[thread overview]
Message-ID: <m17iboz83v.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <86802c440807141006o98afac8t66b0933d8acd2746@mail.gmail.com> (Yinghai Lu's message of "Mon, 14 Jul 2008 10:06:48 -0700")

"Yinghai Lu" <yhlu.kernel@gmail.com> writes:

> for 64bit, kdump can start from address above 4g with bzImage?

I think the boot protocol was properly updated for that, it was in the
original drafts.  A relocatable kernel with a 64bit entry point.

I do know that the 64bit code is ready to do that.

Eric

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

WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Bernhard Walle" <bwalle@suse.de>,
	"Vivek Goyal" <vgoyal@redhat.com>,
	kexec@lists.infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Find offset for crashkernel reservation automatically
Date: Mon, 14 Jul 2008 10:30:28 -0700	[thread overview]
Message-ID: <m17iboz83v.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <86802c440807141006o98afac8t66b0933d8acd2746@mail.gmail.com> (Yinghai Lu's message of "Mon, 14 Jul 2008 10:06:48 -0700")

"Yinghai Lu" <yhlu.kernel@gmail.com> writes:

> for 64bit, kdump can start from address above 4g with bzImage?

I think the boot protocol was properly updated for that, it was in the
original drafts.  A relocatable kernel with a 64bit entry point.

I do know that the 64bit code is ready to do that.

Eric

  reply	other threads:[~2008-07-14 17:32 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 19:54 [PATCH] x86: Find offset for crashkernel reservation automatically Bernhard Walle
2008-06-26 19:54 ` Bernhard Walle
2008-06-27 13:32 ` Vivek Goyal
2008-06-27 13:32   ` Vivek Goyal
2008-06-27 13:42   ` Vivek Goyal
2008-06-27 13:42     ` Vivek Goyal
2008-06-27 14:06     ` Bernhard Walle
2008-06-27 14:06       ` Bernhard Walle
2008-06-27 14:19       ` Vivek Goyal
2008-06-27 14:19         ` Vivek Goyal
2008-06-27 14:22         ` Bernhard Walle
2008-06-27 14:22           ` Bernhard Walle
2008-06-27 18:00           ` Eric W. Biederman
2008-06-27 18:00             ` Eric W. Biederman
2008-06-27 18:29             ` Bernhard Walle
2008-06-27 18:29               ` Bernhard Walle
2008-07-03 13:14               ` Ingo Molnar
2008-07-03 13:14                 ` Ingo Molnar
2008-07-14  7:11   ` Yinghai Lu
2008-07-14  7:11     ` Yinghai Lu
2008-07-14  9:24     ` Bernhard Walle
2008-07-14  9:24       ` Bernhard Walle
2008-07-14  9:44       ` Eric W. Biederman
2008-07-14  9:44         ` Eric W. Biederman
2008-07-14 17:06         ` Yinghai Lu
2008-07-14 17:06           ` Yinghai Lu
2008-07-14 17:30           ` Eric W. Biederman [this message]
2008-07-14 17:30             ` Eric W. Biederman
2008-07-14 18:17             ` Yinghai Lu
2008-07-14 18:17               ` Yinghai Lu
2008-07-14 18:41               ` Eric W. Biederman
2008-07-14 18:41                 ` Eric W. Biederman
2008-07-14 18:47                 ` Bernhard Walle
2008-07-14 18:47                   ` Bernhard Walle
2008-07-14 18:55                   ` Eric W. Biederman
2008-07-14 18:55                     ` Eric W. Biederman
2008-07-14 19:08                     ` Yinghai Lu
2008-07-14 19:08                       ` Yinghai Lu

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=m17iboz83v.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.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.