From: Martin Peres <martin.peres@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Enable stolen for iommu on snb/ivb
Date: Tue, 17 Sep 2019 14:39:13 +0300 [thread overview]
Message-ID: <22b62176-53bf-3dfa-08f9-ab120766e459@linux.intel.com> (raw)
In-Reply-To: <20190913164337.25829-1-chris@chris-wilson.co.uk>
On 13/09/2019 19:43, Chris Wilson wrote:
> Now that we have CI testing of iommu, let's enable stolen + iommu with a
> lot more confidence that we can diagnose any potential erors.
AFAIK, we still haven't checked that these machines indeed have the
IOMMU enabled yet. Am I wrong?
If I am not, then let's hold the merging of this patch :)
Martin
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> index bfbc3e3daf92..c52ecf525c24 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> @@ -369,13 +369,6 @@ int i915_gem_init_stolen(struct drm_i915_private *dev_priv)
> return 0;
> }
>
> - if (intel_vtd_active() && INTEL_GEN(dev_priv) < 8) {
> - dev_notice(dev_priv->drm.dev,
> - "%s, disabling use of stolen memory\n",
> - "DMAR active");
> - return 0;
> - }
> -
> if (resource_size(&intel_graphics_stolen_res) == 0)
> return 0;
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-17 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 16:43 [PATCH] drm/i915: Enable stolen for iommu on snb/ivb Chris Wilson
2019-09-13 18:23 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-09-17 11:39 ` Martin Peres [this message]
2019-09-17 11:47 ` [PATCH] " Chris Wilson
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=22b62176-53bf-3dfa-08f9-ab120766e459@linux.intel.com \
--to=martin.peres@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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.