From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH 0 of 4] KEXEC subsystem fixes and changes
Date: Fri, 9 Mar 2012 14:42:00 +0000 [thread overview]
Message-ID: <patchbomb.1331304120@andrewcoop.uk.xensource.com> (raw)
This patch series implement changes to the kexec system in Xen, both along the
lines of better supporting 32bit crash kernels on 64bit Xen, and providing more
useful information to the crash kernel.
Most of these patches have been submitted upstream in the past; They are largely
unchanged in this new submission. The main new one is patch 4 which introduces
the crashtables mechanism of passing information to the crashdump kernel using
ELF CORE notes. The set of patches (ported to xen-4.1) have been tested against
a wide range of hardware.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
next reply other threads:[~2012-03-09 14:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 14:42 Andrew Cooper [this message]
2012-03-09 14:42 ` [PATCH 1 of 4] KEXEC: Allocate crash notes on boot Andrew Cooper
2012-03-09 15:41 ` Jan Beulich
2012-03-09 16:08 ` Andrew Cooper
2012-03-09 16:58 ` Jan Beulich
2012-03-09 14:42 ` [PATCH 2 of 4] x86: Introduce "top_of_mem" Andrew Cooper
2012-03-09 15:43 ` Jan Beulich
2012-03-09 16:46 ` Andrew Cooper
2012-03-09 17:00 ` Jan Beulich
2012-03-09 14:42 ` [PATCH 3 of 4] KEXEC: Allocate crash structures in low memory Andrew Cooper
2012-03-09 15:52 ` Keir Fraser
2012-03-09 16:24 ` Andrew Cooper
2012-03-09 16:30 ` Keir Fraser
2012-03-09 15:55 ` Jan Beulich
2012-03-09 17:01 ` Andrew Cooper
2012-03-09 14:42 ` [PATCH 4 of 4] KEXEC: Introduce new crashtables interface Andrew Cooper
2012-03-09 16:11 ` Jan Beulich
2012-03-09 17:33 ` Andrew Cooper
2012-03-11 9:59 ` Jan Beulich
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=patchbomb.1331304120@andrewcoop.uk.xensource.com \
--to=andrew.cooper3@citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).