From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Auld, Matthew" <matthew.auld@intel.com>
Subject: Re: [Intel-xe] [PATCH v3 0/5] Try to handle TLB invalidations from CT fast-path
Date: Tue, 4 Jul 2023 18:42:20 +0000 [thread overview]
Message-ID: <9b85e5dab2ef877067ec807131a8323e975e573d.camel@intel.com> (raw)
In-Reply-To: <d899032fae79b3e4a6f1827d0a18746ecb2b5d21.camel@intel.com>
On Tue, 2023-07-04 at 18:19 +0000, Souza, Jose wrote:
> On Tue, 2023-07-04 at 14:45 +0100, Matthew Auld wrote:
> > In various test cases and workloads that put the system under a heavy load, we
> > can sometimes see errors with missed TLB invalidations. If we handle the TLB
> > completions directly from IRQ we can see a big improvement.
> >
>
> The __g2h_release_space() warnings are fixed in this version and so far it is stable.
Ops. Still able to get the warning on DG2/ACM: https://pastebin.com/raw/vcs6wkp9
The previous tests were on TGL.
>
> Tested-by: José Roberto de Souza <jose.souza@intel.com>
prev parent reply other threads:[~2023-07-04 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 13:45 [Intel-xe] [PATCH v3 0/5] Try to handle TLB invalidations from CT fast-path Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 1/5] drm/xe: hold mem_access.ref for " Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 2/5] drm/xe/ct: serialise fast_lock during CT disable Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 3/5] drm/xe/gt: tweak placement for signalling TLB fences after GT reset Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 4/5] drm/xe/tlb: also update seqno_recv during reset Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 5/5] drm/xe: handle TLB invalidations from CT fast-path Matthew Auld
2023-07-04 13:48 ` [Intel-xe] ✓ CI.Patch_applied: success for Try to " Patchwork
2023-07-04 13:49 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-04 13:50 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-04 13:54 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-04 13:54 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-04 13:55 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-04 14:42 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-07-04 18:19 ` [Intel-xe] [PATCH v3 0/5] " Souza, Jose
2023-07-04 18:42 ` Souza, Jose [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=9b85e5dab2ef877067ec807131a8323e975e573d.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@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