From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: "Han, Weidong" <weidong.han@intel.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: ACPI-Tables corrupted?
Date: Thu, 29 Jul 2010 11:04:04 +0200 [thread overview]
Message-ID: <4C514404.3020502@ts.fujitsu.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659732874B82C@shsmsx501.ccr.corp.intel.com>
On 07/29/2010 09:37 AM, Jiang, Yunhong wrote:
> Sorry that I didn't notice it is for crash kernel. In fact, I tried kexec before and never succed to bring it up.
>
> What do you mean of "stab at disabling x2apic"? You mean we need disable x2apic before transfer control to crash kernel, right?
>
> Per my understanding, with kexec, when system crash, it will jump directly to new kernel's entry point, no guest destroy (i.e. clean-up), not reset signal to cpu/chipset, right?
> If yes, another issue need be considered is VT-d. I didn't find the vt-d disable code in xen's kexec_crash code, if the new kernel has no idea of vt-d (thus does not reset the vt-d engine), it may have trouble. Or, will the kexec kernel not use device assigned to guest?
>
> Of course it is ok if crash kernel support vt-d too.
Seems to be the case here.
A patched crash kernel which just took the zapped DMAR entry as a valid one
succeeded in writing a vmcore.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2010-07-29 9:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 9:38 ACPI-Tables corrupted? Juergen Gross
2010-07-28 10:03 ` Keir Fraser
2010-07-28 11:26 ` Juergen Gross
2010-07-28 11:39 ` Keir Fraser
2010-07-28 12:13 ` Juergen Gross
2010-07-28 12:45 ` Keir Fraser
2010-07-28 13:27 ` Juergen Gross
2010-07-28 13:36 ` Konrad Rzeszutek Wilk
2010-07-29 6:19 ` Juergen Gross
2010-07-29 6:39 ` Keir Fraser
2010-07-29 6:48 ` Juergen Gross
2010-07-29 6:48 ` Keir Fraser
2010-07-29 6:53 ` Juergen Gross
2010-08-06 13:39 ` Jan Beulich
2010-08-06 14:04 ` Keir Fraser
2010-07-29 6:31 ` Jiang, Yunhong
2010-07-29 6:40 ` Keir Fraser
2010-07-29 6:48 ` Keir Fraser
2010-07-29 7:37 ` Jiang, Yunhong
2010-07-29 9:04 ` Juergen Gross [this message]
2010-07-29 9:33 ` Keir Fraser
2010-07-29 10:24 ` Keir Fraser
2010-07-30 4:47 ` Juergen Gross
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=4C514404.3020502@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=allen.m.kay@intel.com \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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.