From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Roman Shaposhnik <roman@zededa.com>
Cc: "Juergen Gross" <JGross@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"Paul Durrant" <Paul.Durrant@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx
Date: Wed, 31 Jul 2019 09:58:37 +0100 [thread overview]
Message-ID: <f161e7b4-38a2-c3a3-4a04-167c3631db8c@citrix.com> (raw)
In-Reply-To: <52afea81-33d3-7120-af72-2987bb634f08@suse.com>
On 31/07/2019 09:34, Jan Beulich wrote:
> On 30.07.2019 19:56, Roman Shaposhnik wrote:
>> On Fri, Jul 26, 2019 at 1:06 AM Jan Beulich <JBeulich@suse.com> wrote:
>>> On 23.07.2019 20:25, Roman Shaposhnik wrote:
>>>> Interestingly enough, adding iommu_inclusive_mapping=1 AND iommu=debug
>>>> booted the system just fine.
>>> Btw (I've noticed this only now) - are you saying without "iommu=debug"
>>> the box does _not_ boot fine, despite the other option?
>> Yes. But it made sense to me since iommu=debug (as per your
>> explanation) overwhelms the CPU and I guess adding
>> iommu_inclusive_mapping=1 avoids the code path that does it?
> I'm afraid I don't follow: My question was whether
> "iommu_inclusive_mapping=1" alone would not allow the box to boot.
> Without "iommu=debug" there's no excessive logging afaict, no
> matter what other IOMMU options you use.
Without inclusive mappings, the system boots but the screen is junk and
there are DMA faults all over the place. With inclusive mappings, it
all "works" fine.
With debug enabled, the DMA faults are spat out to the console for a
short while, until an APIC error occurs and the system wedges completely.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-07-31 8:58 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 19:31 [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx Roman Shaposhnik
2019-07-19 20:02 ` Roman Shaposhnik
2019-07-22 8:20 ` Paul Durrant
2019-07-22 11:48 ` Roger Pau Monné
2019-07-22 11:54 ` Paul Durrant
2019-07-22 13:48 ` Roger Pau Monné
2019-07-22 14:03 ` Paul Durrant
2019-07-22 14:39 ` Roger Pau Monné
2019-07-22 15:02 ` Paul Durrant
2019-07-22 15:21 ` Roger Pau Monné
2019-07-22 23:36 ` Roman Shaposhnik
2019-07-22 23:47 ` Andrew Cooper
2019-07-23 17:32 ` Roman Shaposhnik
2019-07-23 17:35 ` Andrew Cooper
2019-07-23 17:48 ` Roman Shaposhnik
2019-07-23 17:50 ` Andrew Cooper
2019-07-23 17:58 ` Roman Shaposhnik
2019-07-23 18:12 ` Andrew Cooper
2019-07-23 18:25 ` Roman Shaposhnik
2019-07-26 7:58 ` Jan Beulich
2019-07-30 17:56 ` Roman Shaposhnik
2019-07-31 8:34 ` Jan Beulich
2019-07-31 8:58 ` Andrew Cooper [this message]
2019-07-31 9:30 ` Jan Beulich
2019-07-31 19:37 ` Roman Shaposhnik
2019-07-24 12:00 ` Jan Beulich
2019-07-24 12:04 ` Jan Beulich
2019-07-24 11:23 ` Andrew Cooper
2019-07-24 11:40 ` Andrew Cooper
2019-07-24 14:11 ` Roger Pau Monné
2019-07-26 0:47 ` Roman Shaposhnik
2019-07-26 9:35 ` Roger Pau Monné
2019-07-30 9:21 ` Roger Pau Monné
2019-07-30 17:55 ` Roman Shaposhnik
2019-07-31 8:31 ` Jan Beulich
2019-07-31 8:36 ` Roger Pau Monné
2019-07-31 8:43 ` Roger Pau Monné
2019-07-31 19:35 ` Roman Shaposhnik
2019-07-31 19:46 ` Andrew Cooper
2019-07-31 21:03 ` Roman Shaposhnik
2019-08-01 8:15 ` Roger Pau Monné
2019-08-01 18:25 ` Roman Shaposhnik
2019-08-02 8:05 ` Roger Pau Monné
2019-08-06 16:17 ` Roger Pau Monné
2019-08-06 21:48 ` Roman Shaposhnik
2019-08-07 7:08 ` Jan Beulich
2019-08-07 9:57 ` Roger Pau Monné
2019-08-07 10:03 ` Jan Beulich
2019-08-07 7:35 ` Roger Pau Monné
2019-08-07 8:31 ` Jan Beulich
2019-08-07 10:17 ` Roger Pau Monné
2019-08-12 8:57 ` Roger Pau Monné
2019-08-13 19:24 ` Roman Shaposhnik
2019-08-14 8:06 ` Roger Pau Monné
2019-08-19 5:00 ` Roman Shaposhnik
2019-08-19 8:16 ` Roger Pau Monné
2019-08-20 2:03 ` Roman Shaposhnik
2019-08-01 7:35 ` Jan Beulich
2019-07-31 19:30 ` Roman Shaposhnik
2019-08-01 8:45 ` Roger Pau Monné
2019-08-01 18:19 ` Roman Shaposhnik
2019-07-20 16:39 ` Andrew Cooper
2019-07-22 8:03 ` Paul Durrant
2019-07-24 17:42 ` Rich Persaud
2019-07-26 1:13 ` Roman Shaposhnik
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=f161e7b4-38a2-c3a3-4a04-167c3631db8c@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=roger.pau@citrix.com \
--cc=roman@zededa.com \
--cc=xen-devel@lists.xenproject.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).