public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Daniel Kiper <daniel.kiper@oracle.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-kernel@vger.kernel.org, Brandon Philips <brandon@ifup.org>,
	xen-devel@lists.xensource.com,
	virtualization@lists.linux-foundation.org
Subject: Re: is kexec on Xen domU possible?
Date: Mon, 22 Jul 2013 11:36:10 -0700	[thread overview]
Message-ID: <51ED7B9A.1050004@zytor.com> (raw)
In-Reply-To: <20130722183315.GA29273@kroah.com>

On 07/22/2013 11:33 AM, Greg KH wrote:
> 
> I don't care about kdump, I care about kexec on domU for people who are
> running on cloud providers with old versions of Xen so that they can
> control what kernel they can boot, when they want to boot it.  If kdump
> works as well, that's just a bonus, but it's down on the list of things
> for me to be concerned about.
> 

Another valid use case, to be sure.

	-hpa



  reply	other threads:[~2013-07-22 18:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  2:06 is kexec on Xen domU possible? Greg KH
2013-07-19 13:18 ` Daniel Kiper
2013-07-19 13:54   ` Konrad Rzeszutek Wilk
2013-07-19 19:04     ` Olaf Hering
2013-07-19 14:58   ` Brandon Philips
2013-07-19 18:19     ` Daniel Kiper
2013-07-19 15:12   ` Greg KH
2013-07-19 18:32     ` Daniel Kiper
2013-07-19 19:14       ` Greg KH
2013-07-19 20:58         ` H. Peter Anvin
2013-07-22 17:03           ` Daniel Kiper
2013-07-22 17:20             ` Eric W. Biederman
2013-07-22 18:24               ` H. Peter Anvin
2013-07-22 18:33                 ` Greg KH
2013-07-22 18:36                   ` H. Peter Anvin [this message]
2013-07-24  0:22                   ` [Xen-devel] " Matt Wilson
2013-07-24  0:40                     ` Greg KH
2013-07-24  7:49                       ` Eric W. Biederman

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=51ED7B9A.1050004@zytor.com \
    --to=hpa@zytor.com \
    --cc=brandon@ifup.org \
    --cc=daniel.kiper@oracle.com \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.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