From: Matthew Wilcox <willy@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Christian Brauner <christian@brauner.io>,
Andrey Grodzovsky <andrey.grodzovsky@amd.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>,
Hawking Zhang <Hawking.Zhang@amd.com>,
Harry Pan <harry.pan@intel.com>,
linux-pm@vger.kernel.org
Subject: Re: ksys_sync_helper
Date: Tue, 1 Aug 2023 13:34:21 +0100 [thread overview]
Message-ID: <ZMj7zTwPw/qi/bNw@casper.infradead.org> (raw)
In-Reply-To: <ZMjnZhbKbNMmcUPN@infradead.org>
On Tue, Aug 01, 2023 at 04:07:18AM -0700, Christoph Hellwig wrote:
> On Mon, Jul 31, 2023 at 08:27:17PM +0200, Wysocki, Rafael J wrote:
> >
> > OK, I'll remember about this.
> >
> >
> > > With this
> > > and commit d5ea093eebf022e now we end up with a random driver (amdgpu)
> > > syncing all file systems for absolutely no good reason.
> >
> > Sorry about that.
> >
> > The problematic commit should still revert more or less cleanly, so please
> > do that if that's what you need.
>
> We'd still need to remove abuse in amdgpu first, though.
This would effectively revert d5ea093eebf0
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index dc0e5227119b..af04fece37d5 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@ -75,7 +75,6 @@
#include "amdgpu_fru_eeprom.h"
#include "amdgpu_reset.h"
-#include <linux/suspend.h>
#include <drm/task_barrier.h>
#include <linux/pm_runtime.h>
@@ -5225,17 +5224,6 @@ int amdgpu_device_gpu_recover(struct amdgpu_device *adev,
*/
need_emergency_restart = amdgpu_ras_need_emergency_restart(adev);
- /*
- * Flush RAM to disk so that after reboot
- * the user can read log and see why the system rebooted.
- */
- if (need_emergency_restart && amdgpu_ras_get_context(adev)->reboot) {
- DRM_WARN("Emergency reboot.");
-
- ksys_sync_helper();
- emergency_restart();
- }
-
dev_info(adev->dev, "GPU %s begin!\n",
need_emergency_restart ? "jobs stop":"reset");
next prev parent reply other threads:[~2023-08-01 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 7:20 ksys_sync_helper Christoph Hellwig
2023-07-31 18:27 ` ksys_sync_helper Wysocki, Rafael J
2023-08-01 11:07 ` ksys_sync_helper Christoph Hellwig
2023-08-01 12:34 ` Matthew Wilcox [this message]
2023-08-07 23:01 ` ksys_sync_helper Deucher, Alexander
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=ZMj7zTwPw/qi/bNw@casper.infradead.org \
--to=willy@infradead.org \
--cc=Hawking.Zhang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=andrey.grodzovsky@amd.com \
--cc=christian@brauner.io \
--cc=harry.pan@intel.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@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;
as well as URLs for NNTP newsgroup(s).