From: "Chen, Jiansong (Simon)" <Jiansong.Chen@amd.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Zhou1, Tao" <Tao.Zhou1@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Zhang, Hawking" <Hawking.Zhang@amd.com>
Subject: RE: [PATCH] drm/amdgpu: enable gpu recovery for navy_flounder
Date: Mon, 11 Jan 2021 12:26:07 +0000 [thread overview]
Message-ID: <BY5PR12MB4885C09A5D21C96E7A175753EAAB0@BY5PR12MB4885.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ea359d1f-169a-7b93-94aa-8bcaf38cef39@molgen.mpg.de>
[AMD Official Use Only - Internal Distribution Only]
Hi Paul,
We just enable gpu recovery when the feature is stable enough for navy_flounder. And you can use debugfs interface to perform
a manual GPU reset. Here is more detail https://github.com/RadeonOpenCompute/ROCm/issues/616. Thanks!
Regards,
Jiansong
-----Original Message-----
From: Paul Menzel <pmenzel@molgen.mpg.de>
Sent: Monday, January 11, 2021 7:58 PM
To: Chen, Jiansong (Simon) <Jiansong.Chen@amd.com>
Cc: Zhou1, Tao <Tao.Zhou1@amd.com>; Zhang, Hawking <Hawking.Zhang@amd.com>; amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: enable gpu recovery for navy_flounder
Dear Jiansong,
Am 11.01.21 um 10:49 schrieb Jiansong Chen:
> Enable gpu recovery for navy_flounder by default to trigger reset once
> needed.
[…]
Why was it disabled before? Were some bugs fixed, that it works now?
How did you test this? Is there a command to “crash“ the GPU, so it can be recovered?
Please extend the commit message accordingly.
Kind regards,
Paul
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-01-11 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 9:49 [PATCH] drm/amdgpu: enable gpu recovery for navy_flounder Jiansong Chen
2021-01-11 10:15 ` Zhou1, Tao
2021-01-11 11:57 ` Paul Menzel
2021-01-11 12:26 ` Chen, Jiansong (Simon) [this message]
2021-01-12 9:20 ` Paul Menzel
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=BY5PR12MB4885C09A5D21C96E7A175753EAAB0@BY5PR12MB4885.namprd12.prod.outlook.com \
--to=jiansong.chen@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=Tao.Zhou1@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=pmenzel@molgen.mpg.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 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.