Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1407751
| From | "Luis R. Rodriguez" <mcgrof@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFT v2] iommu/amd: use subsys_initcall() on amdv2 iommu |
| Date | 2016-05-27 02:20 +0200 |
| Message-ID | <rDdFn-4Hi-3@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <rpbaq-10N-9@gated-at.bofh.it> <rpbtM-1pm-3@gated-at.bofh.it> <rpbtM-1pm-1@gated-at.bofh.it> <rpga6-5po-3@gated-at.bofh.it> <rptgZ-7Fe-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [RFT v2] iommu/amd: use subsys_initcall() on amdv2 iommu "Luis R. Rodriguez" <mcgrof@kernel.org> - 2016-05-27 02:20 +0200
csiph-web