xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@novell.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: iommu=0 leading to panic when system defaults to using x2apic
Date: Fri, 10 Dec 2010 10:06:53 +0000	[thread overview]
Message-ID: <C927AC3D.C5A6%keir@xen.org> (raw)
In-Reply-To: <4D01FD050200007800027296@vpn.id2.novell.com>

Are you looking at xen-4.0? I think you should look at latest xen-unstable
and we can backpoprt patches if that is more satisfactory. I did a big
cleanup patch yesterday which makes the code smaller and clearer than it
was, yet I don't understand the dependencies between x2apic-enabled-by-bios
and the need for interrupt remapping, and all that stuff.

 -- Keir

On 10/12/2010 09:12, "Jan Beulich" <JBeulich@novell.com> wrote:

> Why wouldn't iommu=0 imply not using the x2apic, if use of the
> iommu indeed is a prerequisite (which by itself seems questionable
> as long as APIC IDs aren't wider than 8 bits)?
> 
> Looking further at enable_bsp_x2apic(), I also wonder whether
> the pre-enabled case, when specifying iommu=0 and x2apic=0,
> can actually work if iommu=0 is a prerequisite (intremap_enabled()
> would return 1 in that case afaics, so the early check doesn't help).
> 
> Thanks, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-12-10 10: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 [this message]
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
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=C927AC3D.C5A6%keir@xen.org \
    --to=keir@xen.org \
    --cc=JBeulich@novell.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).