From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Wentland, Harry" <Harry.Wentland@amd.com>,
"Michel Dänzer" <michel@daenzer.net>,
"Kazlauskas, Nicholas" <Nicholas.Kazlauskas@amd.com>,
"Li, Sun peng (Leo)" <Sunpeng.Li@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: amdgpu crashes on OOM
Date: Mon, 26 Oct 2020 10:50:55 -0400 [thread overview]
Message-ID: <1603723649.ang5tduo62.none@localhost> (raw)
In-Reply-To: <MN2PR12MB448824F6E08D1498206EFFE6F7190@MN2PR12MB4488.namprd12.prod.outlook.com>
Excerpts from Deucher, Alexander's message of October 26, 2020 10:34 am:
> It was using kvzalloc, but was accidently dropped when that code was refactored. I just sent a patch to fix it.
Ah, that explains why I wasn't seeing it before. I was only looking at
changes in amdgpu_dm_atomic_commit_tail, not dc_create_state.
Thanks,
Alex.
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Wentland, Harry" <Harry.Wentland@amd.com>,
"Michel Dänzer" <michel@daenzer.net>,
"Kazlauskas, Nicholas" <Nicholas.Kazlauskas@amd.com>,
"Li, Sun peng (Leo)" <Sunpeng.Li@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: amdgpu crashes on OOM
Date: Mon, 26 Oct 2020 10:50:55 -0400 [thread overview]
Message-ID: <1603723649.ang5tduo62.none@localhost> (raw)
In-Reply-To: <MN2PR12MB448824F6E08D1498206EFFE6F7190@MN2PR12MB4488.namprd12.prod.outlook.com>
Excerpts from Deucher, Alexander's message of October 26, 2020 10:34 am:
> It was using kvzalloc, but was accidently dropped when that code was refactored. I just sent a patch to fix it.
Ah, that explains why I wasn't seeing it before. I was only looking at
changes in amdgpu_dm_atomic_commit_tail, not dc_create_state.
Thanks,
Alex.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-10-26 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1603684905.h43s1t0y05.none.ref@localhost>
2020-10-26 4:29 ` amdgpu crashes on OOM Alex Xu (Hello71)
2020-10-26 4:29 ` Alex Xu (Hello71)
2020-10-26 11:03 ` Michel Dänzer
2020-10-26 11:03 ` Michel Dänzer
2020-10-26 14:34 ` Deucher, Alexander
2020-10-26 14:34 ` Deucher, Alexander
2020-10-26 14:50 ` Alex Xu (Hello71) [this message]
2020-10-26 14:50 ` Alex Xu (Hello71)
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=1603723649.ang5tduo62.none@localhost \
--to=alex_y_xu@yahoo.ca \
--cc=Alexander.Deucher@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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.