[opensolaris-summit] driver limits [was Re: My comments (very subjective) on proposed Summit topics]
Randy Fishel
randy.fishel at sun.com
Wed Sep 26 12:39:02 PDT 2007
(resend)
> Randy Fishel writes:
> > We do make the requirement of drivers to specify all the interfaces
> > they expect to import and export. We don't make them list the
> > DDI/DKI, as that is a set of implied interfaces. They must, however,
> > specify if they intend to use GLDvX, kEF, and even FMA. If a driver
> > is using any other interface, it should have listed it, and would be
> > in violation of its ARC case if it didn't (IMHO, they should even list
> > consolidation private interfaces).
>
> You're welcome to that opinion, and you can certainly demand it in any
> reviews you do yourself, but it's not actually an architectural
> requirement.
Agreed, it is my opinion, and I try to work that into my reviews of
drivers. I would, however, like it to be more an architectual
requirement, and would be willing to make some arguments or proposals
in the near future (it would be real nice to get my current project
into Solaris).
>
> It'd be possible to set some sort of OpenSolaris-wide policy here. We
> could have an ARC case that specifies what things must be "declared"
> and how they're declared. Such a thing (other than the existing
> interface taxonomy) does not currently exist for the special case of
> drivers. A fast-track specifying this (and the detailed rationale
> behind it) might be helpful.
>
As Garrett, I am in agreement, and am more than willing to work with
and/or sponsor such an effort (though again, after I integrate my
current set of bits). Garrett- you in for a collaboration here?
---- Randy
More information about the opensolaris-summit
mailing list