Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1407751 > unrolled thread

Re: [RFT v2] iommu/amd: use subsys_initcall() on amdv2 iommu

Started by"Luis R. Rodriguez" <mcgrof@kernel.org>
First post2016-05-27 02:20 +0200
Last post2016-05-27 02:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFT v2] iommu/amd: use subsys_initcall() on amdv2 iommu "Luis R. Rodriguez" <mcgrof@kernel.org> - 2016-05-27 02:20 +0200

#1407751 — Re: [RFT v2] iommu/amd: use subsys_initcall() on amdv2 iommu

From"Luis R. Rodriguez" <mcgrof@kernel.org>
Date2016-05-27 02:20 +0200
SubjectRe: [RFT v2] iommu/amd: use subsys_initcall() on amdv2 iommu
Message-ID<rDdFn-4Hi-3@gated-at.bofh.it>
On Tue, Apr 19, 2016 at 10:02:52AM +0800, Wan Zongshun wrote:
> 
> You have to take carefully to arrange the calling sequence for
> iommuv1, iommuv2, kfd module, and drm like the following sequence :
> v1 ->v2->kfd, drm.
> 
> iommuv1 -- rootfs_initcall(fn)
> IOMMUV2 -- device_initcall(fn)
> kfd module -- late_initcall(fn)
> drm -- late_initcall(fn)

Thanks, it turns out this is not exactly enough, given as 
Joerg notes:

--
AMD-KFD on the other hand needs to be loaded before the                                                                                          
radeon driver (but this it not enforced by symbols), because otherwise                                                                                        
the radeon driver will not initialize the AMD-KFD driver. 
---

We have a theoretical race still possible between the kfd module
and the drm driver. I'll reply to Joerg's e-mail with more feedback.

  Luis

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web