From: Oded Gabbay <oded.gabbay@amd.com>
To: "Christian König" <deathsimple@vodafone.de>,
dri-devel@lists.freedesktop.org
Cc: <linux-kernel@vger.kernel.org>, <Alexander.Deucher@amd.com>
Subject: Re: [PATCH 1/3] amdkfd: Don't clear *kfd2kgd on kfd_module_init
Date: Sun, 21 Dec 2014 13:34:36 +0200 [thread overview]
Message-ID: <5496B04C.50502@amd.com> (raw)
In-Reply-To: <5496AEAD.3090003@vodafone.de>
On 12/21/2014 01:27 PM, Christian König wrote:
> Am 20.12.2014 um 21:46 schrieb Oded Gabbay:
>> When amdkfd and radeon are compiled inside the kernel image (not as modules),
>> radeon will load before amdkfd and will set *kfd2kgd to its interface
>> structure. Therefore, we must not set *kfd2kgd to NULL when amdkfd is loaded
>> because it will override radeon's initialization and cause kernel BUG.
>>
>> Signed-off-by: Oded Gabbay <oded.gabbay@amd.com>
>
> You should probably rather fix the dependency between the two modules to get an
> determined load order instead of doing such nasty workarounds.
>
> Christian.
The problem is that when modules are compiled inside the kernel, there is NO
determined load order and there is no mechanism to enforce that. If there is/was
such a mechanism, I would of course prefer to use it.
Actually, I don't understand why the kernel doesn't enforce the order according
to the use of exported symbols, like it does with modules.
There will always be dependencies between kgd (radeon) and amdkfd and between
amdkfd and amd_iommu_v2. I don't think I can eliminate those dependencies, not
without a very complex solution. And the fact that this complex solution occurs
only in a very specific use case (all modules compiled in), makes me less
inclined to do that.
So I don't see it as a "nasty workaround". I would call it just a "workaround"
for a specific use case, which should be solved by a generic solution to the
kernel enforcing load orders.
Oded
>
>> ---
>> drivers/gpu/drm/amd/amdkfd/kfd_module.c | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_module.c
>> b/drivers/gpu/drm/amd/amdkfd/kfd_module.c
>> index 95d5af1..236562f 100644
>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_module.c
>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_module.c
>> @@ -34,7 +34,7 @@
>> #define KFD_DRIVER_MINOR 7
>> #define KFD_DRIVER_PATCHLEVEL 0
>> -const struct kfd2kgd_calls *kfd2kgd;
>> +const struct kfd2kgd_calls *kfd2kgd = NULL;
>> static const struct kgd2kfd_calls kgd2kfd = {
>> .exit = kgd2kfd_exit,
>> .probe = kgd2kfd_probe,
>> @@ -84,14 +84,13 @@ EXPORT_SYMBOL(kgd2kfd_init);
>> void kgd2kfd_exit(void)
>> {
>> + kfd2kgd = NULL;
>> }
>> static int __init kfd_module_init(void)
>> {
>> int err;
>> - kfd2kgd = NULL;
>> -
>> /* Verify module parameters */
>> if ((sched_policy < KFD_SCHED_POLICY_HWS) ||
>> (sched_policy > KFD_SCHED_POLICY_NO_HWS)) {
>
next prev parent reply other threads:[~2014-12-21 11:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 20:46 [PATCH 0/3] Use workqueue for device init in amdkfd Oded Gabbay
2014-12-20 20:46 ` [PATCH 1/3] amdkfd: Don't clear *kfd2kgd on kfd_module_init Oded Gabbay
2014-12-20 21:25 ` Greg KH
2014-12-21 11:12 ` Oded Gabbay
2014-12-21 11:27 ` Christian König
2014-12-21 11:34 ` Oded Gabbay [this message]
2014-12-21 12:19 ` Christian König
2014-12-21 13:06 ` Oded Gabbay
2014-12-21 13:24 ` Oded Gabbay
2014-12-21 15:57 ` Christian König
2014-12-21 16:03 ` Oded Gabbay
2014-12-21 16:10 ` Christian König
2014-12-22 7:34 ` Oded Gabbay
2014-12-22 7:40 ` Dave Airlie
2014-12-22 7:43 ` Oded Gabbay
2014-12-22 8:57 ` Christian König
2014-12-22 9:26 ` Oded Gabbay
2014-12-22 10:22 ` Oded Gabbay
2014-12-20 20:46 ` [PATCH 2/3] amdkfd: Track when amdkfd init is complete Oded Gabbay
2014-12-20 20:46 ` [PATCH 3/3] amdkfd: Use workqueue for GPU init Oded Gabbay
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=5496B04C.50502@amd.com \
--to=oded.gabbay@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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