From: Lukas Wunner <lukas@wunner.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add a module option for disabling use of stolen memory
Date: Sat, 11 Jun 2016 22:41:28 +0200 [thread overview]
Message-ID: <20160611204128.GA20361@wunner.de> (raw)
In-Reply-To: <1465633271-4316-1-git-send-email-chris@chris-wilson.co.uk>
On Sat, Jun 11, 2016 at 09:21:11AM +0100, Chris Wilson wrote:
> One of the first steps in triaging memory corruption on module load is
> to disable stolen. (It helps reduce the impact of the BIOS clobbering
> our memory since we allocate our ringbuffers and initial objects from
> stolen, if they are clobbered we get an immediate hang and garbage on
> screen.) Rather than requesting bug reporters patch their kernel to test
> the theory, allow us to disable stolen through a module option.
Just a quick drive-by observation, intelfb_alloc() calls
i915_gem_object_create_stolen() and if I follow the call chain
in that function it seems to me that dev_priv->mm.stolen_base == 0
isn't checked anywhere, so this looks like something that might break
with i915.enable_stolen=0. But probably that's what you meant with
"secondary effects".
Best regards,
Lukas
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem_stolen.c | 5 +++++
> drivers/gpu/drm/i915/i915_params.c | 6 ++++++
> drivers/gpu/drm/i915/i915_params.h | 1 +
> 3 files changed, 12 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c
> index e9cd82290408..bb8567b1d6a4 100644
> --- a/drivers/gpu/drm/i915/i915_gem_stolen.c
> +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c
> @@ -411,6 +411,11 @@ int i915_gem_init_stolen(struct drm_device *dev)
> }
> #endif
>
> + if (!i915.enable_stolen) {
> + DRM_INFO("Disabling use of stolen memory at user request.\n");
> + return 0;
> + }
> +
> if (ggtt->stolen_size == 0)
> return 0;
>
> diff --git a/drivers/gpu/drm/i915/i915_params.c b/drivers/gpu/drm/i915/i915_params.c
> index 573e78723fc5..511528199aec 100644
> --- a/drivers/gpu/drm/i915/i915_params.c
> +++ b/drivers/gpu/drm/i915/i915_params.c
> @@ -60,6 +60,7 @@ struct i915_params i915 __read_mostly = {
> .enable_dp_mst = true,
> .inject_load_failure = 0,
> .enable_dpcd_backlight = false,
> + .enable_stolen = true,
> };
>
> module_param_named(modeset, i915.modeset, int, 0400);
> @@ -119,6 +120,11 @@ MODULE_PARM_DESC(enable_hangcheck,
> "WARNING: Disabling this can cause system wide hangs. "
> "(default: true)");
>
> +module_param_named(enable_stolen, i915.enable_stolen, bool, 0400);
> +MODULE_PARM_DESC(enable_stolen,
> + "Enable use of memory reserved (stolen) by the BIOS for graphics. "
> + "(default: true)");
> +
> module_param_named_unsafe(enable_ppgtt, i915.enable_ppgtt, int, 0400);
> MODULE_PARM_DESC(enable_ppgtt,
> "Override PPGTT usage. "
> diff --git a/drivers/gpu/drm/i915/i915_params.h b/drivers/gpu/drm/i915/i915_params.h
> index 1323261a0cdd..f126decae848 100644
> --- a/drivers/gpu/drm/i915/i915_params.h
> +++ b/drivers/gpu/drm/i915/i915_params.h
> @@ -63,6 +63,7 @@ struct i915_params {
> bool nuclear_pageflip;
> bool enable_dp_mst;
> bool enable_dpcd_backlight;
> + bool enable_stolen;
> };
>
> extern struct i915_params i915 __read_mostly;
> --
> 2.8.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-06-11 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 8:21 [PATCH] drm/i915: Add a module option for disabling use of stolen memory Chris Wilson
2016-06-11 8:49 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-06-11 15:22 ` [PATCH] " Jani Nikula
2016-06-11 17:00 ` Chris Wilson
2016-06-11 18:24 ` Jani Nikula
2016-06-11 20:41 ` Lukas Wunner [this message]
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=20160611204128.GA20361@wunner.de \
--to=lukas@wunner.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox