From: Joerg Roedel <joro@8bytes.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Eric Wong <e@80x24.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
"list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>,
Joerg Roedel <joro@8bytes.org>,
" <iommu@lists.linux-foundation.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Date: Tue, 22 Jan 2019 12:01:09 +0100 [thread overview]
Message-ID: <20190122110109.x3zoynemdl3ysbsn@8bytes.org> (raw)
In-Reply-To: <CAKMK7uEX1T6_yXoq_d4Fs2LiWC_tDaEEXv-hTL=S-_4HEeya7A@mail.gmail.com>
Hi Daniel,
On Tue, Jan 22, 2019 at 11:46:39AM +0100, Daniel Vetter wrote:
> Note that the string of platforms which have various issues with iommu
> and igfx is very long, thus far we only disabled it where there's no
> workaround to stop it from hanging the box, but otherwise left it
> enabled. So if we make a policy change to also disable it anywhere
> where it doesn't work well (instead of not at all), there's a pile
> more platforms to switch.
I think its best to just disable iommu for the igfx devices on these
platforms. Can you pick up Eric's patch and extend it with the list of
affected platforms?
Thanks,
Joerg
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-22 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 11:49 iommu_intel or i915 regression in 4.18, 4.19.12 and drm-tip Eric Wong
2019-01-02 9:42 ` Joonas Lahtinen
2019-01-04 1:06 ` Eric Wong
2019-01-04 8:39 ` Joonas Lahtinen
2019-01-18 12:17 ` [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx Eric Wong
2019-01-22 10:39 ` Joerg Roedel
2019-01-22 10:46 ` Daniel Vetter
2019-01-22 11:01 ` Joerg Roedel [this message]
2019-01-22 14:48 ` Joonas Lahtinen
2019-01-22 16:51 ` Joerg Roedel
2019-01-23 15:02 ` Joonas Lahtinen
2019-01-23 16:49 ` Joerg Roedel
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=20190122110109.x3zoynemdl3ysbsn@8bytes.org \
--to=joro@8bytes.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwmw2@infradead.org \
--cc=e@80x24.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.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