intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Andi Shyti <andi.shyti@intel.com>,
	Dave Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PULL] drm-intel-next-fixes
Date: Fri, 5 Aug 2022 17:25:43 +0200	[thread overview]
Message-ID: <20220805172543.1cdcd58a@maurocar-mobl2> (raw)
In-Reply-To: <Yu0rsGnxcFmvzSPi@intel.com>

On Fri, 5 Aug 2022 10:39:44 -0400
Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:

> On Fri, Aug 05, 2022 at 10:46:57AM +0200, Mauro Carvalho Chehab wrote:
> > Hi Rodrigo,
> > 
> > On Thu, 4 Aug 2022 13:33:06 -0400
> > Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> >   
> > > Hi Dave and Daniel,
> > > 
> > > Here goes drm-intel-next-fixes-2022-08-04:
> > > 
> > > - disable pci resize on 32-bit systems (Nirmoy)
> > > - don't leak the ccs state (Matt)
> > > - TLB invalidation fixes (Chris)
> > > 
> > > Thanks,
> > > Rodrigo.
> > > 
> > > The following changes since commit 2bc7ea71a73747a77e7f83bc085b0d2393235410:
> > > 
> > >   Merge tag 'topic/nouveau-misc-2022-07-27' of git://anongit.freedesktop.org/drm/drm into drm-next (2022-07-27 11:34:07 +1000)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2022-08-04
> > > 
> > > for you to fetch changes up to e57b9369e0c6f60155027e120fafd4b57e385b71:
> > > 
> > >   drm/i915/gt: Batch TLB invalidations (2022-08-01 09:48:06 -0400)
> > > 
> > > ----------------------------------------------------------------
> > > - disable pci resize on 32-bit systems (Nirmoy)
> > > - don't leak the ccs state (Matt)
> > > - TLB invalidation fixes (Chris)
> > > 
> > > ----------------------------------------------------------------
> > > Chris Wilson (4):
> > >       drm/i915/gt: Ignore TLB invalidations on idle engines
> > >       drm/i915/gt: Invalidate TLB of the OA unit at TLB invalidations
> > >       drm/i915/gt: Skip TLB invalidations once wedged  
> >   
> > >       drm/i915/gt: Batch TLB invalidations  
> > This patch actually adds a regression due to a silly mistake. 
> > The fix is here:
> > 
> > 	https://patchwork.freedesktop.org/patch/496249/?series=106805&rev=4
> >  
> 
> Thank you for the heads up.
> 
> Since that patch is not merged yet, what are your recommendations here?
> Should I remove this from drm-intel-next-fixes now?

Those patches are OK to merge:

       drm/i915/gt: Ignore TLB invalidations on idle engines
       drm/i915/gt: Invalidate TLB of the OA unit at TLB invalidations
       drm/i915/gt: Skip TLB invalidations once wedged  

And helps reduce performance regressions due to TLB cache invalidation.
So, I would keep them.

With regards to the 4th patch, please don't merge:

	drm/i915/gt: Batch TLB invalidations

or merge it together with:

	drm/i915: pass a pointer for tlb seqno at vma_invalidate_tlb()

> Which regression is worst?

The regression caused by the batch patch is a lot worse, as it
effectively disables TLB cache invalidation. The fix was meant to
be merged at the patch, but somehow between several rebases and 3
machines involved on tests, internal development and upstream, the
branch actually sent upstream was not the right one. It got only
noticed after reviewing a newer patch. Yeah, that sucks.

> Also dim has trouble with fixes for fixes in the same round.
> Please ping me when you get that patch merged so I can pull that.

OK.

Regards,
Mauro

  reply	other threads:[~2022-08-05 15:25 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 17:33 [Intel-gfx] [PULL] drm-intel-next-fixes 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 [this message]
2022-08-05 20:39       ` Rodrigo Vivi
  -- 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-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
2022-01-13  9:33 Tvrtko Ursulin
2022-01-14 13:23 ` Daniel Vetter
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=20220805172543.1cdcd58a@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=andi.shyti@intel.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=rodrigo.vivi@intel.com \
    --cc=tzimmermann@suse.de \
    /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).