From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir@xen.org>
Cc: "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 12:02:30 +0000 [thread overview]
Message-ID: <4D0224E602000078000273AD@vpn.id2.novell.com> (raw)
In-Reply-To: <C927C3C4.C5DD%keir@xen.org>
>>> On 10.12.10 at 12:47, Keir Fraser <keir@xen.org> wrote:
> On 10/12/2010 10:58, "Jan Beulich" <JBeulich@novell.com> wrote:
>
>>>>> On 10.12.10 at 11:06, Keir Fraser <keir@xen.org> wrote:
>>> Are you looking at xen-4.0? I think you should look at latest xen-unstable
>>
>> I looked at 4.0 in parallel with -unstable (non-staging) as of
>> yesterday.
>
> Even before yesterday, xen-unstable benefits from c/s 22388, which is
> intended to work around the iommu=0/x2apic=0 dependency a bit. Not sure if
> it is fully satisfactory. And it is not backported to 4.0 as yet because,
> well, I don't understand this crap enough, basically.
Ah, yes, that makes it better (and I must then have looked at an
older snapshot of -unstable instead).
Still, as you say, a lot of questions remain. On top of what you and
I raised already, I wonder whether the APIC-ID-exceeding-8-bits
case is really being handled correctly now when iommu=0.
Jan
next prev parent reply other threads:[~2010-12-10 12:02 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 [this message]
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=4D0224E602000078000273AD@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir@xen.org \
--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).