From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH 0 of 3] Fix kexec path in xen (take 2)
Date: Wed, 18 May 2011 19:08:13 +0100 [thread overview]
Message-ID: <patchbomb.1305742093@andrewcoop> (raw)
This set of patches is the minimal subset required to get the kexec path working again on Xen 4.x
kdump kernels can't boot if x2apic mode is enabled and the ACPI tables dont state this fact. They also cant boot at all with interrupt remapping enabled.
These patches cause xen to track the local apic boot state and return to it before kexec'ing to a new kernel. It also makes sure to disable IO virtualisation.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
next reply other threads:[~2011-05-18 18:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 18:08 Andrew Cooper [this message]
2011-05-18 18:08 ` [PATCH 1 of 3] apic: record local apic state on boot Andrew Cooper
2011-05-18 18:49 ` Konrad Rzeszutek Wilk
2011-05-18 20:27 ` Andrew Cooper
2011-05-18 20:43 ` Konrad Rzeszutek Wilk
2011-05-19 0:56 ` Tian, Kevin
2011-05-19 8:34 ` Ian Campbell
2011-05-19 16:21 ` Konrad Rzeszutek Wilk
2011-05-19 0:54 ` Tian, Kevin
2011-05-18 23:40 ` Keir Fraser
2011-05-19 11:14 ` Andrew Cooper
2011-05-19 14:26 ` Konrad Rzeszutek Wilk
2011-05-19 14:43 ` Andrew Cooper
2011-05-18 18:08 ` [PATCH 2 of 3] apic: remove 'enabled_via_apicbase' variable Andrew Cooper
2011-05-18 18:53 ` Konrad Rzeszutek Wilk
2011-05-18 20:35 ` Andrew Cooper
2011-05-18 20:45 ` Konrad Rzeszutek Wilk
2011-05-19 3:31 ` Tian, Kevin
2011-05-18 18:08 ` [PATCH 3 of 3] kexec: disable iommu jumping into the kdump kernel Andrew Cooper
2011-05-18 18:49 ` Konrad Rzeszutek Wilk
2011-05-18 20:48 ` Andrew Cooper
2011-05-18 20:57 ` Konrad Rzeszutek Wilk
2011-05-18 21:24 ` Andrew Cooper
2011-05-19 14:32 ` Konrad Rzeszutek Wilk
2011-05-20 0:33 ` Kay, Allen M
2011-05-20 21:55 ` Kay, Allen M
2011-05-18 18:39 ` [PATCH 0 of 3] Fix kexec path in xen (take 2) Konrad Rzeszutek Wilk
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.1305742093@andrewcoop \
--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).