Re: [Intel-gfx] [PATCH 14/14] Doc/gpu/rfc/i915: i915 DG2 uAPI

2021-10-11 Thread Tang, CQ
> -Original Message- > From: C, Ramalingam > Sent: Monday, October 11, 2021 9:12 AM > To: dri-devel ; intel-gfx g...@lists.freedesktop.org> > Cc: Daniel Vetter ; Auld, Matthew > ; Tang, CQ ; Hellstrom, > Thomas ; C, Ramalingam > ; Daniel Vetter > Subj

Re: [Intel-gfx] [PATCH] drm/i915: Perform execbuffer object locking as a separate step

2021-06-17 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Thomas Hellström > Sent: Tuesday, June 15, 2021 4:36 AM > To: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org > Cc: Thomas Hellström ; Auld, Matthew > > Subject: [Intel-gfx] [PATCH] drm/i915: Perform execbuffer

Re: [Intel-gfx] [PATCH v4 14/17] drm/i915/pxp: User interface for Protected buffer

2021-05-25 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Daniele Ceraolo Spurio > Sent: Monday, May 24, 2021 10:48 PM > To: intel-gfx@lists.freedesktop.org > Cc: Vetter, Daniel ; Huang Sean Z > ; dri-de...@lists.freedesktop.org; Chris Wilson > ; Kondapally Kalyan > ; Bommu, Krishnaiah >

Re: [Intel-gfx] [PATCH v2 4/7] drm/i915/gtt/dgfx: place the PD in LMEM

2021-04-27 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Matthew Auld > Sent: Tuesday, April 27, 2021 1:54 AM > To: intel-gfx@lists.freedesktop.org > Cc: dri-de...@lists.freedesktop.org > Subject: [Intel-gfx] [PATCH v2 4/7] drm/i915/gtt/dgfx: place the PD in LMEM > > It's a requirement

Re: [Intel-gfx] [PATCH v5] drm/i915/gt: Ratelimit heartbeat completion probing

2021-02-11 Thread Tang, CQ
Do you have the patch that can apply to DII? --CQ > -Original Message- > From: Chris Wilson > Sent: Thursday, February 11, 2021 3:14 PM > To: intel-gfx@lists.freedesktop.org > Cc: Chris Wilson ; Tang, CQ > Subject: [PATCH v5] drm/i915/gt: Ratelimit heartbeat

Re: [Intel-gfx] [PATCH] drm/i915/gt: Ratelimit heartbeat completion probing

2021-02-10 Thread Tang, CQ
. What is the problem? Do you have the patch for DII for me to try? --CQ > -Original Message- > From: Chris Wilson > Sent: Friday, February 5, 2021 6:32 AM > To: intel-gfx@lists.freedesktop.org > Cc: Chris Wilson ; Tang, CQ > Subject: [PATCH] drm/i915/gt: Ratelimit he

Re: [Intel-gfx] [PATCH v3 3/3] drm/i915/gtt/dg1: add PTE_LM plumbing for GGTT

2021-02-03 Thread Tang, CQ
> -Original Message- > From: Matthew Auld > Sent: Wednesday, February 3, 2021 9:03 AM > To: Tang, CQ > Cc: Auld, Matthew ; intel- > g...@lists.freedesktop.org; Chris Wilson > Subject: Re: [Intel-gfx] [PATCH v3 3/3] drm/i915/gtt/dg1: add PTE_LM > plumbing for

Re: [Intel-gfx] [PATCH v3 3/3] drm/i915/gtt/dg1: add PTE_LM plumbing for GGTT

2021-02-03 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Matthew Auld > Sent: Wednesday, February 3, 2021 7:24 AM > To: intel-gfx@lists.freedesktop.org > Cc: Chris Wilson > Subject: [Intel-gfx] [PATCH v3 3/3] drm/i915/gtt/dg1: add PTE_LM plumbing > for GGTT > > For the PTEs we get an LM

Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced vma check and vma insert

2020-12-16 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Wednesday, December 16, 2020 12:44 PM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Cc: stable@ > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced > vma check and vma insert > >

Re: [Intel-gfx] [PATCH i-g-t] i915/gem_softpin: Check the last 32b page is excluded

2020-12-16 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Wednesday, December 16, 2020 12:53 PM > To: intel-gfx@lists.freedesktop.org > Cc: Chris Wilson ; Tang, CQ > Subject: [PATCH i-g-t] i915/gem_softpin: Check the last 32b page is excluded > > In order to prevent i

Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced vma check and vma insert

2020-12-16 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Wednesday, December 16, 2020 12:43 AM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Cc: stable@ > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced > vma check and vma insert > >

Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced vma check and vma insert

