From: Chris Wilson <chris@chris-wilson.co.uk>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915/uc: Stop sanitizing enable_guc modparam
Date: Tue, 30 Jul 2019 19:23:21 +0100 [thread overview]
Message-ID: <156451100107.6373.6432960079841559038@skylake-alporthouse-com> (raw)
In-Reply-To: <20190730181903.17820-4-michal.wajdeczko@intel.com>
Quoting Michal Wajdeczko (2019-07-30 19:19:03)
> As we already track GuC/HuC uses by other means than modparam
> there is no point in sanitizing it. Just scan modparam for
> major discrepancies between what was requested vs actual.
Note that igt is using this modparam to discover if guc submission is
active. :|
Fortunately, it appears that no one is using that facility so quickly
remove it!
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-30 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 18:19 [PATCH 0/3] Don't sanitize enable_guc Michal Wajdeczko
2019-07-30 18:19 ` [PATCH 1/3] drm/i915/uc: Consider enable_guc modparam during fw selection Michal Wajdeczko
2019-07-30 19:07 ` Chris Wilson
2019-07-31 13:19 ` Michal Wajdeczko
2019-07-31 13:22 ` Chris Wilson
2019-07-30 18:19 ` [PATCH 2/3] drm/i915/guc: Use dedicated flag to track submission mode Michal Wajdeczko
2019-07-30 19:11 ` Chris Wilson
2019-07-31 18:00 ` [PATCH v3 2/4] drm/i915/uc: Consider enable_guc modparam during fw selection Michal Wajdeczko
2019-07-31 19:13 ` Chris Wilson
2019-07-30 18:19 ` [PATCH 3/3] drm/i915/uc: Stop sanitizing enable_guc modparam Michal Wajdeczko
2019-07-30 18:23 ` Chris Wilson [this message]
2019-07-30 21:54 ` ✗ Fi.CI.CHECKPATCH: warning for Don't sanitize enable_guc Patchwork
2019-07-30 22:15 ` ✓ Fi.CI.BAT: success " Patchwork
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=156451100107.6373.6432960079841559038@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
/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.