I'm sorry you've not heard back... life has been busy for a few of us. Let me try to respond.
First off, are you working *for* Intel, or doing this on the side? If you're not part of the Intel OpenSolaris team or working for Sun, you might want to check in with folks at those orgs, because I think VTD support is already being worked on. That said.... Baolu Lu wrote: > OK, sounds nobody is interested by my questions. :) > > On Nov 9, 2007 10:17 PM, Baolu Lu <[EMAIL PROTECTED]> wrote: > >> Hi all, >> >> I am here to ask somebody's help on my kernel coding. First, let me >> try to describe what I am doing. >> >> I am developing lntel IOMMU driver for OpenSolaris. Intel IOMMU is a >> part of Intel VTD (virtual technology >> for direct IO), which spec can be downloaded from >> http://www.intel.com/technology/virtualization/. >> >> The BIOS exports the IOMMU information through the DMAR ACPI table. >> So, first I get the IOMMU information >> through parsing the ACPI table in the pci_enumverate( ). And create >> the dev_info structure under the >> root neuxs. Then want to let the kernel to load my IOMMU nexus driver >> at the boot time. >> >> My questions are: >> >> 1. What can I do to let the kernel load the IOMMU nexus driver module >> automatically during the boot time? >> There are probably a couple of ways you could do this. First, you could modify rootnex or the platform module to load this. Look for the function "load_platform_drivers" (that's where it lives on SPARC systems at least.) Second you could look around for "forceload" in the kernel. I think you can set a forceload property to force your driver to attach. Something along the lines of forceload: drv/mydriver in /etc/system, perhaps? Alternatively, in a driver.conf file for the driver, add the tunable "ddi-forceattach=1". >> 2. The platform may have more than one IOMMU units. Each has it's own >> register set and interrupt. But they share >> the same bus ops. I want to bind only one driver for them. Does this >> make sense? To do so, should I create >> a dev_info structure for each IOMMU unit or just a single one? >> It makes *perfect sense. Just create one dev_info per iommu unit. -- Garrett >> Thanks for your reading and I am very appreciate for your help. >> >> > _______________________________________________ > opensolaris-code mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/opensolaris-code > _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