2020-12-15 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Tuesday, December 15, 2020 2:02 PM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Cc: stable@ > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced > vma check and vma insert > > Q

Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced vma check and vma insert

2020-12-15 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Tuesday, December 15, 2020 2:02 PM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Cc: stable@ > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced > vma check and vma insert > > Q

Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced vma check and vma insert

2020-12-15 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Tuesday, December 15, 2020 12:31 PM > To: intel-gfx@lists.freedesktop.org > Cc: Chris Wilson ; Tang, CQ ; > sta...@vger.kernel.org > Subject: [PATCH] drm/i915: Fix mismatch between misplaced vma check and &

Re: [Intel-gfx] [PATCH i-g-t 1/2] i915/gem_exec_params: Assert a 4G object does _not_ fit without 48b

2020-12-15 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Tuesday, December 15, 2020 1:07 PM > To: intel-gfx@lists.freedesktop.org > Cc: igt-...@lists.freedesktop.org; Chris Wilson ; > Tang, CQ > Subject: [PATCH i-g-t 1/2] i915/gem_exec_params: Assert a 4G object does &g

Re: [Intel-gfx] [PATCH] drm/i915/gt: Onion unwind for scratch page allocation failure

2020-10-20 Thread Tang, CQ
Reviewed-by: CQ Tang --CQ > -Original Message- > From: Intel-gfx On Behalf Of > Chris Wilson > Sent: Monday, October 19, 2020 1:35 AM > To: intel-gfx@lists.freedesktop.org > Cc: Auld, Matthew ; Chris Wilson wilson.co.uk> > Subject: [Intel-gfx] [PATCH] d

Re: [Intel-gfx] [PATCH] drm/i915/gt: Onion unwind for scratch page allocation failure

2020-10-19 Thread Tang, CQ
I fixed this problem partially (not gen6 code) with patch: http://intel-gfx-pw.fi.intel.com/series/5911/ Should I continue to fix on internal? --CQ > -Original Message- > From: Intel-gfx On Behalf Of > Chris Wilson > Sent: Monday, October 19, 2020 1:35 AM > To:

Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue high priority

2020-10-15 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Thursday, October 15, 2020 1:33 PM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue > high priority > > > We can also prune the f

Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue high priority

2020-10-15 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Thursday, October 15, 2020 8:07 AM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue > high priority > > Quoting Tang,

Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue high priority

2020-10-13 Thread Tang, CQ
el-gfx On Behalf Of > Tang, CQ > Sent: Tuesday, October 13, 2020 9:41 AM > To: Chris Wilson ; intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue > high priority > > > > > -Original Message- >

Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue high priority

