From: "Christian König" <deathsimple@vodafone.de>
To: "Michel Dänzer" <michel@daenzer.net>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: Clean up radeon_uvd_force_into_uvd_segment
Date: Tue, 28 Oct 2014 11:32:46 +0100 [thread overview]
Message-ID: <544F70CE.3000902@vodafone.de> (raw)
In-Reply-To: <1414488529-3492-1-git-send-email-michel@daenzer.net>
Am 28.10.2014 um 10:28 schrieb Michel Dänzer:
> From: Michel Dänzer <michel.daenzer@amd.com>
>
> It was adding a second placement for the second 256MB segment of VRAM,
> which is not a good idea for several reasons:
>
> * It fills up the first 256MB segment (which is also typically the CPU
> accessible part) of VRAM first, even for BOs which could go into the
> second 256MB segment. Only once there is no space in the first segment
> does it fall back to the second segment.
> * It doesn't work with RADEON_GEM_NO_CPU_ACCESS BOs, which already use
> two VRAM placements.
>
> Change it to instead restrict the range for each VRAM placement. If the
> BO can go into the second 256MB segment, set up the range to include
> both segments, and set the TTM_PL_FLAG_TOPDOWN flag. That should result
> in preferring the second segment for those BOs, falling back to the
> first segment.
>
> Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
I'm not sure if this will work correctly. Please keep in mind that even
if BOs can be in the second segment they are not allowed to cross
segment borders.
E.g. if you just set lpfn = (2 * 256 * 1024 * 1024) >> PAGE_SHIFT it
might happen that the first halve of a BO lands in the first 256MB
segment and the second halve of a BO in the second 256MB segment.
Have you considered that as well?
Regards,
Christian.
> ---
> drivers/gpu/drm/radeon/radeon_uvd.c | 31 +++++++++++++++----------------
> 1 file changed, 15 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_uvd.c b/drivers/gpu/drm/radeon/radeon_uvd.c
> index 11b6624..eca0ea96 100644
> --- a/drivers/gpu/drm/radeon/radeon_uvd.c
> +++ b/drivers/gpu/drm/radeon/radeon_uvd.c
> @@ -259,27 +259,26 @@ int radeon_uvd_resume(struct radeon_device *rdev)
> void radeon_uvd_force_into_uvd_segment(struct radeon_bo *rbo,
> uint32_t allowed_domains)
> {
> + unsigned lpfn;
> int i;
>
> - for (i = 0; i < rbo->placement.num_placement; ++i) {
> - rbo->placements[i].fpfn = 0 >> PAGE_SHIFT;
> - rbo->placements[i].lpfn = (256 * 1024 * 1024) >> PAGE_SHIFT;
> - }
> -
> - /* If it must be in VRAM it must be in the first segment as well */
> if (allowed_domains == RADEON_GEM_DOMAIN_VRAM)
> - return;
> + /* If it must be in VRAM, it must be in the first 256MB segment */
> + lpfn = (256 * 1024 * 1024) >> PAGE_SHIFT;
> + else
> + /* Allow second 256MB segment as well */
> + lpfn = (2 * 256 * 1024 * 1024) >> PAGE_SHIFT;
>
> - /* abort if we already have more than one placement */
> - if (rbo->placement.num_placement > 1)
> - return;
> + for (i = 0; i < rbo->placement.num_placement; ++i) {
> + if (!(rbo->placements[i].flags & TTM_PL_FLAG_VRAM))
> + continue;
>
> - /* add another 256MB segment */
> - rbo->placements[1] = rbo->placements[0];
> - rbo->placements[1].fpfn += (256 * 1024 * 1024) >> PAGE_SHIFT;
> - rbo->placements[1].lpfn += (256 * 1024 * 1024) >> PAGE_SHIFT;
> - rbo->placement.num_placement++;
> - rbo->placement.num_busy_placement++;
> + if (allowed_domains != RADEON_GEM_DOMAIN_VRAM)
> + rbo->placements[i].flags |= TTM_PL_FLAG_TOPDOWN;
> +
> + if (!rbo->placements[i].lpfn || rbo->placements[i].lpfn > lpfn)
> + rbo->placements[i].lpfn = lpfn;
> + }
> }
>
> void radeon_uvd_free_handles(struct radeon_device *rdev, struct drm_file *filp)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-28 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 9:28 [PATCH] drm/radeon: Clean up radeon_uvd_force_into_uvd_segment Michel Dänzer
2014-10-28 10:32 ` Christian König [this message]
2014-10-29 8:58 ` Michel Dänzer
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=544F70CE.3000902@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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.