All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>,
	Ben Skeggs <bskeggs@redhat.com>,
	nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@ubuntu.com>,
	Ronald <ronald645@gmail.com>
Subject: Re: [PATCH] drm/nouveau: fix TTM_PL_TT memtype on pre-nv50
Date: Sun, 16 Feb 2014 11:43:51 +0100	[thread overview]
Message-ID: <53009667.1050904@canonical.com> (raw)
In-Reply-To: <1392524821-10358-1-git-send-email-imirkin@alum.mit.edu>

op 16-02-14 05:27, Ilia Mirkin schreef:
> Commit a55409066 ("drm/nv50-: map TTM_PL_SYSTEM through a BAR for CPU
> access") made it possible to work with tiled memory. However
> mem->mm_node is not a nouveau_mem for AGP-using pre-NV50 cards, but a
> drm_mm_node, as created by the ttm_bo_manager_func. As such, extend the
> untiled check to explicitly include all pre-nv50 cards.
>
> Reported-by: Ronald <ronald645@gmail.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74613
> Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
> ---
>
> Hmmm... this seems like a really fragile semantic, I wonder if more
> mem->mm_node usages have to be audited. But this one's quick and easy. I'd
> rather see something a little more solid around dealing with these
> differences, but not sure how without reading all the ttm gunk. Perhaps just
> make sure it's always a nouveau_mem by wrapping the ttm_bo_manager logic?
>
>   drivers/gpu/drm/nouveau/nouveau_bo.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c b/drivers/gpu/drm/nouveau/nouveau_bo.c
> index 488686d..4aed171 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_bo.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_bo.c
> @@ -1249,7 +1249,7 @@ nouveau_ttm_io_mem_reserve(struct ttm_bo_device *bdev, struct ttm_mem_reg *mem)
>   			mem->bus.is_iomem = !dev->agp->cant_use_aperture;
>   		}
>   #endif
> -		if (!node->memtype)
> +		if (nv_device(drm->device)->card_type < NV_50 || !node->memtype)
>   			/* untiled */
>   			break;
>   		/* fallthrough, tiled memory */
Acked-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>

      parent reply	other threads:[~2014-02-16 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16  4:27 [PATCH] drm/nouveau: fix TTM_PL_TT memtype on pre-nv50 Ilia Mirkin
     [not found] ` <1392524821-10358-1-git-send-email-imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2014-02-16  9:29   ` Ronald
2014-02-16 10:43 ` Maarten Lankhorst [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=53009667.1050904@canonical.com \
    --to=maarten.lankhorst@canonical.com \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --cc=maarten.lankhorst@ubuntu.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ronald645@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 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.