From: Anssi Hannula <anssi-253J+yWuVH8@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] gf116: remove copy1 engine
Date: Tue, 02 Dec 2014 00:18:36 +0200 [thread overview]
Message-ID: <547CE93C.1070200@onse.fi> (raw)
In-Reply-To: <1417370178-2048-1-git-send-email-imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
30.11.2014, 19:56, Ilia Mirkin kirjoitti:
> Indications are that no GF116's actually have a copy engine there, but
> actually have the decompression engine. This engine can be made to do
> copies, but that should be done separately.
>
> Unclear why this didn't turn up on all GF116's, but perhaps the
> non-mobile ones came with enough VRAM to not trigger ttm migrations in
> test scenarios.
FWIW, I experienced this on my non-mobile GF116 when keeping the system
running for several days and running graphics-intensive games. I don't
have the card at hand right now so don't know how much VRAM it had, though.
Thanks for getting this figured out :)
> Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=85465
> Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=59168
> Cc: stable@vger.kernel.org
> Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
> ---
> nvkm/engine/device/nvc0.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/nvkm/engine/device/nvc0.c b/nvkm/engine/device/nvc0.c
> index cd05677..72a40f9 100644
> --- a/nvkm/engine/device/nvc0.c
> +++ b/nvkm/engine/device/nvc0.c
> @@ -218,7 +218,6 @@ nvc0_identify(struct nouveau_device *device)
> device->oclass[NVDEV_ENGINE_BSP ] = &nvc0_bsp_oclass;
> device->oclass[NVDEV_ENGINE_PPP ] = &nvc0_ppp_oclass;
> device->oclass[NVDEV_ENGINE_COPY0 ] = &nvc0_copy0_oclass;
> - device->oclass[NVDEV_ENGINE_COPY1 ] = &nvc0_copy1_oclass;
> device->oclass[NVDEV_ENGINE_DISP ] = nva3_disp_oclass;
> device->oclass[NVDEV_ENGINE_PERFMON] = &nvc0_perfmon_oclass;
> break;
>
--
Anssi Hannula
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-12-01 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 17:56 [PATCH] gf116: remove copy1 engine Ilia Mirkin
[not found] ` <1417370178-2048-1-git-send-email-imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2014-12-01 22:18 ` Anssi Hannula [this message]
2014-12-02 21:05 ` Andy Ritger
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=547CE93C.1070200@onse.fi \
--to=anssi-253j+ywuvh8@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+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.