From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>,
"Mcgee, Jeff" <jeff.mcgee@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/GuC: Combine the two kernel parameter into one
Date: Tue, 15 Nov 2016 10:30:49 +0000 [thread overview]
Message-ID: <e3551b36-f599-62d1-6f9d-9cd8bcbc8b88@linux.intel.com> (raw)
In-Reply-To: <83F5C7385F545743AD4FB2A62F75B07301937A87@ORSMSX108.amr.corp.intel.com>
On 14/11/2016 17:34, Srivatsa, Anusha wrote:
[snip]
>> One idea could be to hide the guc loading form the user altogether and hence
>> improve usability (decrease exposed complexity) by having only two parameters;
>> i915.enable_guc_scheduling and i915.enable_huc.
> That's a good point. But with this we will have two parameters (which kills the point of why the patch was written in the first place), then we can rather leave it the way it is. Right?
For some reason I thought the HuC patch series add a another module
parameter.
What is the failure mode for HuC is GuC firmware loading is disabled btw?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-15 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 19:11 [PATCH] drm/i915/GuC: Combine the two kernel parameter into one Anusha Srivatsa
2016-11-12 2:21 ` Jeff McGee
2016-11-14 9:34 ` Tvrtko Ursulin
2016-11-14 17:34 ` Srivatsa, Anusha
2016-11-15 10:30 ` Tvrtko Ursulin [this message]
2016-11-15 18:06 ` Srivatsa, Anusha
2016-11-15 22:46 ` Jeff McGee
2016-11-15 22:41 ` Srivatsa, Anusha
2016-11-16 8:34 ` Tvrtko Ursulin
2016-11-16 21:37 ` Srivatsa, Anusha
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=e3551b36-f599-62d1-6f9d-9cd8bcbc8b88@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=anusha.srivatsa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jeff.mcgee@intel.com \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox