From: Jeff McGee <jeff.mcgee@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] i915/GuC: Make GuC loads default
Date: Mon, 31 Oct 2016 14:12:56 -0700 [thread overview]
Message-ID: <20161031211256.GS18646@jeffdesk> (raw)
In-Reply-To: <CABVU7+sZsdsJVauA8EeYY4oAGYpMbzc+U5VsbTi1j0gTYaScZg@mail.gmail.com>
I agree that the parameter controls could use a clean-up, which could
include eventual removal of the enable_guc_loading parameter. But for
now loading parameter should be auto by default.
Might be a good idea to temporarily set the has_guc parameter to 0
for BXT and KBL since those firmwares have not yet been made available
(I don't see them on 01.org).
In either case...
Reviewed-by: Jeff McGee <jeff.mcgee@intel.com>
On Mon, Oct 31, 2016 at 10:06:27AM -0700, Rodrigo Vivi wrote:
> Could someone please ack this? We need this before getting HuC.
>
> GuC submission has regressions so the submission is not getting enabled.
> But we need to have GuC loaded to be able to use HuC.
>
> Thanks,
> Rodrigo.
>
> On Thu, Oct 6, 2016 at 11:08 AM, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> > I also asked that same question many times. Maybe they can be unified
> > later when we enable submission by default, but right now I believe
> > this is the way to go, so
> >
> > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >
> >
> > On Thu, Oct 6, 2016 at 11:03 AM, Srivatsa, Anusha
> > <anusha.srivatsa@intel.com> wrote:
> >>
> >>
> >>>-----Original Message-----
> >>>From: Chris Wilson [mailto:chris@chris-wilson.co.uk]
> >>>Sent: Wednesday, October 5, 2016 11:57 PM
> >>>To: Srivatsa, Anusha <anusha.srivatsa@intel.com>
> >>>Cc: intel-gfx@lists.freedesktop.org
> >>>Subject: Re: [Intel-gfx] [PATCH] i915/GuC: Make GuC loads default
> >>>
> >>>On Wed, Oct 05, 2016 at 04:20:04PM -0700, Anusha Srivatsa wrote:
> >>>> Proper functioning of HuC requires GuC to be loaded. Make GuC loads
> >>>> default so that HuC works seemlessly.
> >>>> Also, note that GuC submission is not made default and still needs to
> >>>> be given as a kernel parameter.
> >>>> Once the issues around GuC submission is resolved it is intended to
> >>>> make it default as well.
> >>>
> >>><broken record>Why is this even a separate parameter?</> -Chris
> >>
> >> It is a separate parameter because HuC requires GuC to be loaded. It is ok if command submission is not happening through GuC but GuC "has to" be loaded for HuC to function. Guc_submission parameter enables the command submission through GUC. But, guc_loading parameter ensures not only that the GuC is loaded but also that HuC can now function.
> >>
> >> Anusha
> >>>--
> >>>Chris Wilson, Intel Open Source Technology Centre
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> >
> >
> > --
> > Rodrigo Vivi
> > Blog: http://blog.vivi.eng.br
>
>
>
> --
> Rodrigo Vivi
> Blog: http://blog.vivi.eng.br
> _______________________________________________
> 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-10-31 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 23:20 [PATCH] i915/GuC: Make GuC loads default Anusha Srivatsa
2016-10-05 23:49 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-10-06 6:56 ` [PATCH] " Chris Wilson
2016-10-06 18:03 ` Srivatsa, Anusha
2016-10-06 18:08 ` Rodrigo Vivi
2016-10-31 17:06 ` Rodrigo Vivi
2016-10-31 21:12 ` Jeff McGee [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=20161031211256.GS18646@jeffdesk \
--to=jeff.mcgee@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@gmail.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