From: "Christian König" <christian.koenig@amd.com>
To: "Lazar, Lijo" <lijo.lazar@amd.com>,
"Somalapuram, Amaranath" <asomalap@amd.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Somalapuram Amaranath" <Amaranath.Somalapuram@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, shashank.sharma@amd.com
Subject: Re: [PATCH v6 1/2] drm/amdgpu: add debugfs for reset registers list
Date: Thu, 17 Feb 2022 11:43:33 +0100 [thread overview]
Message-ID: <ff3633eb-2ba1-567a-722d-cba44b3a6935@amd.com> (raw)
In-Reply-To: <b8cb6a88-76ed-8326-5007-7eb066d1d692@amd.com>
Am 17.02.22 um 11:09 schrieb Lazar, Lijo:
>
>
> On 2/17/2022 3:34 PM, Christian König wrote:
>>
>> [SNIP]
>
> Is this passed to core memory management by a component like drm or ttm?
The dependency comes from multiple directions. But yes, both DRM core as
well as TTM have that restriction.
Additional to that we have dependencies through userptr etc...
>
> I thought reset was mainly internal/contained to device level as we
> reset for multiple reasons and system as whole shouldn't be affected.
No, device reset is vital for core memory management. Otherwise the
whole memory management concept wouldn't work.
Regards,
Christian.
>
> Thanks,
> Lijo
>
>> Regards,
>> Christian.
next prev parent reply other threads:[~2022-02-17 10:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 9:49 [PATCH v6 1/2] drm/amdgpu: add debugfs for reset registers list Somalapuram Amaranath
2022-02-16 9:49 ` [PATCH v6 2/2] drm/amdgpu: add reset register dump trace on GPU reset Somalapuram Amaranath
2022-02-16 10:11 ` [PATCH v6 1/2] drm/amdgpu: add debugfs for reset registers list Christian König
2022-02-16 13:11 ` Somalapuram, Amaranath
2022-02-16 14:56 ` Christian König
2022-02-17 7:54 ` Somalapuram, Amaranath
2022-02-17 8:00 ` Christian König
2022-02-17 9:44 ` Lazar, Lijo
2022-02-17 9:48 ` Christian König
2022-02-17 10:01 ` Lazar, Lijo
2022-02-17 10:04 ` Christian König
2022-02-17 10:09 ` Lazar, Lijo
2022-02-17 10:43 ` Christian König [this message]
2022-02-16 10:15 ` Lazar, Lijo
2022-02-16 10:34 ` Somalapuram, Amaranath
2022-02-16 10:43 ` Lazar, Lijo
2022-02-16 11:00 ` Christian König
2022-02-16 11:09 ` Somalapuram, Amaranath
2022-02-16 13:17 ` Lazar, Lijo
2022-02-16 13:55 ` Somalapuram, Amaranath
2022-02-16 14:53 ` 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=ff3633eb-2ba1-567a-722d-cba44b3a6935@amd.com \
--to=christian.koenig@amd.com \
--cc=Amaranath.Somalapuram@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=asomalap@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=lijo.lazar@amd.com \
--cc=shashank.sharma@amd.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