Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/ttm: remove the virtualized start hack
Date: Fri, 24 Feb 2023 17:32:09 +0100	[thread overview]
Message-ID: <d187005f-b10e-2d1c-3da5-514585717a8a@intel.com> (raw)
In-Reply-To: <20221220112736.161642-1-matthew.auld@intel.com>

On 20.12.2022 12:27, Matthew Auld wrote:
> This was mostly needed to differentiate between mappable and
> non-mappable lmem, such that ttm would understand non-mappable ->
> mappable moves (or vice versa), and not just turn them into noops. We
> have since gained proper .intersects() and .compatible() hooks for the
> resource manager, which takes care of this for us.
> 
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>

Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>

Regards
Andrzej

> ---
>   drivers/gpu/drm/i915/i915_ttm_buddy_manager.c | 7 -------
>   1 file changed, 7 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_ttm_buddy_manager.c b/drivers/gpu/drm/i915/i915_ttm_buddy_manager.c
> index a72698a2dbc8..a1bc804cfa15 100644
> --- a/drivers/gpu/drm/i915/i915_ttm_buddy_manager.c
> +++ b/drivers/gpu/drm/i915/i915_ttm_buddy_manager.c
> @@ -139,13 +139,6 @@ static int i915_ttm_buddy_man_alloc(struct ttm_resource_manager *man,
>   
>   	mutex_unlock(&bman->lock);
>   
> -	if (place->lpfn - place->fpfn == n_pages)
> -		bman_res->base.start = place->fpfn;
> -	else if (lpfn <= bman->visible_size)
> -		bman_res->base.start = 0;
> -	else
> -		bman_res->base.start = bman->visible_size;
> -
>   	*res = &bman_res->base;
>   	return 0;
>   


      parent reply	other threads:[~2023-02-24 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 11:27 [Intel-gfx] [PATCH] drm/i915/ttm: remove the virtualized start hack Matthew Auld
2022-12-21 23:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-12-22  2:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-02-24 11:32 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-02-24 16:32 ` Andrzej Hajda [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=d187005f-b10e-2d1c-3da5-514585717a8a@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=nirmoy.das@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox