From: Andy Ritger <aritger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
gpu-public-documentation
<gpu-public-documentation-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: Second copy engine on GF116
Date: Thu, 20 Nov 2014 22:16:56 -0800 [thread overview]
Message-ID: <20141121061656.GA897@parker.nvidia.com> (raw)
In-Reply-To: <CAKb7UvjB4fY+7eERavM=dZ5HYX+=CwHKyFkm3Px=j-7Ap38ZCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Ilia,
Actually 0x90b8 is different than copy engine. I'm not very familiar
with it, but 0x90b8 is an engine for performing LZO decompression as
part of performing the copy. It has a variety of limitations (e.g.,
cannot handle blocklinear format), and was only in a few Fermi chips,
as I understand it.
It is probably easiest to just ignore it. You can distinguish this
decompress engine from normal copy engine by looking at the CE capability
register on falcon (0x00000650). If bit 2 is '1', then the falcon is
a decompress engine.
I hope that helps,
- Andy
On Thu, Nov 20, 2014 at 02:18:02PM -0500, Ilia Mirkin wrote:
> Hello,
>
> There's a long-standing bug on nouveau (this is a sample bug, but the
> issue has been around for a while:
> https://bugs.freedesktop.org/show_bug.cgi?id=85465) whereby we attempt
> to use the second PCOPY engine on GF116, and it is sometimes does
> nothing, despite mmio register 22500 saying that it's not disabled
> (0x22500 == 0 for this user). In the bug you can see a dump from
> 22400..22600, and all values after 22440 are read as 0. The issue
> appears to be more common on mobile GF116's, but I don't know that the
> correlation is 100%. No errors are reported by the FIFO or invalid
> mmio reads, but the data transfer just does not happen. Switching to
> using the first copy engine resolves things, so it's unlikely to be a
> more systemic issue in nouveau's usage of the copy engine.
>
> To be clear, when I'm talking about the second PCOPY engine, I'm
> talking about the engine at mmio 0x105000, and whose fifo class id is
> 0x90b8.
>
> Any information on properly detecting that the engine is, in fact,
> missing, would be greatly appreciated. Or, conversely, an assurance
> that the engine _is_ there on all GF116's and we're just not
> initializing something properly, along with perhaps some suggestions
> as to what we might be missing.
>
> Thanks,
>
> Ilia Mirkin
> imirkin@alum.mit.edu
> _______________________________________________
> Nouveau mailing list
> Nouveau@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-11-21 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 19:18 Second copy engine on GF116 Ilia Mirkin
[not found] ` <CAKb7UvjB4fY+7eERavM=dZ5HYX+=CwHKyFkm3Px=j-7Ap38ZCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-21 6:16 ` Andy Ritger [this message]
[not found] ` <20141121061656.GA897-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2014-11-21 6:39 ` Ilia Mirkin
[not found] ` <CAKb7UviMqzsBbbJBmTFH+Bu2+uTv=oOK2w3CWeCovBfsBys8wA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-25 1:33 ` Andy Ritger
[not found] ` <20141125013301.GL22016-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2014-11-25 15:57 ` Ilia Mirkin
[not found] ` <CAKb7Uvh1dw4OfPsB9gzjq-En7eFaek+efo2N2dGSRj+xPJAw+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-25 21:05 ` Andy Ritger
[not found] ` <20141125210520.GF32262-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2014-11-25 21:12 ` Ilia Mirkin
2014-11-26 1:18 ` Marcin Kościelnicki
[not found] ` <54752A61.4070303-mP9o5jsk0RY@public.gmane.org>
2014-11-27 1:05 ` Andy Ritger
2014-11-25 18:28 ` Marcin Kościelnicki
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=20141121061656.GA897@parker.nvidia.com \
--to=aritger-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=gpu-public-documentation-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.