All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: Zack Rusin <zackr@vmware.com>, dri-devel@lists.freedesktop.org
Cc: krastevm@vmware.com, mombasawalam@vmware.com
Subject: Re: [PATCH 1/2] drm/vmwgfx: Remove unused hugepage support
Date: Wed, 27 Apr 2022 06:58:15 +0200	[thread overview]
Message-ID: <0c57c6a1-be61-81ad-c7a2-cadbd82bf88b@shipmail.org> (raw)
In-Reply-To: <20220425203152.1314211-1-zack@kde.org>


On 4/25/22 22:31, Zack Rusin wrote:
> From: Zack Rusin <zackr@vmware.com>
>
> There's no point in explicitly trying to align virtual memory to
> facilitate huge page table entries or huge page memory in buffer objects
> given that they're not being used.
>
> Transparent hugepages support for vram allocations has been gradually
> retired over the last two years making alignment of unmapped areas
> unneeded and pointless.
>
> Signed-off-by: Zack Rusin <zackr@vmware.com>

For the series:

Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>


> ---
>   drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 13 -------------
>   1 file changed, 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> index 5dc02fd806db..45028e25d490 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> @@ -1423,18 +1423,6 @@ static void vmw_debugfs_resource_managers_init(struct vmw_private *vmw)
>   					    root, "system_mob_ttm");
>   }
>   
> -static unsigned long
> -vmw_get_unmapped_area(struct file *file, unsigned long uaddr,
> -		      unsigned long len, unsigned long pgoff,
> -		      unsigned long flags)
> -{
> -	struct drm_file *file_priv = file->private_data;
> -	struct vmw_private *dev_priv = vmw_priv(file_priv->minor->dev);
> -
> -	return drm_get_unmapped_area(file, uaddr, len, pgoff, flags,
> -				     dev_priv->drm.vma_offset_manager);
> -}
> -
>   static int vmwgfx_pm_notifier(struct notifier_block *nb, unsigned long val,
>   			      void *ptr)
>   {
> @@ -1601,7 +1589,6 @@ static const struct file_operations vmwgfx_driver_fops = {
>   	.compat_ioctl = vmw_compat_ioctl,
>   #endif
>   	.llseek = noop_llseek,
> -	.get_unmapped_area = vmw_get_unmapped_area,
>   };
>   
>   static const struct drm_driver driver = {

      parent reply	other threads:[~2022-04-27  4:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 20:31 [PATCH 1/2] drm/vmwgfx: Remove unused hugepage support Zack Rusin
2022-04-25 20:31 ` [PATCH 2/2] drm: Remove the drm_get_unmapped_area() helper Zack Rusin
2022-04-27  4:58 ` Thomas Hellström (Intel) [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=0c57c6a1-be61-81ad-c7a2-cadbd82bf88b@shipmail.org \
    --to=thomas_os@shipmail.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krastevm@vmware.com \
    --cc=mombasawalam@vmware.com \
    --cc=zackr@vmware.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.