2020-10-13 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Tuesday, October 13, 2020 9:25 AM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue > high priority > > Quoting Tang, CQ (2020-1

Re: [Intel-gfx] [PATCH] drm/i915: Make the GEM reclaim workqueue high priority

2020-10-13 Thread Tang, CQ
nt', is the objects taken by last worker invocation to free. --CQ > -Original Message- > From: Chris Wilson > Sent: Tuesday, October 13, 2020 3:33 AM > To: intel-gfx@lists.freedesktop.org > Cc: Chris Wilson ; Tang, CQ > Subject: [PATCH] drm/i915: Make the GEM reclaim

Re: [Intel-gfx] [RFC 53/60] drm/i915: Create stolen memory region from local memory

2020-08-07 Thread Tang, CQ
> -Original Message- > From: Joonas Lahtinen > Sent: Friday, August 7, 2020 2:39 AM > To: Tang, CQ ; Dave Airlie > Cc: Auld, Matthew ; Intel Graphics Development > ; Abdiel Janulgue > ; Wilson, Chris P > ; Balestrieri, Francesco > ; Vishwanathapura, Niranja

Re: [Intel-gfx] [PATCH 1/3] drm: Restore driver.preclose() for all to use

2020-07-29 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Tuesday, July 28, 2020 9:28 AM > To: Daniel Vetter ; Dave Airlie > Cc: intel-gfx ; stable > ; Gustavo Padovan > ; Tang, CQ ; dri- > devel ; Vetter, Daniel > > Subject: Re: [PATCH 1/3] drm: Restore dr

Re: [Intel-gfx] [PATCH 1/3] drm: Restore driver.preclose() for all to use

2020-07-27 Thread Tang, CQ
> -Original Message- > From: Daniel Vetter > Sent: Monday, July 27, 2020 12:33 PM > To: Chris Wilson ; Dave Airlie > Cc: intel-gfx ; stable > ; Gustavo Padovan > ; Tang, CQ ; dri- > devel ; Vetter, Daniel > > Subject: Re: [PATCH 1/3] drm: Restore dr

Re: [Intel-gfx] [PATCH 2/3] drm/i915/gem: Move context decoupling from postclose to preclose

2020-07-23 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Thursday, July 23, 2020 10:21 AM > To: intel-gfx@lists.freedesktop.org > Cc: dri-de...@lists.freedesktop.org; Chris Wilson ; > Tang, CQ ; Vetter, Daniel ; > sta...@vger.kernel.org > Subject: [PATCH 2/3] dr

Re: [Intel-gfx] [RFC 53/60] drm/i915: Create stolen memory region from local memory

2020-07-14 Thread Tang, CQ
> -Original Message- > From: Auld, Matthew > Sent: Tuesday, July 14, 2020 8:02 AM > To: Dave Airlie > Cc: Intel Graphics Development ; Tang, CQ > ; Joonas Lahtinen ; > Abdiel Janulgue ; Wilson, Chris P > ; Balestrieri, Francesco > ; Vishwanathapura, Niranja

Re: [Intel-gfx] [PATCH 1/3] drm/i915: make stolen more region centric

2020-01-14 Thread Tang, CQ
Reviewed-by: CQ Tang > -Original Message- > From: Auld, Matthew > Sent: Friday, January 3, 2020 12:00 PM > To: intel-gfx@lists.freedesktop.org > Cc: Tang, CQ ; Chris Wilson > Subject: [PATCH 1/3] drm/i915: make stolen more region centric > > From: CQ Tang >

Re: [Intel-gfx] [PATCH 1/3] drm/i915: make stolen more region centric

2020-01-14 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Friday, January 3, 2020 12:29 PM > To: Auld, Matthew ; intel- > g...@lists.freedesktop.org > Cc: Tang, CQ > Subject: Re: [PATCH 1/3] drm/i915: make stolen more region centric > > Quoting Matthew Auld (2020-0

Re: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers

2019-11-25 Thread Tang, CQ
Chris, I applied your patches and tested on DG1 hardware. This new code works well, except there are still two issues to this test (gem_ctx_isloation.c) 1. the test loops over all possible engines (..ccs0, ccs1, ccs2,). the legacy interface is used to check if an engine is

Re: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers

2019-11-21 Thread Tang, CQ
> -Original Message- > From: Chris Wilson > Sent: Thursday, November 21, 2019 3:45 PM > To: Tang, CQ ; intel-gfx@lists.freedesktop.org > Cc: igt-...@lists.freedesktop.org > Subject: RE: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check > engine relative r

Re: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers

2019-11-21 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Chris Wilson > Sent: Wednesday, November 13, 2019 4:53 AM > To: intel-gfx@lists.freedesktop.org > Cc: igt-...@lists.freedesktop.org > Subject: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine > relative registers >

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Switch obj->mm.lock lockdep annotations on its head

2019-11-07 Thread Tang, CQ
> --- a/drivers/gpu/drm/i915/gem/i915_gem_object.c > +++ b/drivers/gpu/drm/i915/gem/i915_gem_object.c > @@ -22,6 +22,8 @@ > * > */ > > +#include > + > #include "display/intel_frontbuffer.h" > #include "gt/intel_gt.h" > #include "i915_drv.h" > @@ -52,6 +54,14 @@ void

Re: [Intel-gfx] [PATCH v4 1/2] drm/i915: lookup for mem_region of a mem_type

2019-11-06 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Ramalingam C > Sent: Wednesday, November 6, 2019 8:08 AM > To: intel-gfx ; Chris Wilson wilson.co.uk> > Cc: Auld, Matthew > Subject: [Intel-gfx] [PATCH v4 1/2] drm/i915: lookup for mem_region of a > mem_type > > Lookup function to

Re: [Intel-gfx] [PATCH] drm/i915: Switch obj->mm.lock lockdep annotations on its head

2019-11-05 Thread Tang, CQ
> -Original Message- > From: Daniel Vetter > Sent: Tuesday, November 5, 2019 2:02 AM > To: Intel Graphics Development > Cc: Daniel Vetter ; Auld, Matthew > ; Chris Wilson ; Tang, > CQ ; Ursulin, Tvrtko ; Joonas > Lahtinen ; Vetter, Daniel > > Subject

Re: [Intel-gfx] [PATCH v2 13/22] drm/i915: treat stolen as a region

2019-10-03 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Matthew Auld > Sent: Thursday, October 3, 2019 12:25 PM > To: intel-gfx@lists.freedesktop.org > Subject: [Intel-gfx] [PATCH v2 13/22] drm/i915: treat stolen as a region > > Convert stolen memory over to a region object. Still leaves

Re: [Intel-gfx] [PATCH v2 19/22] drm/i915: don't allocate the ring in stolen if we lack aperture

2019-10-03 Thread Tang, CQ
> -Original Message- > From: Intel-gfx On Behalf Of > Matthew Auld > Sent: Thursday, October 3, 2019 12:25 PM > To: intel-gfx@lists.freedesktop.org > Subject: [Intel-gfx] [PATCH v2 19/22] drm/i915: don't allocate the ring in > stolen if we lack aperture > > Since we have no way access

Re: [Intel-gfx] [PATCH] drm/i915: Switch obj->mm.lock lockdep annotations on its head

2019-08-22 Thread Tang, CQ
> -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] > Sent: Thursday, August 22, 2019 7:50 AM > To: Intel Graphics Development > Cc: Daniel Vetter ; Chris Wilson wilson.co.uk>; Tang, CQ ; Ursulin, Tvrtko > ; Joonas Lahtinen > ; Vetter, D

Re: [Intel-gfx] [PATCH] drm/i915: Switch obj->mm.lock lockdep annotations on its head

2019-08-16 Thread Tang, CQ
> -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] > Sent: Friday, August 16, 2019 3:08 PM > To: Tang, CQ > Cc: Intel Graphics Development ; Chris > Wilson ; Ursulin, Tvrtko > ; Joonas Lahtinen > ; Vetter, Daniel > Subject: Re: [

Re: [Intel-gfx] [PATCH] drm/i915: Switch obj->mm.lock lockdep annotations on its head

2019-08-16 Thread Tang, CQ
> -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] > Sent: Friday, August 16, 2019 3:03 PM > To: Chris Wilson > Cc: Intel Graphics Development ; Tang, CQ > ; Ursulin, Tvrtko ; Joonas > Lahtinen ; Vetter, Daniel > > Subject: Re: [

Re: [Intel-gfx] [PATCH] drm/i915: Switch obj->mm.lock lockdep annotations on its head

2019-08-16 Thread Tang, CQ
> -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] > Sent: Friday, August 16, 2019 11:24 AM > To: Intel Graphics Development > Cc: Daniel Vetter ; Chris Wilson wilson.co.uk>; Tang, CQ ; Ursulin, Tvrtko > ; Joonas Lahtinen > ; Vetter, D

