From: "Christian König" <deathsimple@vodafone.de>
To: Lauri Kasanen <cand@gmx.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: TTM must be init with cpu-visible VRAM, v2
Date: Fri, 28 Feb 2014 20:56:26 +0100 [thread overview]
Message-ID: <5310E9EA.8020606@vodafone.de> (raw)
In-Reply-To: <20140228205023.9677a7f9.cand@gmx.com>
Am 28.02.2014 19:50, schrieb Lauri Kasanen:
> Without this, a bo may get created in the cpu-inaccessible vram.
> Before the CP engines get setup, all copies are done via cpu memcpy.
>
> This means that the cpu tries to read from inaccessible memory, fails,
> and the radeon module proceeds to disable acceleration.
>
> Doing this has no downsides, as the real VRAM size gets set as soon as the
> CP engines get init.
>
> This is a candidate for 3.14 fixes.
>
> v2: Add comment on why the function is used
>
> Signed-off-by: Lauri Kasanen <cand@gmx.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
And I suggest to add "Cc: stable@vger.kernel.org" as well.
Christian.
> ---
> drivers/gpu/drm/radeon/radeon_ttm.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c b/drivers/gpu/drm/radeon/radeon_ttm.c
> index 3aa853c..b966f85 100644
> --- a/drivers/gpu/drm/radeon/radeon_ttm.c
> +++ b/drivers/gpu/drm/radeon/radeon_ttm.c
> @@ -715,6 +715,9 @@ int radeon_ttm_init(struct radeon_device *rdev)
> DRM_ERROR("Failed initializing VRAM heap.\n");
> return r;
> }
> + /* Change the size here instead of the init above so only lpfn is affected */
> + radeon_ttm_set_active_vram_size(rdev, rdev->mc.visible_vram_size);
> +
> r = radeon_bo_create(rdev, 256 * 1024, PAGE_SIZE, true,
> RADEON_GEM_DOMAIN_VRAM,
> NULL, &rdev->stollen_vga_memory);
next prev parent reply other threads:[~2014-02-28 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 18:50 [PATCH] drm/radeon: TTM must be init with cpu-visible VRAM, v2 Lauri Kasanen
2014-02-28 19:20 ` Alex Deucher
2014-02-28 19:56 ` Christian König [this message]
2014-02-28 20:47 ` Dave Airlie
2014-03-01 9:15 ` Lauri Kasanen
2014-03-01 10:29 ` Christian König
2014-03-02 17:05 ` Alex Deucher
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=5310E9EA.8020606@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=cand@gmx.com \
--cc=dri-devel@lists.freedesktop.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.