All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Olšák" <maraeo@gmail.com>
To: "Liu, Monk" <Monk.Liu@amd.com>
Cc: "Koenig, Christian" <Christian.Koenig@amd.com>,
	amd-gfx mailing list <amd-gfx@lists.freedesktop.org>
Subject: Re: drm/amdgpu: invalidate L2 before SDMA IBs (on gfx10)
Date: Fri, 1 May 2020 12:02:52 -0400	[thread overview]
Message-ID: <CAAxE2A4aB-9oxD7Wp_RTvbnbz79-vPP7myyvT6BR4MjTD6EYwg@mail.gmail.com> (raw)
In-Reply-To: <DM5PR12MB170826866E450B9772D1A9CC84AD0@DM5PR12MB1708.namprd12.prod.outlook.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 4594 bytes --]

I'll answer two questions asked:

1) SDMA doesn't need GCR at the end of IBs. It's because SDMA writes bypass
GL2 and at the same time they invalidate all cache lines they touch.

2)
> If we always insert a GL2C invalidate at every EOP of every IB from every
engine, why we need a GL2C invalidate before IB  execute ?

I just sent you a counterexample on a private thread that proves that
invalidation in RELEASE_MEM doesn't accomplish anything. The invalidation
flag is there because:
1) it was inherited from gfx9, which was inherited from gfx8, which was
inherited from gfx7, which doesn't have the WB flag, so INV has to be used
instead.
2) to hide bugs

Marek

On Wed, Apr 29, 2020 at 7:24 AM Liu, Monk <Monk.Liu@amd.com> wrote:

> >> Well from my understanding I think that a G2LC invalidation is still
> necessary before an IB executes.
>
> Agree, I think before an IB executes the only thing we need on GL2C is the
> invalidation, not the flush .
>
>
> >> The problem is that the memory of the IB could also be cached because
> of some activity of the GFX or Compute rings.
>
> If we always insert a GL2C invalidate at every EOP of every IB from every
> engine, why we need a GL2C invalidate before IB  execute ?
>
> _____________________________________
>
> Monk Liu|GPU Virtualization Team |AMD
>
> [image: sig-cloud-gpu]
>
>
>
> *From:* Koenig, Christian <Christian.Koenig@amd.com>
> *Sent:* Wednesday, April 29, 2020 5:38 PM
> *To:* Liu, Monk <Monk.Liu@amd.com>; Marek Olšák <maraeo@gmail.com>;
> amd-gfx mailing list <amd-gfx@lists.freedesktop.org>
> *Subject:* Re: drm/amdgpu: invalidate L2 before SDMA IBs (on gfx10)
>
>
>
> Well from my understanding I think that a G2LC invalidation is still
> necessary before an IB executes.
>
> The problem is that the memory of the IB could also be cached because of
> some activity of the GFX or Compute rings.
>
> Regards,
> Christian.
>
> Am 29.04.20 um 11:35 schrieb Liu, Monk:
>
> Here is the reason we should always insert a “sync mem” packet at the
> FENCE place of SDMA, not before IB emit.
>
>
>
> By always inserting “sync mem” in the FENCE place we can make sure:1
>
>    1. data is really flushed to system memory before CPU try to read it
>    2. all the G2LC is invalidated by “sync mem”, thus in the next round
>    SDMA IB, it won’t get staled data from G2LC cache
>
>
>
> by inserting “sync mem” in prior to IB could only achieve :  Avoid get
> staled data in g2lc during IB execution
>
>
>
> for GFX/COMPUTE ring since they have release_mem packet so it is
> inherently doing the G2LC flush and invalidate upon a fence signaled
>
>
>
> _____________________________________
>
> Monk Liu|GPU Virtualization Team |AMD
>
> [image: sig-cloud-gpu]
>
>
>
> *From:* Liu, Monk
> *Sent:* Wednesday, April 29, 2020 5:06 PM
> *To:* 'Marek Olšák' <maraeo@gmail.com> <maraeo@gmail.com>; amd-gfx
> mailing list <amd-gfx@lists.freedesktop.org>
> <amd-gfx@lists.freedesktop.org>; Koenig, Christian
> <Christian.Koenig@amd.com> <Christian.Koenig@amd.com>
> *Subject:* RE: drm/amdgpu: invalidate L2 before SDMA IBs (on gfx10)
>
>
>
> Hi @Koenig, Christian <Christian.Koenig@amd.com> & Marek
>
>
>
> I still have some concerns regarding Marek’s patch, correct me if I’m wrong
>
>
>
> See that Marek put a SDMA_OP_GCR_REQ before emitting IB, to make sure SDMA
> won’t get stale cache data during the IB execution.
>
>
>
> But that “SDMA_OP_GCR_REQ” only invalidate/flush the GFXHUB’s G2LC cache
> right ?  what if the memory is changed by MM or CPU (out side of GFXHUB) ?
>
>
>
> Can this “ SDMA_OP_GCR_REQ” force MMHUB or even CPU to flush their
> operation result from their cache to memory ??
>
>
>
> Besides, with my understanding the “EOP” of gfx ring is doing the thing of
> “invalidate/flush” L2 cache upon a fence signaled, so what we should do on
> SDMA5 is to insert this “SDMA_OP_GCR_REQ”
>
> Right before thee “emit_fence” of SDMA  (this is what windows KMD do)
>
>
>
> thanks
>
> _____________________________________
>
> Monk Liu|GPU Virtualization Team |AMD
>
> [image: sig-cloud-gpu]
>
>
>
> *From:* amd-gfx <amd-gfx-bounces@lists.freedesktop.org> *On Behalf Of *Marek
> Ol?ák
> *Sent:* Saturday, April 25, 2020 4:52 PM
> *To:* amd-gfx mailing list <amd-gfx@lists.freedesktop.org>
> *Subject:* drm/amdgpu: invalidate L2 before SDMA IBs (on gfx10)
>
>
>
> This should fix SDMA hangs on gfx10.
>
>
>
> Marek
>
>
>

[-- Attachment #1.1.2: Type: text/html, Size: 10059 bytes --]

[-- Attachment #1.2: image001.png --]
[-- Type: image/png, Size: 12243 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2020-05-01 16:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25  8:52 drm/amdgpu: invalidate L2 before SDMA IBs (on gfx10) Marek Olšák
2020-04-25 15:04 ` Christian König
2020-04-26  0:28   ` Marek Olšák
2020-04-26  8:52     ` Christian König
2020-04-27 13:01       ` Deucher, Alexander
2020-04-27 13:53         ` Marek Olšák
2020-04-25 16:28 ` Pierre-Eric Pelloux-Prayer
2020-04-29  9:06 ` Liu, Monk
2020-04-29  9:35   ` Liu, Monk
2020-04-29  9:37     ` Christian König
2020-04-29 11:24       ` Liu, Monk
2020-05-01 16:02         ` Marek Olšák [this message]
2020-04-29 12:17 Koenig, Christian

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=CAAxE2A4aB-9oxD7Wp_RTvbnbz79-vPP7myyvT6BR4MjTD6EYwg@mail.gmail.com \
    --to=maraeo@gmail.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Monk.Liu@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /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.