Re: [Intel-gfx] [PATCH] RFC: drm/i915: Switch obj->mm.lock lockdep annotations on its head

2019-08-15 Thread Tang, CQ
> -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf > Of Daniel Vetter > Sent: Wednesday, August 14, 2019 12:25 PM > To: Intel Graphics Development > Cc: Daniel Vetter ; Vetter, Daniel > > Subject: [Intel-gfx] [PATCH] RFC: drm/i915: Switch

Re: [Intel-gfx] [PATCH v2 03/37] drm/i915/region: support basic eviction

2019-08-15 Thread Tang, CQ
> -Original Message- > From: Daniel Vetter [mailto:dan...@ffwll.ch] > Sent: Thursday, August 15, 2019 9:21 AM > To: Tang, CQ > Cc: Matthew Auld ; Intel Graphics > Development ; Auld, Matthew > > Subject: Re: [Intel-gfx] [PATCH v2 03/37] drm/i915/region:

Re: [Intel-gfx] [PATCH v2 03/37] drm/i915/region: support basic eviction

2019-08-15 Thread Tang, CQ
> -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf > Of Daniel Vetter > Sent: Thursday, August 15, 2019 7:27 AM > To: Matthew Auld > Cc: Intel Graphics Development ; Auld, > Matthew > Subject: Re: [Intel-gfx] [PATCH v2 03/37]

Re: [Intel-gfx] [PATCH v3 03/37] drm/i915/region: support basic eviction

2019-08-10 Thread Tang, CQ
> -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf > Of Chris Wilson > Sent: Saturday, August 10, 2019 3:19 AM > To: Auld, Matthew ; intel- > g...@lists.freedesktop.org > Cc: dri-de...@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH

Re: [Intel-gfx] [PATCH 3/3] drm/i915/blt: bump the size restriction

2019-08-09 Thread Tang, CQ
> -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf > Of Tang, CQ > Sent: Friday, August 9, 2019 3:21 PM > To: Chris Wilson ; Auld, Matthew > ; intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i9

Re: [Intel-gfx] [PATCH 3/3] drm/i915/blt: bump the size restriction

2019-08-09 Thread Tang, CQ
> -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf > Of Chris Wilson > Sent: Friday, August 9, 2019 2:18 PM > To: Auld, Matthew ; intel- > g...@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915/blt: bump the size