intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	Dave Airlie <airlied@gmail.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PULL] drm-intel-next-fixes
Date: Fri, 14 Jan 2022 14:23:01 +0100	[thread overview]
Message-ID: <YeF5NQUzc4UKO465@phenom.ffwll.local> (raw)
In-Reply-To: <Yd/xzyCM87rfrwQT@tursulin-mobl2>

On Thu, Jan 13, 2022 at 09:33:03AM +0000, Tvrtko Ursulin wrote:
> 
> Hi Dave and Daniel,
> 
> A few fixes for the merge window.
> 
> One dealing with runtime PM handling on the PXP unbind path and a few
> regarding the newly added TTM backend support.
> 
> Regards,
> 
> Tvrtko
> 
> ---
> 
> drm-intel-next-fixes-2022-01-13:
> - Hold runtime PM wakelock during PXP unbind (Juston Li)
> - Three fixes for the TTM backend fault handling (Matthew Auld)
> - Make sure to unmap when purging in the TTM backend (Matthew Auld)
> The following changes since commit c65fe9cbbfd61dbc12868f9ed4940c80fcb249e8:
> 
>   drm/i915/fbc: Remember to update FBC state even when not reallocating CFB (2021-12-27 11:46:48 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2022-01-13

Pulled, thanks.
-Daniel

> 
> for you to fetch changes up to 6ef295e34297433c78ea02dfcf1c649a769050bb:
> 
>   drm/i915/ttm: ensure we unmap when purging (2022-01-10 14:00:47 +0000)
> 
> ----------------------------------------------------------------
> - Hold runtime PM wakelock during PXP unbind (Juston Li)
> - Three fixes for the TTM backend fault handling (Matthew Auld)
> - Make sure to unmap when purging in the TTM backend (Matthew Auld)
> 
> ----------------------------------------------------------------
> Juston Li (1):
>       drm/i915/pxp: Hold RPM wakelock during PXP unbind
> 
> Matthew Auld (4):
>       drm/i915: don't call free_mmap_offset when purging
>       drm/i915/ttm: only fault WILLNEED objects
>       drm/i915/ttm: add unmap_virtual callback
>       drm/i915/ttm: ensure we unmap when purging
> 
>  drivers/gpu/drm/i915/gem/i915_gem_mman.c           |  3 +++
>  drivers/gpu/drm/i915/gem/i915_gem_object_types.h   |  1 +
>  drivers/gpu/drm/i915/gem/i915_gem_pages.c          |  1 -
>  drivers/gpu/drm/i915/gem/i915_gem_ttm.c            | 27 +++++++++++++++++++++-
>  drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c | 18 ++++-----------
>  drivers/gpu/drm/i915/pxp/intel_pxp_tee.c           |  5 +++-
>  6 files changed, 38 insertions(+), 17 deletions(-)

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2022-01-14 13:23 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  9:33 [Intel-gfx] [PULL] drm-intel-next-fixes Tvrtko Ursulin
2022-01-14 13:23 ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08 14:04 Jani Nikula
2023-11-10 15:48 ` Daniel Vetter
2023-08-31 21:28 Rodrigo Vivi
2023-08-24 12:34 Rodrigo Vivi
2023-07-06  8:24 Tvrtko Ursulin
2023-06-29 10:02 Tvrtko Ursulin
2023-06-21  9:54 Tvrtko Ursulin
2023-05-04 13:01 Joonas Lahtinen
2023-04-27 11:23 Joonas Lahtinen
2023-04-20  8:12 Joonas Lahtinen
2023-04-13 12:12 Joonas Lahtinen
2023-04-13 18:47 ` Daniel Vetter
2023-02-27 10:17 Jani Nikula
2023-02-17 12:24 Jani Nikula
2022-12-15 20:36 Rodrigo Vivi
2022-12-01 16:40 Rodrigo Vivi
2022-10-13 12:56 Tvrtko Ursulin
2022-10-06 10:18 Tvrtko Ursulin
2022-09-29 14:26 Tvrtko Ursulin
2022-08-11 21:03 Rodrigo Vivi
2022-08-04 17:33 Rodrigo Vivi
2022-08-05  8:46 ` Mauro Carvalho Chehab
2022-08-05 14:39   ` Rodrigo Vivi
2022-08-05 15:25     ` Mauro Carvalho Chehab
2022-08-05 20:39       ` Rodrigo Vivi
2022-05-24 13:59 Jani Nikula
2022-03-24  8:44 Tvrtko Ursulin
2022-03-17  7:47 Joonas Lahtinen
2022-03-10  7:58 Joonas Lahtinen
2022-01-20 10:13 Tvrtko Ursulin
2021-11-09 23:17 Rodrigo Vivi
2021-08-26  9:03 Jani Nikula
2021-07-07 15:09 Rodrigo Vivi
2021-06-29 18:54 Rodrigo Vivi
2021-06-30 10:05 ` Jani Nikula
2021-06-30 19:04   ` Rodrigo Vivi
2021-07-01  8:57     ` Jani Nikula
2021-07-01 19:30       ` Rodrigo Vivi
2021-02-25 14:43 Rodrigo Vivi
2021-02-18 22:46 Rodrigo Vivi
2020-12-18 15:04 Jani Nikula
2020-12-18 15:42 ` Daniel Vetter
2020-10-22 20:56 Rodrigo Vivi
2020-10-15 18:14 Rodrigo Vivi
2020-10-02 18:26 Rodrigo Vivi
2020-07-30 16:26 Joonas Lahtinen
2020-08-10  7:31 ` Dave Airlie
2020-08-12 12:49   ` Jani Nikula
2020-06-10  9:37 Joonas Lahtinen
2020-06-10 11:19 ` Joonas Lahtinen
2020-06-04 15:04 Joonas Lahtinen
2020-05-28 14:40 Joonas Lahtinen
2020-05-20 12:32 Joonas Lahtinen
2020-04-08 21:59 Rodrigo Vivi
2020-04-02 21:30 Rodrigo Vivi
2020-03-27  8:16 Rodrigo Vivi
2019-12-05  9:24 Joonas Lahtinen
2019-11-28 14:15 Joonas Lahtinen
2019-11-28 14:15 ` [Intel-gfx] " Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-22 15:55 ` [Intel-gfx] " Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-20 20:40 ` [Intel-gfx] " Joonas Lahtinen
2019-11-22 12:08 ` Joonas Lahtinen
2019-11-22 12:08   ` [Intel-gfx] " Joonas Lahtinen
2019-11-14  8:52 Joonas Lahtinen
2019-11-14  8:52 ` [Intel-gfx] " Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-11-07 14:50 ` [Intel-gfx] " Joonas Lahtinen

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=YeF5NQUzc4UKO465@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mripard@kernel.org \
    --cc=tvrtko.ursulin@linux.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;
as well as URLs for NNTP newsgroup(s).