xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Yinghai Lu <yinghai@kernel.org>, Jan Beulich <JBeulich@novell.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
	Weidong Han <weidong.han@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Allen M Kay <allen.m.kay@intel.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: iommu=0 leading to panic when system defaults  to using x2apic
Date: Tue, 14 Dec 2010 18:18:45 +0000	[thread overview]
Message-ID: <C92D6585.CE99%keir@xen.org> (raw)
In-Reply-To: <4D07AEF3.7010306@kernel.org>

On 14/12/2010 17:52, "Yinghai Lu" <yinghai@kernel.org> wrote:

> On 12/14/2010 09:08 AM, Jan Beulich wrote:
>>>>> 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.
>> 
>> Oh, and I should have added that I'm currently polishing up
>> patches from Yinghai Lu to address this as well as other
>> problems preventing (certain?) large boxes from booting or
>> functioning correctly.
> 
> Yes, just want to make xen aligned to current Linux kernel behavior.
> BIOS guys said why Linux non-xen kernel is happy but xen kernel is not.
> 
> please check attached patches. Our big box with x2apic-preenabled, AND half
> cpus' apic id are above 255.
> 
> They are on top of xen-4.0.1. and first one is from Weidong in unstable.

I assume Jan is going to help with posting these as a regular patch series
for inclusion, with separate patches for 4.0 and 4.1 as appropriate.

 -- Keir

> Thanks
> 
> Yinghai Lu
> 

  reply	other threads:[~2010-12-14 18:18 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
2010-12-14 17:08                   ` Jan Beulich
2010-12-14 17:52                     ` Yinghai Lu
2010-12-14 18:18                       ` Keir Fraser [this message]
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=C92D6585.CE99%keir@xen.org \
    --to=keir@xen.org \
    --cc=JBeulich@novell.com \
    --cc=allen.m.kay@intel.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=weidong.han@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yang.z.zhang@intel.com \
    --cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).