From: "Christian König" <christian.koenig@amd.com> To: Michal Kubecek <mkubecek@suse.cz>, Alex Deucher <alexdeucher@gmail.com> Cc: "Yang, Philip" <Philip.Yang@amd.com>, amd-gfx list <amd-gfx@lists.freedesktop.org>, Alex Deucher <alexander.deucher@amd.com>, Felix Kuehling <Felix.Kuehling@amd.com>, LKML <linux-kernel@vger.kernel.org> Subject: Re: (REGRESSION bisected) Re: amdgpu errors (VM fault / GPU fault detected) with 5.19 merge window snapshots Date: Mon, 6 Jun 2022 12:25:13 +0200 [thread overview] Message-ID: <a9d69525-04f0-5f75-b7a6-5a09199deb15@amd.com> (raw) In-Reply-To: <20220605220055.cshuzyveneu5a4hf@lion.mk-sys.cz> Am 06.06.22 um 00:00 schrieb Michal Kubecek: > [SNIP] >> This patch should help: >> https://patchwork.freedesktop.org/patch/488258/ > After ~48 hours with this patch, still no apparent issues. > > Tested-by: Michal Kubecek <mkubecek@suse.cz> Thanks, this could be optimized for gfx8 a bit if anybody is interested in a typing exercise. E.g. we only need the tlb flush when "start" or "end" are not 8 entries aligned on gfx8. I don't have time to test this, but should be trivial to implement. Christian. > > Michal
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com> To: Michal Kubecek <mkubecek@suse.cz>, Alex Deucher <alexdeucher@gmail.com> Cc: Alex Deucher <alexander.deucher@amd.com>, "Yang, Philip" <Philip.Yang@amd.com>, Felix Kuehling <Felix.Kuehling@amd.com>, LKML <linux-kernel@vger.kernel.org>, amd-gfx list <amd-gfx@lists.freedesktop.org> Subject: Re: (REGRESSION bisected) Re: amdgpu errors (VM fault / GPU fault detected) with 5.19 merge window snapshots Date: Mon, 6 Jun 2022 12:25:13 +0200 [thread overview] Message-ID: <a9d69525-04f0-5f75-b7a6-5a09199deb15@amd.com> (raw) In-Reply-To: <20220605220055.cshuzyveneu5a4hf@lion.mk-sys.cz> Am 06.06.22 um 00:00 schrieb Michal Kubecek: > [SNIP] >> This patch should help: >> https://patchwork.freedesktop.org/patch/488258/ > After ~48 hours with this patch, still no apparent issues. > > Tested-by: Michal Kubecek <mkubecek@suse.cz> Thanks, this could be optimized for gfx8 a bit if anybody is interested in a typing exercise. E.g. we only need the tlb flush when "start" or "end" are not 8 entries aligned on gfx8. I don't have time to test this, but should be trivial to implement. Christian. > > Michal
next prev parent reply other threads:[~2022-06-06 10:25 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-27 9:00 amdgpu errors (VM fault / GPU fault detected) with 5.19 merge window snapshots Michal Kubecek 2022-05-27 12:44 ` (REGRESSION bisected) " Michal Kubecek 2022-05-27 12:44 ` Michal Kubecek 2022-06-01 14:55 ` Alex Deucher 2022-06-01 14:55 ` Alex Deucher 2022-06-01 14:59 ` Christian König 2022-06-02 13:58 ` Alex Deucher 2022-06-02 13:58 ` Alex Deucher 2022-06-02 14:22 ` Michal Kubecek 2022-06-02 14:22 ` Michal Kubecek 2022-06-03 15:49 ` Alex Deucher 2022-06-03 15:49 ` Alex Deucher 2022-06-03 17:23 ` Michal Kubecek 2022-06-03 17:23 ` Michal Kubecek 2022-06-05 22:00 ` Michal Kubecek 2022-06-05 22:00 ` Michal Kubecek 2022-06-06 10:25 ` Christian König [this message] 2022-06-06 10:25 ` Christian König
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=a9d69525-04f0-5f75-b7a6-5a09199deb15@amd.com \ --to=christian.koenig@amd.com \ --cc=Felix.Kuehling@amd.com \ --cc=Philip.Yang@amd.com \ --cc=alexander.deucher@amd.com \ --cc=alexdeucher@gmail.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mkubecek@suse.cz \ /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: linkBe 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.