From: "Jan Beulich" <JBeulich@novell.com>
To: Allen M Kay <allen.m.kay@intel.com>,
Yang Z Zhang <yang.z.zhang@intel.com>
Cc: Keir Fraser <keir@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Weidong Han <weidong.han@intel.com>
Subject: RE: iommu=0 leading to panic when system defaults to using x2apic
Date: Tue, 14 Dec 2010 17:06:16 +0000 [thread overview]
Message-ID: <4D07B2180200007800027E6B@vpn.id2.novell.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D530193C384E4@orsmsx505.amr.corp.intel.com>
>>> On 14.12.10 at 17:53, "Kay, Allen M" <allen.m.kay@intel.com> wrote:
>> And why is it that Xen panics when the BIOS pre-enabled x2apic
>> mode without also enabling interrupt re-mapping, while Linux
>> (afaict from looking at 2.6.32 code and output from an affected
>> machine) simply enables interrupt re-mapping in this case?
>
> AFAIK, Linux also requires interrupt remapping for x2apic. I believe
> Weidong has fixed the panic issue in Xen when x2apic is enabled without
> enabling interrupt remapping. It should now behave the same way as Linux.
No - just look at the very first if() in enable_bsp_x2apic().
Jan
next prev parent reply other threads:[~2010-12-14 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 9:12 iommu=0 leading to panic when system defaults to using x2apic Jan Beulich
2010-12-10 10:06 ` Keir Fraser
2010-12-10 10:58 ` Jan Beulich
2010-12-10 11:47 ` Keir Fraser
2010-12-10 12:02 ` Jan Beulich
2010-12-10 15:00 ` Zhang, Yang Z
2010-12-10 15:39 ` Jan Beulich
2010-12-10 18:26 ` Kay, Allen M
2010-12-10 18:49 ` Keir Fraser
2010-12-11 0:07 ` Kay, Allen M
2010-12-13 8:15 ` Jan Beulich
2010-12-13 9:03 ` Keir Fraser
2010-12-14 2:25 ` Kay, Allen M
2010-12-14 7:44 ` Keir Fraser
2010-12-14 7:59 ` Keir Fraser
2010-12-15 2:35 ` Kay, Allen M
2010-12-14 8:21 ` Jan Beulich
2010-12-14 8:46 ` Weidong Han
2010-12-14 9:12 ` Jan Beulich
2010-12-14 16:53 ` Kay, Allen M
2010-12-14 17:06 ` Jan Beulich [this message]
2010-12-14 17:08 ` Jan Beulich
2010-12-14 17:52 ` Yinghai Lu
2010-12-14 18:18 ` Keir Fraser
2010-12-15 7:53 ` 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=4D07B2180200007800027E6B@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=allen.m.kay@intel.com \
--cc=keir@xen.org \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@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 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).