public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
	Simon Horman <horms@verge.net.au>,
	kexec@lists.infradead.org, xen-devel@lists.xen.org
Subject: Re: [PATCHv7 0/4] kexec-tools: add support for Xen 4.4
Date: Wed, 13 Nov 2013 10:27:53 +0000	[thread overview]
Message-ID: <52835429.8040708@citrix.com> (raw)
In-Reply-To: <1383749722-12091-1-git-send-email-david.vrabel@citrix.com>

On 06/11/13 14:55, David Vrabel wrote:
> The series adds support for the new hypercall ABI which should be
> provided by Xen 4.4.  Images are loaded into Xen directly with no
> kernel involvement.
> 
> Please do not apply until the hypervisor side patches are applied to
> Xen.

The hypervisor patches are now in Xen unstable and will be available in
the upcoming Xen 4.4 release.

Please apply this corresponding kexec-tools series.

When making a new release with these patches in I would recommend adding
a release note saying Xen 4.4 is now required to kexec under Xen.

Thanks.

David

> Patch 1 makes libxc 4.4 mandatory for Xen support.
> 
> Patch 2-3 remove uses of /proc/iomem in favour of libxc.
> 
> Patch 4 adds the support for loading, unloading, and exec'ing an image
> in Xen.
> 
> This series explicitly drops support for older version of libxc/Xen as
> supporting kexec on these hypervisors requires kernel support that
> will never be available upstream.
> 
> Changes in v7:
> - extend extra segment to 0-1 MiB so the VGA memory is accesible by
>   the image.
> 
> Changes in v6:
> - Close libxc handle a few error paths.
> 
> Changes in v5:
> - Dropped the purgatory patch.
> 
> Changes in v4:
> - KEXEC_ARCH_DEFAULT => EM_386
> - add segment in the crash case for the backup src.
> 
> Changes in v3 (not posted):
> - Rebased
> 
> Changes in v2:
> - Patch from Don Sultz: use libxc for vmcoreinfo.
> - Use xc_get_max_cpus() to get number of PCPUs.
> - Enable unload and exec of images.
> 
> David
> 
> 


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

  parent reply	other threads:[~2013-11-13 10:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 14:55 [PATCHv7 0/4] kexec-tools: add support for Xen 4.4 David Vrabel
2013-11-06 14:55 ` [PATCH 1/4] kexec/xen: require libxc from " David Vrabel
2013-11-07 20:35   ` [Xen-devel] " Don Slutz
2013-11-13  3:12   ` Simon Horman
2013-11-06 14:55 ` [PATCH 2/4] kexec/xen: use libxc to get location of crash notes David Vrabel
2013-11-07 20:36   ` [Xen-devel] " Don Slutz
2013-11-06 14:55 ` [PATCH 3/4] kexec/xen: switch to use xc_kexec_get_range for get_xen_vmcoreinfo David Vrabel
2013-11-06 14:55 ` [PATCH 4/4] kexec/xen: directly load images images into Xen David Vrabel
2013-11-07 20:36   ` [Xen-devel] " Don Slutz
2013-11-19  1:20   ` Simon Horman
2013-11-19  8:28     ` Daniel Kiper
2013-11-19  9:19       ` Simon Horman
2013-11-09 19:21 ` [PATCHv7 0/4] kexec-tools: add support for Xen 4.4 Daniel Kiper
2013-11-11 14:35   ` Don Slutz
2013-11-13 10:27 ` David Vrabel [this message]
2013-11-19  1:15   ` Simon Horman

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=52835429.8040708@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=xen-devel@lists.xen.org \
    /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