From: Jani Nikula <jani.nikula@intel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 for -fixes] drm/i915: Disable stolen memory when DMAR is active
Date: Thu, 20 Mar 2014 09:36:18 +0200 [thread overview]
Message-ID: <871txxxqx9.fsf@intel.com> (raw)
In-Reply-To: <1395262305.19007.41.camel@shinybook.infradead.org>
On Wed, 19 Mar 2014, David Woodhouse <dwmw2@infradead.org> wrote:
> On Tue, 2014-03-18 at 14:59 +0200, Jani Nikula wrote:
>> From: Chris Wilson <chris@chris-wilson.co.uk>
>>
>> We have reports of heavy screen corruption if we try to use the stolen
>> memory reserved by the BIOS whilst the DMA-Remapper is active. This
>> quirk may be only specific to a few machines or BIOSes, but first lets
>> apply the big hammer and always disable use of stolen memory when DMAR
>> is active.
>>
>> v2 by Jani: Rebase on -fixes, only look at intel_iommu_gfx_mapped.
>
> Perhaps this (and all similar workarounds) should be predicated on
> i915_preliminary_hw_support? When people are using the Linux kernel for
> chipset validation, we sure as hell don't want to silently disable this
> stuff and let them think it's working when it's not.
Or an additional knob, in case it's really not working and people want
to get other things depending on prelim hw support done.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-03-20 7:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 12:14 [PATCH] drm/i915: Disable stolen memory when DMAR is active Chris Wilson
2014-03-05 15:17 ` Daniel Vetter
2014-03-05 15:32 ` Chris Wilson
2014-03-05 17:39 ` Daniel Vetter
2014-03-14 13:10 ` Jani Nikula
2014-03-18 12:59 ` [PATCH v2 for -fixes] " Jani Nikula
2014-03-18 16:48 ` Daniel Vetter
2014-03-18 16:50 ` Daniel Vetter
2014-03-19 9:07 ` Jani Nikula
2014-03-19 20:51 ` David Woodhouse
2014-03-20 7:36 ` Jani Nikula [this message]
2014-03-20 7:49 ` David Woodhouse
2014-03-20 9:23 ` Jani Nikula
2014-03-20 9:45 ` Daniel Vetter
2014-03-20 10:21 ` David Woodhouse
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=871txxxqx9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dwmw2@infradead.org \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.